pxedave Posted February 16, 2012 Report post Posted February 16, 2012 Folks, anyone got any thoughts on the best way of automating the uninstall of the SMS client and the install of SCCM 2012? I'm going to have to face this one at some point. I had hoped that deploying the new client would remove the old one but the deployment fails (with an upgrade version error); you have to uninstall the SMS client in advance. I'm thinking that deploying an SMS program that creates a local scheduled task to perform the job might be the neatest. Wouldn't it have been nice if MS had of added some /uninstallall switch or something rather than assume an upgrade... Quote Share this post Link to post Share on other sites More sharing options...
pxedave Posted February 21, 2012 Report post Posted February 21, 2012 I just noticed there is a "always install client" tick box when pushing the SCCM 2012 client from the console. I can't remember if I tried this. Maybe ticking this will uninstall the old SMS client for me(?) I'll try it and report back... Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted February 21, 2012 Report post Posted February 21, 2012 nope it cannot uninstall the SMS 2003 client, you'll see that logged in ccmsetup.log, it can only deal with ConfigMgr Client's from 2007 and onwards Quote Share this post Link to post Share on other sites More sharing options...
pxedave Posted February 22, 2012 Report post Posted February 22, 2012 OK it looks like you really do need to remove the SMS client before attempting a push of 2012 (I'm using doing this manually using "ccmclean.exe /removehistory"). It was worth a try. Anyone come up with ways to automate the uninstall of SMS / install of SCCM yet? Quote Share this post Link to post Share on other sites More sharing options...
joekokey Posted March 7, 2012 Report post Posted March 7, 2012 We're trying to use Software Update Point-based installation and it appears that the uninstallation of SMS 2003 works... Doing some more tests to validate this. Anybody else tried this? <![LOG[Current client version '2.50.4253.3000' doesn't meet the minimum in-place upgradable version '5.00.7685.0000'.]LOG]!><time="00:24:48.996+480" date="02-27-2012" component="ccmsetup" context="" type="1" thread="2860" file="msiutil.cpp:638"> <![LOG[upgrade code '{252DA259-82CA-4177-B8D0-49C78937BA3E}': product = '{4A39A27F-005B-407E-8CF5-F4D8065658E4}', installed = 1, version = 2.50.4253.3000]LOG]!><time="00:24:52.386+480" date="02-27-2012" component="ccmsetup" context="" type="0" thread="2860" file="msiutil.cpp:1242"> <![LOG[A SCCM client with version '2.50.4253.3000' is detected. It's smaller than the minimum upgradable version '5.00.7685.0000' so current client will be uninstalled.]LOG]!><time="00:24:52.386+480" date="02-27-2012" component="ccmsetup" context="" type="1" thread="2860" file="util.cpp:451"> <![LOG[source location is not under software distrubtion cache folder. No need to back up source.]LOG]!><time="00:24:52.401+480" date="02-27-2012" component="ccmsetup" context="" type="0" thread="2860" file="preuninstallcopysource.cpp:51"> <![LOG[No current reboot settings to backup.]LOG]!><time="00:24:52.401+480" date="02-27-2012" component="ccmsetup" context="" type="0" thread="2860" file="uninstallpreservereboot.cpp:66"> <![LOG[A newer version client is being installed over an old client and uninstalling old client is necessary. Uninstalling the old client.]LOG]!><time="00:24:52.401+480" date="02-27-2012" component="ccmsetup" context="" type="1" thread="2860" file="ccmsetup.cpp:7248"> <![LOG[uninstalling product '{4A39A27F-005B-407E-8CF5-F4D8065658E4}'.]LOG]!><time="00:24:52.401+480" date="02-27-2012" component="ccmsetup" context="" type="1" thread="2860" file="msiutil.cpp:1141"> <![LOG[Running installation package Product: {4A39A27F-005B-407E-8CF5-F4D8065658E4} Log: C:\WINDOWS\ccmsetup\client.msi_uninstall.log Properties: ]LOG]!><time="00:24:52.401+480" date="02-27-2012" component="ccmsetup" context="" type="1" thread="2860" file="msiutil.cpp:1053"> Quote Share this post Link to post Share on other sites More sharing options...
pxedave Posted March 7, 2012 Report post Posted March 7, 2012 We're trying to use Software Update Point-based installation and it appears that the uninstallation of SMS 2003 works... Doing some more tests to validate this. Anybody else tried this? <![LOG[Current client version '2.50.4253.3000' doesn't meet the minimum in-place upgradable version '5.00.7685.0000'.]LOG]!><time="00:24:48.996+480" date="02-27-2012" component="ccmsetup" context="" type="1" thread="2860" file="msiutil.cpp:638"> <![LOG[upgrade code '{252DA259-82CA-4177-B8D0-49C78937BA3E}': product = '{4A39A27F-005B-407E-8CF5-F4D8065658E4}', installed = 1, version = 2.50.4253.3000]LOG]!><time="00:24:52.386+480" date="02-27-2012" component="ccmsetup" context="" type="0" thread="2860" file="msiutil.cpp:1242"> <![LOG[A SCCM client with version '2.50.4253.3000' is detected. It's smaller than the minimum upgradable version '5.00.7685.0000' so current client will be uninstalled.]LOG]!><time="00:24:52.386+480" date="02-27-2012" component="ccmsetup" context="" type="1" thread="2860" file="util.cpp:451"> <![LOG[source location is not under software distrubtion cache folder. No need to back up source.]LOG]!><time="00:24:52.401+480" date="02-27-2012" component="ccmsetup" context="" type="0" thread="2860" file="preuninstallcopysource.cpp:51"> <![LOG[No current reboot settings to backup.]LOG]!><time="00:24:52.401+480" date="02-27-2012" component="ccmsetup" context="" type="0" thread="2860" file="uninstallpreservereboot.cpp:66"> <![LOG[A newer version client is being installed over an old client and uninstalling old client is necessary. Uninstalling the old client.]LOG]!><time="00:24:52.401+480" date="02-27-2012" component="ccmsetup" context="" type="1" thread="2860" file="ccmsetup.cpp:7248"> <![LOG[uninstalling product '{4A39A27F-005B-407E-8CF5-F4D8065658E4}'.]LOG]!><time="00:24:52.401+480" date="02-27-2012" component="ccmsetup" context="" type="1" thread="2860" file="msiutil.cpp:1141"> <![LOG[Running installation package Product: {4A39A27F-005B-407E-8CF5-F4D8065658E4} Log: C:\WINDOWS\ccmsetup\client.msi_uninstall.log Properties: ]LOG]!><time="00:24:52.401+480" date="02-27-2012" component="ccmsetup" context="" type="1" thread="2860" file="msiutil.cpp:1053"> Interesting. I'm guessing you're using a seperate WSUS setup to do this other than the SUP I've just configured in my SCCM 2012 console (as per the guides) as surely you'd need the SCCM client on the PC first for it to receive SUP updates via SCCM (?) Sorry, I'm new to SUP / WSUS... Quote Share this post Link to post Share on other sites More sharing options...
pxedave Posted March 13, 2012 Report post Posted March 13, 2012 OK since replacing my SCCM 2012 RC1 server with RC2 I happened to try this again (a remote client push to a machine which has SMS 2003 client installed) expecting it to fail... but it worked. The log file (c:\windows\ccmsetup\ccmsetup.log) shows that the old client was detected but now it says it is going to continue with the upgrade (although it does state this is unsupported, probably because SMS is so old). I'm going to get a cup of tea to celebrate and try this again just to make sure Quote Share this post Link to post Share on other sites More sharing options...
