This article discusses an issue in Microsoft System Center 2012 Configuration Manager Client and System Center 2012 R2 Configuration Manager Client that could cause an inadvertent client upgrade in a Configuration Manager current branch or long-term servicing branch environment.
This article provides workarounds to prevent clients from being upgraded automatically.
In a Microsoft System Center 2012 or System Center 2012 R2 environment, you notice the following symptoms:
- Clients successfully reinstall themselves every five hours. This activity is logged in the ccmsetup.log and Windows event logs.
- When you view the \Microsoft\Microsoft\ConfigurationManager folder in Task Scheduler, you find a task that is named “Configuration Manager Client Retry Task.”
This issue occurs because CCMSetup creates the client retry task in the wrong folder on the client. This prevents CCMSetup from locating and removing the task.
The scheduled task is created in the “\Microsoft\Microsoft\Configuration Manager” folder instead of the “\Microsoft\Configuration Manager” folder.
To work around this problem, remove the retry task. To do this, use one of the following methods.
Manually remove “Configuration Manager Client Retry Task” from the “\Microsoft\Microsoft\Configuration Manager” folder by using Task Scheduler.
Deploy a script to remove "Configuration Manager Client Retry Task” from the “\Microsoft\Microsoft\Configuration Manager” folder.
Example Windows PowerShell commands to add to your script
get-scheduledtask -taskname "Configuration Manager Client Retry Task"unregister-scheduledtask -taskname "Configuration Manager Client Retry Task" -confirm:$false
In System Center Configuration Manager current branch version 1602 and later versions, and in long-term servicing branch version 1606, Ccmsetup correctly removes the scheduled task after the clients are upgraded.