Check the ccmsetup .tcf files too and make sure provisioning mode is not enabled. In order to remove ALL references to provisioning mode.
Sent from my Windows Phone ________________________________ From: JONES, RICK J<mailto:[email protected]> Sent: 10/17/2013 8:29 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Issue with MS13-091 take 2 Just wanted to give you all a heads up and how to fix it for the issues where a client might flip into Provisioning Mode from this last month's MS13-091 patch (http://support.microsoft.com/kb/2862330) where a dual reboot during task sequencing could freak out the client. Here is Microsoft's Information on the problem and fix; http://support.microsoft.com/kb/2894518 The alternatives were not very attractive, namely reloading the client or remotely finding a broken system and running the PowerShell script. I have confirmed that a DCM still works while in the Provisioning Mode (and have PowerShell bypass enabled for clients), this is the command I used to get the information; (Get-ItemProperty HKLM:\SOFTWARE\Microsoft\CCM\CcmExec).ProvisioningMode [cid:[email protected]] Validate it as Value = false [cid:[email protected]] And then use the command referenced in the link for Remediation; Invoke-WmiMethod -Namespace root\CCM -Class SMS_Client -Name SetClientProvisioningMode -ArgumentList $false [cid:[email protected]] Rick J. Jones Wireless from AT&T Domestic Desktop Application Management D: (425) 288-6240 C: (206) 419-1104
<<inline: image001.png>>
<<inline: image002.png>>
<<inline: image003.png>>
