Re: Moving SMS server to a new domain
- From: Rob Birchmeier <RobBirchmeier@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 25 Apr 2008 07:04:01 -0700
OH, thanks for the clarification. I agree take the opportunity to rebuild.
"Garth" wrote:
He is not rebuilding SMS, he is re-using the SMS server. I could see that.
there could be allot of problems do this.
For example:
• SID issue
• SQL issues (generally SQL does not like being renamed, yes you
can do it but there are steps that need to be done in order to make it work
again)
• ResourceID issues
Why not rebuilt the server from scratch? Thsi is alos a good tiem to upgrade
to ConfigMgr too, if you can.
"Rob Birchmeier" <Rob Birchmeier@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C3FB6461-533E-47BE-808F-F3D1FDA8D23A@xxxxxxxxxxxxxxxx
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
- References:
- Moving SMS server to a new domain
- From: garynreese
- RE: Moving SMS server to a new domain
- From: Rob Birchmeier
- Re: Moving SMS server to a new domain
- From: Garth
- Moving SMS server to a new domain
- Prev by Date: RE: Moving SCCM 2007
- Next by Date: RE: Moving SCCM 2007
- Previous by thread: Re: Moving SMS server to a new domain
- Next by thread: SMS 2003 SP3 - Secondary site install fails with logon failure
- Index(es):
Relevant Pages
|
Loading
