UPGRADE MECM CONSOLE TO 2111

 While upgrading MECM Console to 2111, following key pointers are helpful.

1. Check Current version thru About
2. Select Update & Servicing thru Administrations
3. Check Prerequisites 
4. Log file to review :: ConfigMgrPrereq.log
5. Check Status in Monitoring Pane
6. Incase of error reported , review as per info in Status message in Description
7. Fix the error.
8. Re check Prerequisites
9. Install Update Pack
10. Check logs to review thru Status message during update process
11. Monitoring Update status 
12. Verification post successful install

Complete Video guide herewith :

STEP BY STEP GUIDE FOR PATCHING WINDOWS CLIENT DEVICES

For remediating patching on SCCM Managed client computers 

4 Important Steps :

1. Scanning of devices
2. Reviewing Logs to see patch status
3. Remediation to deploy Patches
4. Patches are deployed as per logs, however reporting is showing as non compliant

Additional info on :

• Manual Patch deployment
• Possibility of why issues being reported.
• Software Center Error Codes & description

--------------------------------------------------------------------------------------------

--------------------------------------------------------------------------------------------

STEP 1: Scanning of devices: 

• Check WUA Handler log if scanning is failing
• Complete detail on WUAHandler.log & fix is linked to registry.pol <check date>, rename or delete registry.pol file & run gpupdate /force & run software update eval cycle & scan cycle.
• Complete troubleshooting video on scanning issue https://youtu.be/4ntGsLCu-7E

STEP 2: Reviewing Logs to see patch status:

• Check updatestore.log for that particular KB we will see if missing or existing by taking note of unique ID.
• Review more logs based on unique id Updatedeployment.log, updatehandler.log, updatestore.log, WUAHandler.log, windowsupdate.log may give us good clue on errors.
• To review Windowsupdatelog
• Powershell >> get-windowsupdatelog
• Another file is created which will have more details.
• Logs will have entry like:
• ASSIGNMENT_EVALUATE_SUCCESS, ASSIGNMENT_ENFORCE_FAILED or any other message like Failed to attach update to the automation wrapper = 0x87D00215.
• If seen as finished installing (0x000000000), means patches are installed.
• No pending patches available as of now, kindly find the log details.
• <![LOG[EnumerateUpdates for action (UpdateActionInstall) – Total actionable updates = 0]LOG]!><time=”05:02:16.837-60”date=”02-16-2022” component=”UpdatesDeploymentAgent” context=”” type=”1” thread=”27904” file=updatesmanager.cpp:1826”>

STEP 3: Remediation to deploy Patches:

• Caused by some update files becoming corrupt while being downloaded. If this happens you can delete or rename the folder & it will be recreated in same location.
• Couple of placed observed one in software distribution & ccmcache
• Renaming Folders
• Softwaredistribution folder located in C:\windows\
• If ccmcache, can rename ccmcache folder or specific subfolder if aware
• Catroot2 folder located in C:\windows\System32
• By default it will not allow as services are running in backend
• Stop Windows update service Service name: wuauserv
• Stop Cryptographic Services Service name: CryptSvc
• Stop Background Intelligent Transfer Service name: bits
• Stop Windows Installer Services Service name: msiserver
• Post service stopped rename folder
• Sometimes few services auto start so you will need to disable it.
• Once folders are renamed restart / enable above 4 services & also check status of SMS Agent host service
• If windows installer services is giving error while starting check to Unregister and re-register Windows Installer by following command
• Msiexec /unregister
• Msiexec /regserver
• Reboot system & check
• Initiate “Software Update Scan Cycle” and “Software Updates deployment evaluation cycle” from configuration manager applet 
• Review logs 
• If patches still fail to deploy, there can be windows issue
• Sfc/scannow (this is System File Checker)
• Windows Update troubleshooter can be accessed thru settings

STEP 4: Patches are deployed as per logs, however reporting is showing as non compliant. 

• We need client to resend its data to the MP.  It’s a convenient way to force some state messages up.
• Powershell query
• $UpdateStore = New-Object –ComObject Microsoft.CCM.updateStore
• $UpdateStore.RefreshServerComplianceState()
• This command will help to update / refresh compliance state on SCCM
• Sitecode change
• Reinstall Client

--------------------------------------------------------------------------------------------

Additional observation: Certain times specially for in case office patches if missing can check to Repair / reinstalling of Office application.

Manual Patch deployment:

Go to patches kb downloaded will see location either in ccmcache or download folder

• c:\windows\softwaredistribution\Download
• Open CMD (elevated rights)
• DISM.exe /online /Add-package /PackagePath: “c:\windows\softwaredistribution\Download\.... <get info from folder.cab file?>

       OR

• Extract cab file & run windows installer file post extract

Possibility of why issues being reported:

• Offline or Inactive client – bring it back to network
• Device not in use – its retired from AD or SCCM 
• Pending Reboot
• Low Disk space – housekeeping of HDD / upgrade HDD size
• Download Corrupt
• SCCM Client Corrupted
• If client not updating recent date client repair / reinstall
• GPO issue

--------------------------------------------------------------------------------------------

Software Center Error Codes:

Error Code	Error Description	Error Status Description
-2146498170	Unknown Error	This update application failed
-2146498173	Unknown Error	This update application failed
-2016410855	Unknown Error	ConfigMgr internal error occurred for this update
-2146498168	Unknown Error	This update application failed
-2146498174	Unknown Error	This update application failed
-2146498171	Unknown Error	This update application failed
-2146498172	Unknown Error	This update application failed
-2145099757	Unknown Error	This update application failed
-1906441218	Unknown Error	This update application failed
-2146498304	Unknown Error	This update application failed
-1906441221	Unknown Error	This update application failed
-2146498169	Unknown Error	This update application failed
-1906441212	Unknown Error	This update application failed
-2145099774	A download manager operation could not be completed because the file digest was not recognized	ConfigMgr internal error occurred for this update
-2147024891	Access is denied	This update application failed
-2147024873	Data error (cyclic redundancy check)	This update application failed
-2147023898	Invalid access to memory location	This update application failed
-2147024882	Not enough storage is available to complete this operation	This update application failed
-2016409851	Pause state required	ConfigMgr internal error occurred for this update
-2016410031	Post install scan failed	ConfigMgr internal error occurred for this update
-2147024858	Reached the end of the file	This update application failed
-2016409844	Software update execution timeout	This update did not finish in allocated time
-2016410008	Software update still detected as actionable after apply	ConfigMgr internal error occurred for this update
-2147010798	The component store has been corrupted	This update application failed
-2146869232	The digital signatore of the object did not verify	ConfigMgr internal error occurred for this update
-2147024629	The directory name is invalid	This update application failed
-2147023504	The file or directory is corrupted and unreadable	This update application failed
-2147024894	The file you specified could not be found. This may be because it is not signed	This update application failed
-2016411062	The job is already connected	ConfigMgr internal error occurred for this update
-2147010815	The referenced assembly could not be found	This update application failed
-2147010893	The referenced assembly is not installed on your system	This update application failed
-2147023170	The remote procedure call failed	This update application failed
-2147010788	The SMI primitive installer failed during setup or servicing	This update application failed
-2147024291	The specified buffer contains ill-formed data	This update application failed
-2147024784	There is not enough space on the disk	This update application failed
-2147018095	Transaction support within the specified resource manager is not started or was shutdown due to an error	This update application failed
-2016410012	Updates handler job was cancelled	ConfigMgr internal error occurred for this update
-2147023838	Windows: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.	ConfigMgr internal error occurred for this update

 

Follow Below platforms to get updates:

Blog Website: https://mecmworld.blogspot.com

Twitter : https://twitter.com/YagneshMalaviya

Linked In : https://www.linkedin.com/in/yagnesh-malaviya

Facebook: https://www.facebook.com/mecmworld

Instagram : https://www.instagram.com/mecm_world

Email ID: mecmworld22@gmail.com

If you would like to share your troubleshooting fix or knowledge on MECM, you are most welcome to share your interest in email. Will look forward to collaborate & share knowledge.

Thanks.

Yagnesh Malaviya

Software Center Install Error Codes

Application do install thru Software Center however there are certain moments when apps fail to install & we see some error codes in Software Center.

Software Center Error Codes:

• 0x1(1)
• Incorrect function
• Residuals found in device also app present in Appwiz, uninstall restart, check install , if still problem persist check registry
• Deployment Failed

• 0x87D00213(-2016411117) : Timeout occurred
• 0x87D0027C (-2016411012) : CI Document download time out
• 0x800705B4 (-2147023436) : Operation returned because timeout period expired
• Install took longer than allowed.
• Try install again usually associated with installs that require user input to complete.
• Review Install logs
• issue observed while reviewing DCMAgent log with bug in MS… I had to rename ccmstore.sdf or reinstall client.. complete video link https://www.youtube.com/watch?v=6qpphPO4AJ0
• "Deployment Failed or "Requirments not met" or "Evaluation Failed" or "Failed to locate content"

• 0x87D00324(-2016410844) 
• Detection issue
• The software package installed successfully, but a software detection rule was not found.
• You can verify the application detection method mentioned also by checking install logs , appenforce can also give certain clue.


• 0x87D00325(-2016410843) 
• Detection issue
• The software package uninstalled successfully, but a software detection rule was still found.
• Review uninstall logs, check appwiz.cpl"

• 112 : Not enough space on the disk
• -2147024784 : Not enough space on the disk
• -2147023080 : Not enough quota is available to process this command
• 0x87d01201(-2016407039) : Out of space
• Deployment Failed
• Download fail, HDD out of space
• Check HDD Space
• CCMCache max size limitation check

• 0x652 (1618) : Another installation is already in progress
• -2147023278 : Another installation is already in progress
• Deployment Failed
• Another install in progress
• Restart services or computer"

• 0x80040154 (-2147221164)
• Class not registered 
• Evaluation Failed
• CCMRepair, Client Reinstall

• -2147010895
• Deployment Failed
• Application has failed to start because its config is incorrect.
• Check event log

Additional Error Codes:

• -2147023504
• Deployment Failed
• The file or directory is corrupted & unreadable
• Clear CCMCache repository folder & Run Action cycle

• -2016407040
• No content request found with the given handle
• Failed to download dependent contents
• Clear CCMCache repository folder & Run Action cycle

• 0x87D00607(-2016410105)
• Content not found
• Could be DP not assigned to Boundary Group Check CITaskMgr, Appdiscovery, appinitEval, appenforce, data transfer, content transfer, CI Agent, DCMagent,

• 0x87D01106(-2016407290)
• Content not available
• Check if content is distributed to DP

• -2147024809
• The parameter is incorrect
• Failed to verify the executable file is valid or to construct the associated CMD line
• Failed to download dependent contents
• Check content in CCMCache or clear ccmcache repository & run action cycles

• 1619
• This installation package could not be opened. 
• Check content in CCMCache or clear ccmcache repository & run action cycles

• 0x80041001(-2147217407)
• Generic Failure
• SMS Agent host service not running, restart service, else repair ccmclient or reinstall client

• 0x80091007(-2146889721)
• Hash value incorrect
• Clear ccmcache & retry, check event log if something else is blocking

• 0x64C (1612)
• Deployment Failed
• Installation source for this product is not available. Verify that source exists and you can access it

• 0x643 (1603) : Fatal error during installation
• 0x87D00443(-2016410557)
• -1073741510 : Fatal error during installation
• -1073741502 : Fatal error during installation
• 424 : Fatal error during installation
• Deployment Failed
• One or more process are running & prevent enforcement action
• Conflict of application, restart pc or review services , apps & close it.

• 5 : Access denied
• -2147217405 : Access denied
• -2147024891 : Access denied
• Deployment Failed or Evaluation Failed or Dependency Installation Failed
• Check permission

• 0x87D01107 (-2016407289)
• Failed to access all provided program locations. 
• Failed to locate content

• 0x80004004 (-2147467260)
• Operation aborted
• Failed to download dependent contents

• -214718113
• Catastrophic failure
• Evaluation Failed

• -2147217389
• Provider load failure
• Evaluation Failed

• 1625
• Deployment Failed
• Installation forbidden by system policy

• 1400
• Deployment Failed
• Invalid Window handle

• -2147023446
• Deployment Failed
• Insufficient System resource exit to complete the requested service

• -2146959355
• Evaluation Failed
• Policy for this program does not exist or is invalid

• -2016410105
• Content not found
• Failed to download dependent contents

Patch scanning fail GROUP POLICY issue linked with Registry.pol

Troubleshoot to diagnose if Patch scanning is failing.

1. Assignment of Patches
2. Scanning of Devices
3. Deploying of Patches

Log Files to check: WUAHandler.log

Common Error seen in log:

Failed to run BeginSearch() on WUAgent. Error = 0x80070422
It’s a WSUS update source type… adding it
Existing WUA Managed server was already set (http://sup.domain:8530) , skipping Group Policy registration.
Failed to run BeginSearch() on WUAgent. Error = 0x80070422

OnSearchComplete – Failed to end search job. Error = 0x80248007
Scan failed with error = 0x80248007
GroupPolicyError.

Error Code seen in logs:
0x0005
0x80004005
0x87d00605
0x87d00692
0x800703EE
0x80070422
0x80070570
0x80248007
0x80080005
0xC8000710
0x80244017
0x80040154
0x80240FFF
0x80240438

FIX:
1. To rename or delete REGISTRY.POL file located in 

C:\windows\system32\Grouppolicy\Machine

C:\windows\system32\Grouppolicy\User (Optional in certain devices)

 
Explore Registry.pol thru notepad or thru third party software

2. Gpupdate /force
3. SoftwareupdateEvalCycle & Scan cycle thru ConfigManager Action items

Post this scanning is successfully