cubspsycho85

Hello, I have some, not all, clients showing in an inactive status after I upgraded our infrastructure to R2 SP1, then right after CU2. The ones showing inactive have a last heartbeat date around the time I did the upgrade. The only thing that seems to resolve the issue is to remove the device object from SCCM, and restart the service on the device. Unfortunatly I don't see this as a valid solution as some devices may be in many collections. In my testing, I have noticed the CM Client GUIDs do not match from the client to the console for some reason. I was wondering if anyone has seen this themselves, or if anyone has any suggestions on what to check. The log files all look "fine" except for many of them are missing.

Jaybone, I know this is an older topic, but I'm now experiencing this issue as well after upgrading to 2012 R2 SP1 CU2. Did you figure anything out for this?