I'd like to start a discussion for us to share information about SMS 2 client health maintainance.
I bet each of us has some trouble with clients with bad WMI repositories, old hardware scans (while software is current), oddball status messages, connecting to incorrect sites, dropping out of inventory, misbehaving advertisements, etc. Do you handle this manually or through automation?
We have two items of automation right now but are hoping to implement additional mechanisms. One automation we have is to immediately turn on the travel mode setting to prevent a SMS client from reporting to a different site while traveling. (Sometimes it gets applied at the wrong site, but the frequency is low.) Another is to create a "clone" collection based on duplicate GUIDs and other factors. A newUID package is advertised to the GUID to help automate cleanup. (Letting the folks at the site understand how to replicate hard drive images helps reduce the clones.)
What automated actions do you take (or wish you could take) for misbehaving clients?
I bet each of us has some trouble with clients with bad WMI repositories, old hardware scans (while software is current), oddball status messages, connecting to incorrect sites, dropping out of inventory, misbehaving advertisements, etc. Do you handle this manually or through automation?
We have two items of automation right now but are hoping to implement additional mechanisms. One automation we have is to immediately turn on the travel mode setting to prevent a SMS client from reporting to a different site while traveling. (Sometimes it gets applied at the wrong site, but the frequency is low.) Another is to create a "clone" collection based on duplicate GUIDs and other factors. A newUID package is advertised to the GUID to help automate cleanup. (Letting the folks at the site understand how to replicate hard drive images helps reduce the clones.)
What automated actions do you take (or wish you could take) for misbehaving clients?