Jump to content


Mackan

Established Members
  • Posts

    2
  • Joined

  • Last visited

About Mackan

  • Birthday 12/07/1974

Profile Information

  • Gender
    Male
  • Location
    Stockholm, Sweden

Mackan's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hi again! Have you installed Powershell 3.0 on your clients? If so, it could be the trigger to cause the problems. What we think we know for now is... When we install Powershell 3.0 it breaks something (eg. WMI). When the nightly scheduled task runs ccmeval.exe it tries to repair the client. When this happens the last thing it does is to set the client in Provisioning Mode because it is instructed to do so in "C:\Windows\ccmsetup\MobileClient.TCF" and "C:\Windows\ccmsetup\MobileClientUnicode.tcf". A quick fix is to open MobileClient.TCF and MobileClientUnicode.tcf in C:\Windows\ccmsetup\ in Notepad (as Admin) and change "SMSPROVISIONINGMODE=1" to "SMSPROVISIONINGMODE=0". Then run C:\Windows\CCM\ccmeval.exe to repair and set the client to none provisioning mode. It is the installation of Powershell 3.0 that triggers Ccmeval to repair and set the client in provisioning mode but we think it could be triggered by other software too. The real issue seems to be that the tcf-files has the SMSPROVISIONINGMODE=1 setting. So even though we choose to NOT install Powershell 3.0 we believe it could be a time ticking bomb because suddenly another software may cause the ccmeval to repair and set all clients in provisioning mode. We have opened a support case at Microsoft Support for this issue.
  2. Check if the failed clients are in Provisioning Mode. For some reason working clients sometimes is set back to provisioning mode the night after they have been deployed (and that may be caused by a scheduled task). Check the values “ProvisioningMode” and “SystemTaskExcludes” under the registry key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmExec] Change the value“ProvisioningMode” to "False" and delete the data in value “SystemTaskExcludes” so it is blank. Then restart the SMS Client service. Wait a minute and then check in the ConfigMgr control panel if PKI is enabled again and that all Actions are there. We have seen this problem and we think it is caused by one or several applications in the Task Sequence that is stuck in a installation loop. The MSI product code detection method was not enough so we added other detection methods, eg a registry value or a file existence, fore those applications. Beware of that a client you fix can be set to Provisioning Mode again the night after you have fixed it. Regards M
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.