locked
Complete removal of SMS advanced client RRS feed

  • Question

  • Hello.

    We are currently using SMS 2003 and are planning to upgrade to SCCM, unfortunatly during the SCCM implementation the SCCM client was released to all of the workstations which we manage which resulted in the SMS client being upgraded.  All clients then started to report back the SCCM server which was was far from ideal!

    We have started to remove the SCCM agent using ccmsetup /uninstall which appears to be working fine (if this is incorrect, please let me know).  Once the SCCM agent is removed we have started to push the SMS client out again through the SMS console and this appears to be working also however a number of machines don't appear to be installing the agent (according to the console).

    After further investigation some clients had the agent installed but the console was not identifying this, this was resolved by running the ccmdelcert utility.  I also ran the built in report 'Computers that may share the same SMS unique ID' and the result was very disheartening.  Some of the duplicate guids aere probably caused when images were taken from a master machine which had the client installed on.

    As it stands I am not happy with the health of our clients, one issue gets understood and another one is identified.  I would therefore like to remove all traces of the SMS client from the workstations (to get them to the state they were in pre SMS client) and re-install.  After reading various posts ccmclean /all appears to be the utility to use, I ran this on a test machine and noticed that smscfg.ini was left. 

    I would like to know what the correct process is to remove the SMS client and all traces of it to allow me to push the advanced client out to ensure the installs on each and every workstation have a clean bill of health, including a unique GUID.  I was concerned with smscfg.ini being left on the workstation in case this resulted in the previous GUID being allocated.

    Many thanks

    Nigel

    Thursday, May 26, 2011 4:15 PM

Answers

All replies

  • Hi - Checkout the below MS article which states about SMS 2003 client removal.

    http://support.microsoft.com/kb/826842

    The best way is to use ccmcleanup.exe in combination with PSTools (http://technet.microsoft.com/en-us/sysinternals/bb897553)


    Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Friday, May 27, 2011 2:04 AM
  • ccmcleanup.exe


    Just to avoid any confusion: that tool does not exist. It's called ccmclean.exe instead and is found in SMS 2003 Toolkit 2: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=61e4e21f-2652-42dd-a04d-b67f0573751d
    Torsten Meringer | http://www.mssccmfaq.de
    Friday, May 27, 2011 7:14 AM
  • Thanks both for your replies.

    I have used ccmclean /all from the toolkit but noticed that smscfg.ini was left on the workstation, does anybody know if this is expected behaviour?

    My concerns are that if this file is left on, will the guid be picked up from within the file or will the file be updated and a new guid allocated when the client is pushed out again?

    Thanks again.

    Nigel

    • Proposed as answer by Tom Watson Wednesday, June 1, 2011 5:29 PM
    • Unproposed as answer by Tom Watson Wednesday, June 1, 2011 5:29 PM
    Friday, May 27, 2011 7:57 AM
  • You are correct.  However, simply deleting the SMSCFG.ini after a Ccmclean does seem to work, in that a new GUID gets generated once the client is reinstalled.


    Regards,
    Tom Watson,
    E-Mail: Tom_...@...
    Blog: http://myitforum.com/cs2/blogs/tom_watson
    Wednesday, June 1, 2011 5:32 PM
  • If left, the new client install will use the same GUID.
    Wally Mead
    Friday, June 3, 2011 10:02 PM