Adding a Windows Server 2008 R2 x64 domain controller
I am trying to add a Windows Server 2008 R2 64bit server as a domain controller to a network that has windows server 2003 domain controllers. What are the steps that I need to take to do this? I can't find adprep and forestprep on our disk. We are running our DC's on Citrix XenCenter as virtual machines.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
mkline71:
I tried running the adprep32 but it didn't work, when I tried to promote the 2008 server, it still shows that it hasn't been done.
I tried running the adprep32 but it didn't work, when I tried to promote the 2008 server, it still shows that it hasn't been done.
ASKER
mkline71:
One more thing, which server do I need to run adprep and forestprep on? I've run it on our windows 2003 DC, but we have a total of 3 DC's, all on 2003.
One more thing, which server do I need to run adprep and forestprep on? I've run it on our windows 2003 DC, but we have a total of 3 DC's, all on 2003.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
1.) On existing PDC run "adprep /forestprep" and "adprep /domainprep"
2.) Join new server to the domain and install DNS, and Global Cert roles.
3.) Make the new server a BDC
4.) Reccomend waiting 1-2 days as BDC role to make sure all syncs have happened.
5.) Run dcpromo on new server and set it as PDC.
You can use netdom query fsmo to list the roles and verify after all is done.
2.) Join new server to the domain and install DNS, and Global Cert roles.
3.) Make the new server a BDC
4.) Reccomend waiting 1-2 days as BDC role to make sure all syncs have happened.
5.) Run dcpromo on new server and set it as PDC.
You can use netdom query fsmo to list the roles and verify after all is done.
3.) Make the new server a BDC
4.) Reccomend waiting 1-2 days as BDC role to make sure all syncs have happened.
There is no BDC...that went out with Windows NT
You don't need to wait that long for replication.
Thanks
Mike
4.) Reccomend waiting 1-2 days as BDC role to make sure all syncs have happened.
There is no BDC...that went out with Windows NT
You don't need to wait that long for replication.
Thanks
Mike
mkline1 is correct, just didnt know full structure. Basically its just another DC in the list. As for time in replication, I always allow extra time in case hidden errors arise, but a few hours will generally be enough.
ASKER