RE: Moving SMS server to a new domain

Gary,
What part does Microsoft not support? I am working on a project to migrate
10 NASA centers with seperate forests and seperate SMS infrastructures into 1
forest but still keep 10 seperate SMS infrastructures.

Our current plan is to migrate users and wkstns first and let the current
sms servers in the 10 trusted forest still manage the clients. Then ~8
months later come back and migrate all resources, including SMS into the
single forest. I figured SMS wont migrate and will have to be rebuilt using
the process you detailed.

"garynreese" wrote:


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: Require some documentation whether SMS is supported across mul
    ... no. SMS is pretty flexible. ... secondary in a different forest, but you can have a primary site in one ... the accounts and groups used by SMS ... domain or do i have to install child primaries? ...
    (microsoft.public.sms.misc)
  • Re: Design question - AD/SMS sites
    ... You an have an SMS site hierarchy span un-trusted forests. ... Ensure clients are assigned only to a site in their forest. ... > installation across a couple of dozen different small business customers. ...
    (microsoft.public.sms.setup)
  • Re: sms 2003 advance clients in different AD forest ?
    ... When I try to deploy the Advanced Client to workstations in the other domain that the sms server is not located in, ... sms Primary server in Forest A. ...
    (microsoft.public.sms.setup)
  • Re: SMS 2003 across multiple AD domains
    ... Answer on your first inline question: I have SMS 2003 running in advanced ... security mode with advanced clients only. ... forest one domain only, with anywhere from 20-50 computers where i would ... > There is also some content about multiple forests with SMS in the Security ...
    (microsoft.public.sms.admin)
  • Re: sms 2003 advance clients in different AD forest ?
    ... I also have 2 forests with a 2 way transitive trust between the domains, sms ... When I try to deploy the Advanced Client to ... workstations in the other domain that the sms server is not located in, ... sms Primary server in Forest A. ...
    (microsoft.public.sms.setup)
Loading