asked on
DCPROMO Order
I am adding a new DC to an existing 2003 forest. Existing has 1 GC and 5 DC's at branch offices connected over MPLS WAN. We use Sites and services to replicate changes. Do I join domain at main site, run dcpromo and let AD replicate, then change IP subnet and setup sites for AD replication...or I have the option of hanging new server off a local firewall and running dcpromo from the new subnet. I thought this might try to pull AD from a BO.. Hope question and explanation is sufficient..Thanks in advance
Active DirectoryWindows Server 2003
Last Comment
Awinish
Personally i would build the server at the main site, and set up the IP address on the remote subnet. The run DCPROMO from the remote site.
ASKER
AD is not that large. If I'm going to run it from the branch should I join the domain first dcpromo will take care of that and will it install DNS? Thanks.
What I usually do is image the DC at the main site join to the domain and ship to the branch. Then run DCPromo from the branch site. If you are worried about the bandwidth of the promo you could put a copy of the system state from another DC on the server and run dcpromo /adv
Its not good practices to join system into domain & then promote as DC, dcpromo should be directly run on server & you should not change IP because mostly DC's are heart of domain & they should not be going through changes or testing.
Awinish, Do you have any documentation that says it is not good practice to run DCPromo on domain joined servers?
There is nothing wrong with changing the IP of a Domain Controller. You need to make sure you follow the proper procedures.
http://technet.microsoft.com/en-us/library/cc758579(WS.10).aspx
http://technet.microsoft.com/en-us/library/cc794931(WS.10).aspx
There is nothing wrong with changing the IP of a Domain Controller. You need to make sure you follow the proper procedures.
http://technet.microsoft.com/en-us/library/cc758579(WS.10).aspx
http://technet.microsoft.com/en-us/library/cc794931(WS.10).aspx
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Yes, i do believe certain circumstances require us to do changes changes,but making changes on dc esp when users, application & servers depends heavily on it, personally i don't feel comfortable.
So better planning is the key to road ahead, even though its small environment, still we should not make practice, that's what i wanted to guide the author.
So better planning is the key to road ahead, even though its small environment, still we should not make practice, that's what i wanted to guide the author.
I would probably just run DCPromo at the branch with only that many DCs.
You could also take a systemstate backup of one DC restore to a seperate directory on the new DC and run dcpromo /adv and point to the file while the DC is in the branch.