Shutting Down Virtualized Domain Controllers

  • Section(s): Management
  • Published on Jan 14, 2010.
  • Last Modified on Jun 23, 2009.
  • Last Modified by Chris Sanders.
  • Rated 4 out of 5 based on 1 votes.
Hyper-V supports the ability to virtualize Windows domain controllers, but there are a few best practices to keep in mind when managing downtime associated with a virtualized DC.

Hyper-V supports the Virtualizing of Windows domain controllers in production environments, where as in previous versions of Microsoft virtualization technology, this was not recommended. There are a few best practices to keep in mind when managing downtime associated with a virtualized DC.

 

Whenever you need to take a virtualized domain controller offline for maintenance it is a best practice to always fully shut down the VM completely. You should never use the “Save State” option, and you should also never pause the VM for a great deal of time. Lastly, don’t plan on taking a snapshot of a virtualized domain controller and restoring it elsewhere. Performing any of these actions could result in synchronization and replication issues that will prevent your domain controller from functioning properly.

 

 

About Chris Sanders


Article not looking right or info is missing? Let us know so that we can fix it: .


Receive all the latest articles by email!

Receive Real-Time & Monthly VirtualizationAdmin.com article updates in your mailbox. Enter your email below!
Click for Real-Time sample & Monthly sample

Become a VirtualizationAdmin.com member!

Discuss all your Virtualization issues with other experts. Click here to join!

Readers' Choice

Which is your preferred Backup and Recovery solution?

Follow TechGenix on Twitter