Replacing old SMS Servers with New Servers

[coulters]

We are going to be replacing an existing SMS servers with new SMS servers. The new servers will have a different name and different site code. We are NOT keeping the existing database, but may want to import Collections/Packages, if possible. Is there any documentation or advice on the proper way to do this? Also, one of the existing SMS servers has the same Site Code as the new server. What problems could arise from this? Any help or documentation would be greatly appreciated!

 

[tbrennans]

Are you upgrading to SCCM?

http://technet.microsoft.com/en-us/library/bb632845.aspx

 

[Abhirag]

I am sure this is not SCCM. In SMS changing the server name and site code is not supported by MS. If you install with new name and site, you loose everything including your collection/Packages.

Same site code should work only in seperate SMS Hierarchy and Seperate domain/Forest.

You must shutdown the other SMS siteserver with same site code and manually delete the entries from AD (Ofcourse if AD Schema is extended and SMS is configured to publish in AD)

 

[coulters]

Unfortunately not upgrading to SCCM. Same domain/forest. So basically, shutdown all SMS services on old server with same site code, delete entries in AD. Is there anything else? I know you can do this in SCCM, but in 2003, if old and new servers have different site codes, can the old be set as the parent of the new and all the collections/packages will flow down? Not too concerned about clients. Thanks for the input.

 

[Abhirag]

Yes, if the new installation is with new site code you can always configure it to report to old one.

Collections/Package/Advertisement will flow from top to bottom.

Client also shouldnt be an issues as long as boundaries are configured properly and you have proper site systems (MP/DP) in place in all sites.