asked on Adding 2012 R2 Domain controller in 2008 R2 domain
Hello,
We have two DC both are running 2008 R2
DC1 - All FSMO roles, AD integrated DNS (VM)
DC2 - DC, AD integrated DNS (VM)
SRV1 - DHCP windows 2003 (VM)
I want to add 2012 R2 (Physical) as DC and want to move DHCP to 2012 R2 server.
Need to migrate FRS to DFSR.
Show question is should I migrate FRS to DFSR first before adding another DC running 2012 R2 or after adding it?
or add 2012 R2 first then move DHCP to 2012 R2 and then migrate FRS to DFSR?
Instructions to migrate FRS from another SW topic https://blogs.technet.microsoft.com/filecab/2014/06/25/streamlined-migration-of-frs-to-dfsr-sysvol/
Can you also provide me working instructions on migrating DHCP from 2003 to 2012?
Also, I need to add processor on existing DC servers which are VM any issues doing that specially on DC? I have tested on another 2008 server and did not cause any issues?
Thank you
We have two DC both are running 2008 R2
DC1 - All FSMO roles, AD integrated DNS (VM)
DC2 - DC, AD integrated DNS (VM)
SRV1 - DHCP windows 2003 (VM)
I want to add 2012 R2 (Physical) as DC and want to move DHCP to 2012 R2 server.
Need to migrate FRS to DFSR.
Show question is should I migrate FRS to DFSR first before adding another DC running 2012 R2 or after adding it?
or add 2012 R2 first then move DHCP to 2012 R2 and then migrate FRS to DFSR?
Instructions to migrate FRS from another SW topic https://blogs.technet.microsoft.com/filecab/2014/06/25/streamlined-migration-of-frs-to-dfsr-sysvol/
Can you also provide me working instructions on migrating DHCP from 2003 to 2012?
Also, I need to add processor on existing DC servers which are VM any issues doing that specially on DC? I have tested on another 2008 server and did not cause any issues?
Thank you
Windows Server 2012DHCPActive DirectoryVMware
Last Comment
Nirav04
ASKER
You are correct I should have created separate questions, I will remember this in future.
I did google it but getting two separate methods and I wasn't sure which method should I use, first using netsh link you provided and second using migration tool https://www.petri.com/windows-server-2003-dhcp-migration-2012
As far as the processor is concerned this VM is running on a single processor with 1 core and they have this way for quite a while now, recently we had added SSO agent for our firewall so it checks auth using logon events which is a little processor intensive.
I did google it but getting two separate methods and I wasn't sure which method should I use, first using netsh link you provided and second using migration tool https://www.petri.com/windows-server-2003-dhcp-migration-2012
As far as the processor is concerned this VM is running on a single processor with 1 core and they have this way for quite a while now, recently we had added SSO agent for our firewall so it checks auth using logon events which is a little processor intensive.
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.
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.
How many processors currently on he VMs?
I find it,s better to have two vCPU,s on a Windows virtual Windows server ( in VMWare ESXi).
I find it,s better to have two vCPU,s on a Windows virtual Windows server ( in VMWare ESXi).
ASKER
Currently, both DC have one vCPU.
ASKER
Successfully added second vCPU and performance is much better. Thank you for everyone's help.
Answers, in my opinion:
Since both of your DCs are 2008 R2 already, migrate to DFS-R before introducing a new DC. DFS-R is *much* better than FRS and you have a lower risk of problems when you do eventually introduce a new DC.
I'd migrate DHCP before doing *anything* else. Get that 2003 server off your network. It is already two years too late.
Once you have the 2003 server gone, then do DFS-R, then introduce your new DC.
Migrating DHCP is easy. I googled it. Googling is a good skill to learn. https://blogs.technet.microsoft.com/canitpro/2013/04/28/step-by-step-migration-of-dhcp-from-windows-server-2003-to-windows-server-2012/
Adding a processor to a VM in Hyper-V is a non-issue for DCs. I'm not a VMWare guy, but I can't think it'd be a problem there either. But I can't say that with 100% certainty.
With that said, I wouldn't usually bother. Domain controllers are not CPU intensive. Their bottlenecks lie elsewhere. I doubt you'd see any benefit. Have you actually used performance metrics to decide if this is necessary?!?