I would add SMSMP property yo your cmd line so clients know directly which no to communicate with. /MP: switch is to download bits. On Jan 22, 2014 7:47 AM, "John M" <[email protected]> wrote:
> Thanks Ivan, > I'll add that to the command line. Any thoughts on the upgrade weirdness? > > > From: [email protected] > > To: [email protected] > > Subject: RE: [mssms] Using SCCM 2007 to upgrade clients to 2012 weirdness > > Date: Wed, 22 Jan 2014 15:05:13 +0000 > > > > One thing you'll need is to add "RESETKEYINFORMATION=TRUE" to the > install command line. This is from personal experience going from 2007 to > 2012 clients. It was also recommended by a Sr. PFE recently which is to say > it's possibly a best practice. > > > > The client install needs to forget the old SMS certificate and get the > new one from the MP. > > > > We did not need it when going from SCCM 2012 client RTM to SP1. > > > > > > Ivan Lindenfeld > > Sr. Systems Engineer > > Enterprise Deployment / SCCM > > Fidelity National Financial | Jacksonville, Florida > > > > > > -----Original Message----- > > From: [email protected] [mailto: > [email protected]] On Behalf Of John > > Sent: Wednesday, January 22, 2014 10:00 AM > > To: [email protected] > > Subject: [mssms] Using SCCM 2007 to upgrade clients to 2012 weirdness > > > > I am transitioning from 2007 to 2012 R2 and am using a 2007 package to > do so, my command line for my upgrade package reads: > > > > ccmsetup.exe /mp:<FQDN of Site Server> SMSSITECODE=XXX FSP=<FQDN of Site > > Server> DNSSUFFIX=Mydomain.com > > > > On some of the clients it works pretty much right away, but for some > groups of machines, it shows as successful (exit status 0) and yet, very > strangely, if I log on to one of those machines, it still shows the SCCM > > 2007 client in the control panel. > > > > For those machines I will see many entries in the ccmsetup log of: > > > > *Failed to get DP locations as the expected version from MP '<FQDN of > Site Server>'. Error 0x80072ee2** > > * > > However, if I wait a few hours or even days, it will show . > > > > *GET 'HTTP://<FQDN of Site Server>/CCM_Client/ccmsetup.cab' > > ccmsetup 1/21/2014 8:29:03 AM 4292 (0x10C4)** > > **Failed to send HTTP request. (Error at WinHttpSendRequest: 12002) > > ccmsetup 1/21/2014 8:29:24 AM 4292 (0x10C4)** > > **Next retry in 10 minute(s)... ccmsetup 1/21/2014 8:29:24 AM > > 4292 (0x10C4)** > > * > > *GET 'HTTP://<FQDN of Site Server>/CCM_Client/ccmsetup.cab' > > ccmsetup 1/21/2014 8:39:25 AM 4292 (0x10C4)** > > **C:\Windows\ccmsetup\ccmsetup.cab is Microsoft trusted. ccmsetup > > 1/21/2014 8:39:34 AM 4292 (0x10C4)** > > **Successfully extracted manifest file C:\Windows\ccmsetup\ccmsetup.xml > > from file C:\Windows\ccmsetup\ccmsetup.cab. ccmsetup 1/21/2014 > > 8:39:34 AM 4292 (0x10C4)* > > > > The install will then proceed and looks like it's successful, but then, > near the bottom, it has this: > > > > *Client installation will be skipped because required version of client > > is already installed. ccmsetup 1/21/2014 10:45:54 PM 3592 (0x0E08)* > > > > > > So, in a nutshell, what appears to be happening is: > > The package advertised by SCCM 2007 is run on all the client machines > They all run the package successfully (exit status 0) I change the > boundaries from SCCM 2007 to SCCM 2012 Some machines show up right away in > the SCCM 2012 console as client=yes with proper sitecode Most others still > have the SCCM 2007 client in control panel, and errors in the ccmsetup log > about failed to get DP locations After waiting some time period, they start > to work and download the ccmsetup.cab file The installation looks like it > then proceeds, but again, the SCCM 2007 client still shows up in control > panel > > > > On one machine I was able to log on and watch this, and after I > rebooted, the SCCM 2012 client appeared in the control panel and it looked > ok. > > > > Has any one got any light to shed on this? Should it take this long to > complete? Is my command line for upgrading flawed? Should the old SCCM > client still appear in control panel? Should I put in a reboot after the > client installs? > > > > Any and all thoughts are appreciated. > > > > Cheers > > John > > > > > > > > > >
