Ivan,
Yes, sir. It's just a precaution, if nothing else. During my development / testing period, I would regularly come across cases where I invoked ccmsetup.exe asynchronously, and instead meant to launch it synchronously. In those cases, I'd have to kill the async ccmsetup.exe (which was running as a service, and probably just sleeping, waiting for content), to allow the synchronous invocation to run successfully. As long as there aren't any client installations or uninstallations running, killing ccmsetup.exe should be relatively safe. Even then, ccmsetup.exe simply calls out to other processes (eg. msiexec.exe, prerequisite files, etc.), so it's not like you're interrupting any installation itself, just the installation wrapper. Cheers, Trevor Sullivan From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Lindenfeld, Ivan Sent: Friday, January 24, 2014 3:46 PM To: mssms@lists.myitforum.com Subject: RE: [mssms] R2 client upgrade question Trevor, Curious as to why you killed CCMSETUP first? As a best practice just in case it's running still from a previous attempt? Thanks. Ivan Lindenfeld From: listsad...@lists.myitforum.com <mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Trevor Sullivan Sent: Friday, January 24, 2014 4:41 PM To: mssms@lists.myitforum.com <mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] R2 client upgrade question 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: listsad...@lists.myitforum.com <mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Elias Leal Sent: Friday, January 24, 2014 3:38 PM To: mssms@lists.myitforum.com <mailto:mssms@lists.myitforum.com> 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
