Saturday, January 29, 2022

Microsoft 365 Apps Update Stuck at 50% Downloading error 0x87D0024A

Referring to any Microsoft 365 Apps update getting stuck in Downloading (50% Complete)

There could be multiple reason on Updates getting stuck..




1. To get brief understanding on what does a KB or update do, review https://www.catalog.update.microsoft.com/ 

Will get good information on a KB as well as old / new updates that are superseded or replaced



2. Logs to Review:

WUAHandler.logRecords details about the Windows Update Agent on the client when it searches for software updates.

UpdatesDeployment.logRecords details about deployments on the client, including software update activation, evaluation, and enforcement. Verbose logging shows additional information about the interaction with the client user interface.

UpdatesHandler.logRecords details about software update compliance scanning and about the download and installation of software updates on the client.

UpdatesStore.logRecords details about compliance status for the software updates that were assessed during the compliance scan cycle.

Microsoft Document link: https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/hierarchy/log-files

Entry in UpdatesHandler.log:
BeginDownload alternate update content failed. Error = 0x87d0024a
CDeploymentJob – Failed to download update Error= 0x87d0024a

Error in Software Center: 


3. Error Definition:
Office365 Updates failing with error 0x87D0024A The job is already connected

4. Probabilities of solution:
  1. Reinstallation SCCM Client
  2. Repair SCCM Client
  3. Added devices exclusion, post scan cycle this will wipe info.. Remove exclusion
  4. Language pack.. multiple DP & Redistribute content
  5. Other blogs .. apiclient.dll is missing or corrupt.. 
    • C:\programfiles\Common Files\Microsoft Shared\ClickToRun\ApiClient.dll
    • Replacing this file from working machine can be tried

5. Fix I have applied:
  • Software Center >> Installation Status >> Office 365 English (US) Language Pack >> Repair
  • 30 min down time..
  • Reinstalls office. Successful completion
  • Updates & Retry MS 365 App updates 
  • Completes Installs Successfully.
  • Pre Restart Client OS before repairing language pack.






Sunday, January 23, 2022

Devices Stuck in Waiting for Maintenance Window

Question :: Why application deployment is not enforcing automatically ?





Observation : In Appenforce.log no entry of enforcing visible.

Workaround : In Software Center when click on Retry Application installs successfully.

Or

Click on app eval from action cycle during maintenance window

Troubleshoot Application Deployment: https://docs.microsoft.com/en-us/mem/configmgr/apps/understand/deployment-policy-technical-reference


Snapshot of Application deployment :

  1. Policy Creation:
    • ConfigMgr :: Policy Created SMSProv.log >> objreplmgr.log
  2. Application Deployment for Device / User Collection:
    • Client.log :: PolicyAgent.log >> Scheduler.log >> DCMAgent.log
  3. DCMAgent.log >> CIAgent.log (other logs too CCMessaging.log)
  4. CI Agent >> Downloading CI… metadata is downloaded CI Downloader.log , DataTransferService.log
  5. InvokingSdmMethod >> Application detection (Appdiscovery.log , AppIntEval.log)
  6. StateDownloadingContents >> CAS, ContentTransferManger,LocationService, DataTransferService
  7. StateEnforcing CI >> AppEnforce.log
  8. StateEnforcementReporting >> StateMessage.log

Error observed in DCMAgent.log:
DCMAgent error : The DCMAgent.log also contains an error resembling the following, recorded at the same time as the SCClient log entry.  The 0x87d00315 error code translates to "The CI version info data is not available."  



FIX: 
  1. ccmstore.sdf >> rename / delete (Ccmstore.sdf is created) >> Run Action Cycle
  2. Uninstall SCCM Client & Reinstall

Saturday, January 15, 2022

FIX for CCMSETUP install error code 0x87d00227

 FIX for CCMSETUP install error code 0x87d00227



While installing client if see error in installing client as 0x87d00227 CCMSetup error



Can check metered connection settings:

Go to Select Start  > Settings  > Network & Internet > Internet Properties

Set as Metered Connection if its ON need to turn OFF

Rerun CCMSetup should get CcmSetup is exiting with return code 0







Sunday, January 9, 2022

Enable Verbose / Debug Logging in SCCM / MECM Client Computers



In case if we need more detail information while troubleshooting thru logs, we need to enable Verbose / Debug logging

2 Ways we can enable Verbose Logging.

  1. Thru SCCM / MECM Client Computer 
  2. Thru SCCM / MECM Console


1. Thru SCCM / MECM Client Computer 

Go to regedit :: 
  • Registry path HKEY_LOCAL_MACHINE\Software\Microsoft\CCM\Logging\@GLOBAL\
  • LogLevel set as 0
  • By default value is 1, need to change to 0.
  • Below are different values of logging ranging from 0 to 3









To enable debug logging set registry in below :

  • Create registry value as REG_SZ , name as Enabled with a value of True
  • HKEY_LOCAL_MACHINE\Software\Microsoft\CCM\Logging\DebugLogging\Enabled
  • If DebugLogging folder not present need to create it



  • Restart SMS Agent Host Service


2. Thru SCCM / MECM Console 
  • Open Microsoft Endpoint Configuration Manager
  • Go to Devices >> Select Device 
  • Right Click >> Client Diagnostics >> Enable Verbose Logging


  • Restart SMS Agent Host Service on client computer


More info on below Microsoft site:

https://docs.microsoft.com/en-us/troubleshoot/mem/configmgr/enable-verbose-logging

https://docs.microsoft.com/en-US/troubleshoot/mem/configmgr/turn-on-debuglogging-key



HOW TO DEPLOY SCCM / MECM CLIENT ON DEVICES ?

To install SCCM / MECM client on devices: Precheck: 1. Installation Account is a member of Local Administration group 2. Site Server can ...