Config Manager

[aac]

Hi all, we are using config manager 2309 and are experiencing an issue whereby if we reimage a machine using the same name it is not picking up application or software updates. I can confirm there is not a duplicate machine listed under devices as I make a point of removing these as and when and I have also tried running the application and software updates evaluation under client notification options of the machine. A quick google suggests it may be a known issue that has existed for a while but I cannot see any obvious resolution.

 

Many thanks in advance

[chris_uk]

It is an annoying problem, it happens so randomly. The only way I have found to fix it is below.

 

On the client, delete the contents of the folder c:\windows\ccmsetup, on the SCCM console, right click, install client, tick - Always install the client software, then tick "Uninstall existing configuration manager client before the client is installed". This will then get everything to re-register. Also if you add the following as a script,

SCCM, Software Library, Scripts, Create Script. Call it "SCCM - Run all actions"

 

Invoke-WmiMethod -Namespace root\ccm -Class sms_client -Name TriggerSchedule "{00000000-0000-0000-0000-000000000021}"
Invoke-WmiMethod -Namespace root\ccm -Class sms_client -Name TriggerSchedule "{00000000-0000-0000-0000-000000000022}"
Invoke-WmiMethod -Namespace root\ccm -Class sms_client -Name TriggerSchedule "{00000000-0000-0000-0000-000000000003}"
Invoke-WmiMethod -Namespace root\ccm -Class sms_client -Name TriggerSchedule "{00000000-0000-0000-0000-000000000002}"
Invoke-WmiMethod -Namespace root\ccm -Class sms_client -Name TriggerSchedule "{00000000-0000-0000-0000-000000000001}"
Invoke-WmiMethod -Namespace root\ccm -Class sms_client -Name TriggerSchedule "{00000000-0000-0000-0000-000000000113}"
Invoke-WmiMethod -Namespace root\ccm -Class sms_client -Name TriggerSchedule "{00000000-0000-0000-0000-000000000114}"
Invoke-WmiMethod -Namespace root\ccm -Class sms_client -Name TriggerSchedule "{00000000-0000-0000-0000-000000000031}"
Invoke-WmiMethod -Namespace root\ccm -Class sms_client -Name TriggerSchedule "{00000000-0000-0000-0000-000000000121}"
Invoke-WmiMethod -Namespace root\ccm -Class sms_client -Name TriggerSchedule "{00000000-0000-0000-0000-000000000026}"
Invoke-WmiMethod -Namespace root\ccm -Class sms_client -Name TriggerSchedule "{00000000-0000-0000-0000-000000000027}"
Invoke-WmiMethod -Namespace root\ccm -Class sms_client -Name TriggerSchedule "{00000000-0000-0000-0000-000000000032}"
Invoke-WmiMethod -Namespace root\ccm -Class sms_client -Name TriggerSchedule "{00000000-0000-0000-0000-000000000010}"

 

Once you have saved and authorised the script, you will then be able to right click on a device and select "Run Script" This script runs all the actions that you find in the control panel applet. So it will do a hardware scan, windows update scan, required software scan... etc etc. Handy to force hardware to check in if you have software for specific hardware.

 

Shout if you need any more help.

 

Chris

[aac]

Hi Chris

 

I am getting "Some of the selected resources are not assigned to any site" when trying to redeploy the client using the 2 settings you suggest above. If I use "Install the client from a specified site" option it is not erroring but does not deploy.

[chris_uk]

Delete the device from SCCM, let the system re-find it from AD and if the device self registers. Deleting it from SCCM won't harm anything.