Restart the Windows Management Instrumentation serviceĤ. Rename repository folder in c$\Windows\System32\wbem to repository.OLDģ. Stop the Windows Management Instrumentation serviceĢ. For WMI errors try to rebuild the WMI repositoryġ. While the setup is running, monitor task manager – CCMSetup to CCMExec – meaning setup is success and its moving to contacting the SCCM server for further assignmentsĤ. Monitor the c$\Windows\ccmsetup\Logs – ccmsetup.log for error code 0Ĥ.
Run the command as – cscript.exe c:\temp\CM2012Client$\SCCM-ClientInstall.vbs /RunLocal:trueģ. Copy all the setup files (CM2012Client$) to local drive from ( c:\temp) \\MFCSCCMPKL02 \CM2012Client$\Ģ. Make sure registry key HKLM\Software\Microsoft – CCM & CCM setup is no more – if not rename themġ. Make sure no task scheduler named Configuration manager under Microsoft task scheduler, if exist delete it ( delete the task in it before deleting the folder)Ħ. Make sure C:\windows\SMSCFG.ini is deleted, if not rename itĥ. Rename CCMSetup,CCM,CCMCache folders in c:\windowsĤ. Run ccmclean.exe and wait for the process to complete ( process monitor)ģ. Run c:\windows\ccmsetup\ccmsetup.exe /uninstall – monitor ccmsetup.logĢ. If the installation is failed performed clean uninstallation and reinstallationġ. Check ccmsetup logs for installation failure errors. Therefore we use following manual steps for each VDI machines one by one which takes couple of hours … How can we go for an Automation kind of batch file or script to do this job on schedule basis by providing the VDI corrupted client machine name from Primary Server instead of these manual steps. In daily basis we found 20-30 machine’s SCCM client corruption issue.
In our SCCM 2012 environment We have VDI machines. If another service or process is using those files, then I’d love to know what it is so I can kill that process in my uninstaller script prior to executing CCMClean.
Is anyone aware of what, exactly, the Windows Installer needs a reboot for to complete the uninstallation and whether or not there are any workarounds? I’ve seen it move files into the Windows temporary directory for deletion, but it should just be able to delete it anyways because CCMExec should not longer be active and utilizing the files in question, so I’m at a loss. I’ve tried shutting down both the SMS Agent Host Service and the CmRcService prior to the uninstall, but it’s usually the same result. SCCM 2007 was never like this, from what I recall. I feel it is absurd that the OS requests this, as no administrator or technician has time nor desire to contact a user and request that they interrupt their current session just for a reinstall of the CCM client (likewise, no user wants to do it – nor should they have to do it). Windows Installer has requested a reboot. I know this is an old thread, but I continually run into the following message while running CCMClean.exe to uninstall CM12 SP1 clients:
0 kommentar(er)
