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: @Opsgility <http://twitter.com/opsgility/> , @pcgeek86 <http://twitter.com/pcgeek86> <http://opsgility.com/> 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
