Jaybone Posted March 27, 2015 Report post Posted March 27, 2015 Hi, all. SCCM 2012 SP1 A few months back, we deployed CU5 to clients via SCUP. Most clients upgraded without issue. There are a bunch, though, that the console seems confused about: Client version listed under Devices, and in the properties of the device is .1000. Client version shown on a compliance report run against the deployment is .1000, even though the device is shown as compliant. CCMexec.exe version on the device is .1600. Anyone know how to get this sorted out? Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted March 27, 2015 Report post Posted March 27, 2015 The version gets updated with the next heartbeat discovery. Quote Share this post Link to post Share on other sites More sharing options...
Jaybone Posted March 30, 2015 Report post Posted March 30, 2015 The version gets updated with the next heartbeat discovery. When it works, sure, but that's not the issue here, unfortunately. These computers were updated months ago. You can see in the report window for this client that the last state received and last state change were back in February and January, respectively, and you can see in the client window that the last heartbeat was on 3/26. I manually initiated a DDC anyway for the heck of it on Friday 3/27. Didn't help. Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted March 30, 2015 Report post Posted March 30, 2015 This is normal, not every place list the FULL version number. it will only list the last service pack version number. Quote Share this post Link to post Share on other sites More sharing options...
Jaybone Posted March 30, 2015 Report post Posted March 30, 2015 It's normal that ~75% of my clients that successfully upgraded to CU5 will show as version 5.0.7804.1600, and the remainder will show as version 5.0.7804.1000? Sorry, but I have a hard time believing that. Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted March 30, 2015 Report post Posted March 30, 2015 Again, not all columns in CM12 will show the Full Version #, some will only show the SP version#. If you are saying that within one column you are seeing some with the updated versions and other without then yes there might be a problem. Generally HB will fix this but I just review the inventoryagent.log and the CM12 client version is NOT listed as one of the fields queried, therefore I'm not sure what actually updated this. Quote Share this post Link to post Share on other sites More sharing options...
Jaybone Posted April 1, 2015 Report post Posted April 1, 2015 If you are saying that within one column you are seeing some with the updated versions and other without then yes there might be a problem. That's exactly it. Most devices show the correct build number (1600) in the "Client Version" column when the device list is viewed in the console, and in that same field if the device properties are viewed, and in that field in the Complicance 8 report. But many don't, and instead show build 1000 even though they're really updated to CU5/build 1600. This even months later, after many heartbeats (set to happen once a day). Quote Share this post Link to post Share on other sites More sharing options...
Jaybone Posted September 21, 2015 Report post Posted September 21, 2015 ...six months later... After upgrading to R2 SP1 CU1 some weeks back, this problem seems to have disappeared. We've got only a handful of systems that are showing old builds in the console, and they're all ones that are either powered off or off-network for extended periods, so it's expected. Quote Share this post Link to post Share on other sites More sharing options...
