I have not tried the solution described on this link yet, but I plan to try it in the lab when I have some time, he has automated the repair of the SCCM client using a GPO and PowerShell.
https://4sysops.com/archives/managing-inactive-clients-in-sccm-2012/ From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Wednesday, October 22, 2014 1:56 PM To: [email protected] Subject: RE: [mssms] Random CM12 Client Corruption For Win7, start with KB2775511. It's a hotfix rollup with major group policy processing, WMI, and performance fixes. It's a must have for Win7. Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Wisniewski, Philip Sent: Wednesday, October 22, 2014 2:46 PM To: [email protected] Subject: RE: [mssms] Random CM12 Client Corruption Thanks for the reply Trevor. Our machines are currently all Windows 7 or 8.1(mostly 7). Our software update point currently has all classifications selected with 2 exceptions, Feature Packs and Tools. There are several WMI Hotfixes <http://support.microsoft.com/kb/2591403> available from Microsoft as well but these are not downloaded via the software update point. I wouldn't want to just deploy them all, I'd have to figure out which ones would apply to our problems. From: [email protected] [mailto:[email protected]] On Behalf Of Trevor Sullivan Sent: Wednesday, October 22, 2014 11:56 To: [email protected] Subject: RE: [mssms] Random CM12 Client Corruption Phil, What are the client operating systems? Are you sure you're deploying all operating system patches, including non-security patches? There are WMI fixes out there for Windows 7, and you gotta be sure to deploy those. A lot of folks seem to deploy security patches only, but ignore reliability patches. Trevor Sullivan Director of Training and Product Development - Opsgility Microsoft MVP: PowerShell <http://www.opsgility.com/> http://www.opsgility.com M: 630-344-9867 Follow us on Twitter: <http://twitter.com/opsgility/> @Opsgility, <http://twitter.com/pcgeek86> @pcgeek86 <http://opsgility.com/> Description: Description: Opsgility Azure Training Delivery and Content Development From: [email protected] [mailto:[email protected]] On Behalf Of Wisniewski, Philip Sent: Wednesday, October 22, 2014 11:35 AM To: [email protected] Subject: [mssms] Random CM12 Client Corruption Hello everyone, There are articles and documentation everywhere on troubleshooting the miscellaneous issues with random client corruption in CM12 environments. Everything from broken clients to WMI corruption to provisioning mode and on and on and on. We seem to see about 5% to 10% of our clients go dark as a rough estimate. My query to all of you is how are you dealing with these issues in your environment(if you have them)? We've been looking for a way to keep our clients functioning and compliant. I've developed a PowerShell based troubleshooter for our service team to use that runs through the typical tasks. I've recently started looking into the GPO based startup script <http://blog.configmgrftw.com/configmgr-client-startup-script/> as a proactive way to try and remediate issues. Thanks for any input or suggestions you may have, -Phil The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
