Thanks, Trevor. That make sense. It just seems with R2, performing the client upgrade is not as intuitive as it has been with SP1 or CU3 where the site installer asked you if you wanted to create a package for your client and console upgrades. And, I can't see using the "Automatic Client Upgrade" feature as being a comprehensive solution. If I recall, I thought I read in past Technet documentation that the "Automatic Client Upgrade" was not recommended to fully upgrade your entire client environment, but rather only after you have performed some mass client package push. In other words, for those the small percentage remaining on the older client version.
Elias On Fri, Jan 24, 2014 at 3:41 PM, Trevor Sullivan <[email protected]> wrote: > Elias, > > > > Yes, I just recently used a ConfigMgr client package to upgrade a customer > from Service Pack 1 to R2. The upgrade process went flawlessly. > > > > I used a wrapper batch file that would: > > > > 1. Kill *ccmsetup.exe* (if running) using *taskkill.exe* > > 2. Launch *ccmsetup.exe* with the */NoService* parameter > > 3. Install Microsoft KB2905002 using *msiexec.exe /update* > > > > There was some issue I ran into while trying to install KB2905002 using > the PATCH property, but I cannot recall what it was. That's why I just used > msiexec.exe > > > > Cheers, > > Trevor Sullivan > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Elias Leal > *Sent:* Friday, January 24, 2014 3:38 PM > *To:* [email protected] > *Subject:* [mssms] R2 client upgrade question > > > > > > I am curious what everyone is doing with R2 client upgrades. > > > > Outside of OSD and before addressing the R2 hotfix KB2905002, I am trying > to figure the best way to upgrade clients from the SP1 CU3 version > (5.00.7804.1400) to the initial R2 version (5.00.7958.1000). > > > > Some observations... > > > > 1. From previous email threads, I've notice recommendations to use > "Automatic Client Upgrade". However, when I enable this feature...there is > wording in the UI that says"Clients in slow or unreliable boundaries will > not be upgraded automatically". > > > > 2. When I installed R2 on my lab primary site, there wasn't an option to > include a client installer package like how we saw with SP1 or CU3 site > installs (unless I missed that). > > > > So, I am trying to confirm if my observations are correct. And if so, what > is everyone doing with client upgrades in slow boundaries? Do we create a > package for them? > > > > Thanks, > > > > Elias > > > > > > > > > > > > > >
