Got a call today from a customer that wanted to phase out an old server. There’s a physical box that’s old as dirt. So they have a virtual setup and I built a domain controller on it and joined it to the domain…
There is a video below but I will roughly go through the steps…
I loaded the ISO of Server 2008 R2 as CD/DVD
Existing Server (Server 2008 X64)
- Open CMD Prompt
- C:\Users\Administrator>d:\support\adprep\adprep.exe /forestprep
- This will prepare the forest
- C:\Users\Administrator>d:\support\adprep\adprep.exe /domainprep
- This will prep the Domain
New Server (Server 2008 R2)
- Built a server 2008 R2
- Joined it to the domain
- Promoted the Server to a DC (ran dcpromo)
- Global Catalog
Transferring the roles (perform these on the 2008 R2 Server)
- Open CMD Prompt (type the following commands)
- regsvr32 schmmgmt.dll
- connect to server DC02
- transfer role
- Transfer infrastructure master
- Transfer naming master
- Transfer PDC
- Transfer RID master
- Transfer schema master
- netdom query /domain:contoso fsmo
The Active Directory Installation Wizard (Dcpromo.exe) assigns all 5 FSMO roles to the first domain controller in the forest root domain.
We recommend that you transfer FSMO roles in the following scenarios:
- The current role holder is operational and can be accessed on the network by the new FSMO owner.
- You are gracefully demoting a domain controller that currently owns FSMO roles that you want to assign to a specific domain controller in your Active Directory forest.
- The domain controller that currently owns FSMO roles is being taken offline for scheduled maintenance and you need specific FSMO roles to be assigned to a “live” domain controller. This may be required to perform operations that connect to the FSMO owner. This would be especially true for the PDC Emulator role but less true for the RID master role, the Domain naming master role and the Schema master roles.