Moving SMS server to a new domain


We will move all of our servers and workstations, SMS included, to a new
domain in three weeks. I thought through the process for moving the SMS
server, and found an almost identical process. I also discovered that
Microsoft does not support this, recommends the site be completely removed
and reinstalled.

Not sure what the stop-the-clock issue is here. About to open a case with
support to discover why. Computer accounts will change and change SIDs but
those can be switched so that they should work in the new domain where every
machine would then reside.

Anyone had experience with this situation? It does seem like a sit that
would often come up.

Here is the procedure I found that mirrors my initial thoughts on this:



1. Remove roaming boundaries from all servers (removes the
mSSMSRoamingBoundaryRange from SystemsManagement folder in AD)

2. Remove SLP, MPs and DPs (removes mSSMSServerLocatorPoint and
mSSMSManagementPoint from SystemsManagement folder in AD)

3. Turn off Publish ID in AD

4. Reboot SMS Servers once removals have completed

5. Move servers to new domain

6. Ensure SMS has rights to SystemsManagement folder in AD

7. Add server accounts to appropriate groups

8. Turn on Publish ID in AD (creates mSSMSSite in SystemsManagement folder
in AD?????)

9. Add roaming boundaries to all servers (creates the
mSSMSRoamingBoundaryRange in SystemsManagement folder in AD)

10. Add SLP, MPs and DPs (creates mSSMSServerLocatorPoint and
mSSMSManagementPoint in SystemsManagement folder in AD)

11. Reboot SMS Servers


.

Relevant Pages

  • Re: Moving SMS server to a new domain
    ... 10 NASA centers with seperate forests and seperate SMS infrastructures ... I figured SMS wont migrate and will have to be rebuilt ... We will move all of our servers and workstations, SMS included, to a new ... mSSMSRoamingBoundaryRange from SystemsManagement folder in AD) ...
    (microsoft.public.sms.setup)
  • Moving SMS server to a new domain
    ... We will move all of our servers and workstations, SMS included, to a new ... I thought through the process for moving the SMS ... mSSMSRoamingBoundaryRange from SystemsManagement folder in AD) ... mSSMSManagementPoint from SystemsManagement folder in AD) ...
    (microsoft.public.sms.admin)
  • Re: Moving SMS server to a new domain
    ... He is not rebuilding SMS, he is re-using the SMS server. ... sms servers in the 10 trusted forest still manage the clients. ... I figured SMS wont migrate and will have to be rebuilt using ... mSSMSRoamingBoundaryRange from SystemsManagement folder in AD) ...
    (microsoft.public.sms.setup)
  • Re: subnet inclusion in the AD site boundary is not being seen by
    ... Are you sure the other 50 servers weren't manually assigned? ... Windows Server System MVP - SMS ... subnet to the SMS site boundaries - even though their subnet is already part ... the sms client is in the correct ad site ...
    (microsoft.public.sms.setup)
  • Opinions: Is SMS an option for this scenario?
    ... client machines, plus servers. ... So my question is, without you knowing all of the details, could SMS ... foot opinions on how appropriate SMS might be in our situation. ...
    (microsoft.public.sms.admin)
Loading