Share This Post

Fix for ConfigMgr Clients Stuck in Provisioning Mode After 1610 Upgrade

Microsoft has now supplied a fix for Configuration Manager clients that are stuck in provisioning mode after the following conditions are true:

  • A Configuration Manager Current Branch client was deployed by using the Setup Windows and ConfigMgr task sequence step.
  • After you upgrade to client version 1610, a client update (hotfix) is installed, or a client language pack is installed or removed by using the Automatic Client Upgrade feature.

 

The fix that is available through Updates and Servicing will keep future clients from entering this state. However, for those already affected, you’ll need to run the following PS script in an elevated CMD window:

Powershell.exe Invoke-WmiMethod -Namespace root\CCM -Class SMS_Client -Name SetClientProvisioningMode -ArgumentList $false


Looking for an awesome, no-nonsense technical conference for IT Pros, Developers, and DevOps? IT/Dev Connections kicks off in San Francisco in 2017!

IT/Dev Connections

Share This Post

Leave a Reply