Host Hyper-V server is getting it's Authentication/DNS from a DC that I need to remove. How do I proceed

I have two DC's 1 is virtual.  I need to remove the physical DC to rebuild it.  However, the Host member Hyper-V server is authenticating to the server I need to rebuild.

How do I proceed to accomplish this task?
J.R. SitmanIT DirectorAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Cliff GaliherConnect With a Mentor Commented:
No, that is a chicken-and-egg scenario. If you envision rebooting your hyper-v server within the time it takes to rebuild your physical DC, stand up another DC in the interim, even if only temporarily.
0
 
Cliff GaliherCommented:
Active Directory is a multi-master topology, so as long as your DC is healthy, advertising, and working properly (use dcdiag to check this) machines will seamlessly move among available DCs. They won't lock onto and authenticate against only one. So you can remove a DC easily and transparently without extra steps.
0
 
TunerMLSystems EngineerCommented:
You will however want to ensure that the DC you are rebuilding does not hold the FSMO roles, and if it does transfer them to the DC that will remain active during this period.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
J.R. SitmanIT DirectorAuthor Commented:
So lets say the physical DC is off.  If I reboot the Host Hyper-V server, it will authenticate to the VM on itself that is the DC?

All FSMO roles have been moved to the VM DC.
0
 
J.R. SitmanIT DirectorAuthor Commented:
That's what I thought.  Does it need to be a DNS server?

Thanks
0
 
Cliff GaliherConnect With a Mentor Commented:
If your only other DNS servers with AD zones are VMs on the host, yes. AD is heavily dependent on DNS.
0
 
J.R. SitmanIT DirectorAuthor Commented:
got it.  It will using the existing scope that exists on AD, correct?
0
 
Cliff GaliherCommented:
Scope?
0
 
J.R. SitmanIT DirectorAuthor Commented:
Sorry, was thinking DHCP.  I just checked it has the proper "Zones"
0
 
Cliff GaliherCommented:
So I am not sure there was a question there, but the rule is the same as it is for a domain controller. You want to make sure a DNS server is always available. If that means making a temp DC also be a DNS server then do that.
0
 
J.R. SitmanIT DirectorAuthor Commented:
got it.  All is good.

Thanks
0
 
J.R. SitmanIT DirectorAuthor Commented:
Final question.  I have the DHCP scope split over two DC.  If the DC that I'm shutting down is one DHCP and the other is the VM, is that a problem?
0
 
Cliff GaliherConnect With a Mentor Commented:
It would be for clients requesting leases if you rebooted the host or guest while the physical machine is down. Or if the host also gets its address from DHCP. Otherwise, no.
0
 
J.R. SitmanIT DirectorAuthor Commented:
Thanks for all the help
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.