22 January 2021

Configuration Manager Message ID 11170 Error

I was in the process of pushing out the Microsoft Windows 10 20H2 upgrade when I had 23 systems that errored out. They reported the error shown below. 


After looking at the logs and at Software Center on the target machine, I found the target machine was not seeing the deployment under Operating Systems. The fix was to reinstall the client on the target machine. Once the reinstall completed and the client synchronized with the ConfigMgr server, the deployment appeared in Software Center and successfully completed. 

Related Posts:

  • USMT 4.0 PC-to-PC Migration Script This script will execute the USMT, migrating data from the old machine to the new machine. Both PCs must be on the network. You will be prompted to enter the old computer name, new computer name, and the username. This is t… Read More
  • Java Runtime Environment Installation Script This VB script I wrote will uninstall all previous versions of Java Runtime Environment. It will also install both the x86 and x64 versions, depending on whether the OS is 64-bit compatible. It uses the msi installer, which … Read More
  • VBScript Software Installation With as often as I deploy software, I created a standard VBScript template to use when needing to create an unattended application installation. One thing that I do not have in this script is and uninstall procedure, which I… Read More
  • List all systems that are logged off I wrote this script in 2010 to be able to give me a list of systems that are currently logged off from a list of computers in a text file. My purpose for this was to be able to find systems to test software deployments on in… Read More
  • Deploying Autodesk Revit Packages Autodesk makes it very easy to create installation packages for deploying Revit software. The problem is that when executing these deployment packages through SMS/SCCM or integrating them into a build process, the package re… Read More

0 comments:

Post a Comment