Current Environment
Microsoft Active Directory 2008R2 with Exchange 2010
Requirements for migration
1- New Windows Server 2012 R2 server to be prepared.
2- Join the new Server to the old Dc.
First I will be Installing the new Server windows 2012 R2 which I will migrate all the roles to after preparing it and joining it to the domain as in the following snapshots.
Below I will add the server to the current existing DC.
Here I will leave the default settings but will have to enter the DSRM password as it’s mandatory.
to migrate the AD Operations Master roles. The simplest way to move these roles is via PowerShell. On Server 2012 AD PowerShell modules, this can be done from anywhere. Simply run the following command to view you current configuration, and change them:
PS C:\> netdom query FSMO
In order to Migrate all the roles from the DC (Kibtek.local) to the new Server I will use the following powershell cmdlet.
Move-ADDirectoryServerOperationMasterRole -identity “Destination DC’s Hostname” -OperationMasterRole 0,1,2,3,4
Once you copy and paste the powershell after you edit the destination host DC name you it will take couple of minutes to migrate all the FSMO roles to the new Server.
Making sure that all the roles have been migrated :
Netdom query FSMO
Adding second DC
Reference:
https://technet.microsoft.com/en-us/library/ee617229.aspx?f=255&MSPPError=-2147217396
Source: Default-First-Site-Name\DC2
******* 1 CONSECUTIVE FAILURES since 2015-03-23 19:37:45
Last error: 8524 (0x214c):
The DSA operation is unable to proceed because of a DNS lookup failure.
Naming Context: CN=Configuration,DC=kibtek,DC=local
Source: Default-First-Site-Name\DC2
******* WARNING: KCC could not add this REPLICA LINK due to error.
Naming Context: CN=Schema,CN=Configuration,DC=kibtek,DC=local
Source: Default-First-Site-Name\DC2
******* WARNING: KCC could not add this REPLICA LINK due to error.
Naming Context: DC=kibtek,DC=local
Source: Default-First-Site-Name\DC2
******* WARNING: KCC could not add this REPLICA LINK due to error.
Resolution:
After joining new DC you will see this error until the replication with the PDC and schema master is finished.
Use the repadmin /syncall to hasten the sync process.
Hope this was useful