SMS decomission

This topic contains 1 reply, has 2 voices, and was last updated by Avatar yanivfel 13 years ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • Avatar

    I’ve been tasked with removing SMS from a domain we support. I have removed all the site boundaries from within the sms2003 admin console, which should uninstall all the legacy clients (I think!) There are no machines which have the advanced client installed. Is it now as simple as removing from add/remove programs, or is there an uninstall option from the cd which needs to be run? Are there any pitfalls I need to be aware of?

    Seems an easy question but I can find nothing on uninstalling SMS completely, only the client.

    Thanks in advance



    Re: SMS decomission

    HI jem,

    technicly you are on the right track. just remember that whatever you do, you cannot undo the schema extension.

    take a look at the folowing notes, see if anything comes to mind that you haven’t considered:

    Removing a Primary Site
    If you want to remove an SMS 2003 site, use the SMS 2003 Setup.

    To remove a primary site

    From the SMS 2003 CD, run Setup.exe. Or, from the Systems Management Server program group on the site server, run SMS Setup.

    From the Setup Options page, select Remove SMS.

    Click Next to display the SMS Database Deinstallation Options page.

    Clear the Delete the SMS Site Database check box if you do not need to remove the SMS site database, for example, if you plan to reinstall the site server and use the existing site database.

    Click Next, and then click Finish to complete the removal process.

    After you uninstall SMS from a site server, some SMS related items remain, such as files, folders, and registry keys. SMS does not remove those items, primarily in order to allow a subsequent installation of SMS to be associated with the previous installation. In some cases, it can be necessary to completely remove SMS from that computer.

    To completely remove SMS from a site server computer

    • Manually remove the following items:

    • :SMSSetup.log

    • %Windir%System32SMSMsgs

    • %Windir%System32SMSExec_Prochist.dat

    • %Windir%SMSCfg.ini (if SMS 2003 client components are not installed on the computer)

    • C:Documents and Settings – all profiles with an SMS prefix (if the computer is not an SMS 2003 Legacy Client)

    • %Windir%HelpSMS

    • The SMS_CCM folder in the SMS installation drive (if the computer is not an SMS 2003 Advanced Client)

    • The SMSPKG folder (compressed package folder) on the SMS installation drive


    • HKLMSOFTWAREMicrosoftSMS (if an SMS 2003 client is not installed on the computer)

    • HKLMSOFTWAREMicrosoftNAL (if an SMS 2003 client is not installed on the computer)

    • The SMS namespace from WMI (RootSMS)

    • Depending on the SMS 2003 security mode, the domain or local computer can contain various accounts that are related to SMS. The number and type of accounts depends on the security mode with which the site was configured. A site configured with standard security generates more accounts than a site configured with advanced security.

    Remove the following accounts (which exist for both security modes): SMS Admins, SMS Reporting Users (if an SMS reporting point was created), SMS_SiteSystemToSiteServerConnection_sitecode, SMS_SiteSystemToSQLConnection_sitecode, and SMS_SiteToSiteConnection_sitecode. If the site was configured with standard security, there can be additional SMS user accounts [such as the SMS Service account (SMSService, by default), SMSClient_sitecode, and SMSServer_sitecode].

    When you uninstall SMS 2003, all installed feature packs are also uninstalled.

    Removing a Secondary Site
    The process for uninstalling a secondary site is similar to that for uninstalling a primary site. You can initiate an uninstall by running setup from the SMS 2003 source CD as described in Removing A Primary Site, or by running the Delete a Secondary Site Wizard from the SMS Administrator console for the parent site of the secondary site that you want to remove.

    To remove a secondary site using the Delete a Secondary Site Wizard

    In the SMS Administrator console, navigate to the secondary site entry in the Site Hierarchy node of the console tree.

    Right-click the secondary site entry and select Delete to run the Delete a Secondary Site Wizard.

    Click Next to display the Choose Whether to Delete or Deinstall wizard page.

    Select Deinstall to completely remove the secondary site installation. Select Delete to remove all references to the secondary site from its parent, while leaving the secondary site server installation intact. Select the Delete option if, for example, the secondary site server is no longer functioning or no longer exists and cannot respond to commands to uninstall. Selecting Deinstall, in this case, generates error messages and the uninstall process fails. The Delete option bypasses the uninstall portion of the process and simply removes the reference of the secondary site from the parent site. You must then manually remove the secondary site software from the secondary site server.

    Click Finish to begin the uninstall process.

    Refresh the SMS Administrator console. When the secondary site entry is no longer displayed, the secondary site removal process is complete. Follow the site server clean-up steps outlined in Removing a Primary Site earlier in this section.

    When using an Administrator console at a parent site to uninstall a child secondary site, the secondary site’s object might not be removed from Active Directory. If the site’s SMS-Site- object remains in Active Directory, than you need to manually remove it.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.