rem7777 Posted January 5, 2016 Report post Posted January 5, 2016 I recently inherited an SCCM 2012 R2 environment from a colleague. The primary was upgraded to 5.00.7958.1604 in May 2015 (just before the release of R2 SP1). 'Automatic Client Upgrade' is enabled, but only 60% of the clients seem to be on the correct version: 5.00.7958.1000 = 40% of computers 5.00.7958.1604 = 60% of computers Is there any troubleshooting I can do to find out why these clients haven't upgraded? As I understand it, the clients should've detected that a new version of the client was available and scheduled an upgrade during the period defined in the 'Automatic Client Upgrade' settings (in this case 7 days). Appreciate any advice on this. Quote Share this post Link to post Share on other sites More sharing options...
Jaybone Posted January 5, 2016 Report post Posted January 5, 2016 Are you sure they're really on the wrong version? We had an issue with non-R2 SP1, CU...something - 5 maybe, where the console would show an older version for a client, even though the client had indeed updated. That seemed to get fixed after we upgraded to R2 SP1. Quote Share this post Link to post Share on other sites More sharing options...
rem7777 Posted January 5, 2016 Report post Posted January 5, 2016 Are you sure they're really on the wrong version? We had an issue with non-R2 SP1, CU...something - 5 maybe, where the console would show an older version for a client, even though the client had indeed updated. That seemed to get fixed after we upgraded to R2 SP1. Thanks Jaybone - That's interesting! I've taken my figures from the “Count of Configuration Manager clients by client versions” report - I'll do some checking tomorrow to find out whether they're actually the version showing on the report. Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted January 5, 2016 Report post Posted January 5, 2016 The client provides the updated version number during the next heartbeat discovery. Depending on the schedule of the heartbeat discovery, this might take some time. Quote Share this post Link to post Share on other sites More sharing options...
rem7777 Posted January 5, 2016 Report post Posted January 5, 2016 The client provides the updated version number during the next heartbeat discovery. Depending on the schedule of the heartbeat discovery, this might take some time. Thanks Peter - The SCCM primary was upgraded in May last year Quote Share this post Link to post Share on other sites More sharing options...
rem7777 Posted January 6, 2016 Report post Posted January 6, 2016 I've checked a few of the machines reporting client version 5.00.7958.1000. The control panel applet also shows this as the version, so I'm inclined to think that the report is accurate. Any idea how I can troubleshoot the automatic upgrade process? Quote Share this post Link to post Share on other sites More sharing options...
