Rename an SMS Site

Not long ago, I had to rename an SMS Site, here are the steps I used, from Jase T. Wolfe's blog.

  1. If an SMS Primary Site server, stop the SMS_SITE_COMPONENT_MANAGER, SMS_EXECUTIVE, SMS_SERVER_LOCATOR_POINT, and SMS_SQL_MONITOR services.
  2. If an SMS Secondary Site server, stop the SMS_SITE_COMPONENT_MANAGER and SMS_EXECUTIVE services.
  3. Open the "\SMS\inboxes\sitectrl.box\sitectrl.ct0" site control file.
  4. Search for the section "BEGIN_SITE_DEFINITION".
  5. Within this section, locate the third value, which is the site name.
  6. Change this value to the new site name, leaving the brackets intact.
  7. Do not change any other values.
  8. Save the "\SMS\inboxes\sitectrl.box\sitectrl.ct0" site control file.
  9. Open RegEdit and find HKLM\Software\Microsoft \SMS\Identification.
  10. Change the Site Name value to the new site name.
  11. Done!

Comments

Anonymous said…
Thanks for this post, it is great
March 29, 2011 at 2:18 PM
Anonymous said…
thanks to the author for taking his time on this one.
April 2, 2011 at 1:26 AM
Post a Comment

Popular posts from this blog

SMS "Program failed (run time exceeded)" 10070

When a program fails due to error 10070, it does so because the Run Time was Exceeded. SMS Allows a program to run for 12 hours, afterwhich it will issue the failed status message if the program hasn't completed successfully. Note: The Maximum allowed run time within program properties is generally a guide for users running the program themselves, and is not enforced.
Read more

SMS "Waiting for User Condition" 10036

Status Message ID 10036, or "Waiting for User Condition" can occasionally grind advertisements to a halt. Make sure the environment and user condition settings for a particular program have been configured appropriately and are not excluding a large portion of your intended audience. Related Articles SMS WQL for All Clients where Last Status is Waiting for User Condition SMS Status Message ID's
Read more

SMS "Waiting for content" 10035

Status Message ID 10035, or "Waiting for content" is a common error which can drive you up the wall when testing a package deployment. Have you checked your site boundaries? Often a client is located in a IP Subnet which hasn't been configured within Site or Roaming Boundaries. Has the software been deployed to the clients local DPs? Check the reports and console, make sure the package has been deployed and is available to the clients. Is the advertisement configured for download and execute? Check the DP, make sure BITS is enabled, and the web site is functioning properly. Have you checked the logs? Start with the cas.log and execmgr.log on the client computer. Related Articles Clients do not send a status message when an advertised program is disabled in Systems Management Server 2003 SMS Status Message ID's
Read more