I set up automated collections to turn around and deploy the CU's so I don't have to worry about it...
Chris Nackers Microsoft MVP - Enterprise Client Management Email: [email protected]<mailto:[email protected]> Nackers Consulting Services, LLC From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Wednesday, May 21, 2014 2:41 PM To: [email protected] Subject: [mssms] RE: R2 CU1 upgrade - still older client version There's no supported way to do this. Client push always installs the major version. There are many caveats to the first statement though. Ultimately, using SCUP or the client update package created during the CU1 installation is the recommended way even though they both happen after the major version installation. J ________________________________ From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Lutz, Ken <[email protected]<mailto:[email protected]>> Sent: Wednesday, May 21, 2014 1:30 PM To: 'SMS List' Subject: [mssms] R2 CU1 upgrade - still older client version Hi everyone. I just installed CU1 for SCCM 2012 R2. I deployed the client to a small test group of machines and saw one machine that failed to do the client upgrade. I then went to the console and did a manual push to just that machine. I then watched the ccmsetup.log on the workstation. It installed just fine, but it installed version 5.00.7958.1000 not what I was expecting - version 5.00.7958.1203. My question is what do I need to do to get the client version to be the CU1 version when I do a push from the console? Thanks. [cid:[email protected]] Ken Lutz Senior Systems Administrator Information Systems Department Spokane County 815 N. Jefferson Spokane, Washington 99260
