marksheeks
asked on
Move 2003 AD including GC and all FSMO to new subnet, then move Exchange.
I have an AD2003 native environment with (2) servers at our seattle site. DC1 is the GC and all FSMO roles with AD integrated DNS. This is the one which Exchange coughs over when it's rebooted. The other server (DC2) is AD integrated DNS and DHCP server holding all the scopes for this site. I have to move both and then our Exchange Cluster (2 nodes in active/standby) to a new subnet. We will be routing between the 2 subnets until the migration is complete. The DC's are replicating with other pgysical sites across WAN links. My concerns involve the steps and sequencing for DNS reverse lookup zones, replication partners, standby partners (never designed in the first place currently) and of course, the potential for breakign Exchange. I wish I could offer more than 500 for this somehow. I've read some of the links and other solutions already. Please don't point me to MS KB's unless they truly apply to exactly my situation. Thanks all!!!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Awesome, thank you!
Is ther a preferred sequence to FSMO roles and/or should GC be enabled first please? Do you have an opinion. My impression is that the sequence does not matter.
Also, is it necesary to do anything in sites/svcs? Recommend any command line tools for verifying replication, GC operation? Thanks pal.
Is ther a preferred sequence to FSMO roles and/or should GC be enabled first please? Do you have an opinion. My impression is that the sequence does not matter.
Also, is it necesary to do anything in sites/svcs? Recommend any command line tools for verifying replication, GC operation? Thanks pal.
ASKER
to answer arnolds questions; it's all internal. we're redoing our vlans.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thanks all. Very helpful! Again, I wish I had more points.
Are you mirating from 192.168.x.x to 172.z.x.y?
Or is the change necessitated because of a change in ISPs?