Time Synchronization for Virtual Domain Controllers running on either Hyper-V or VMware Virtualization Platforms should be managed by Active Directory.
There are several reasons as to why we should let Active Directory manage Time Sync for Virtual Domain Controllers, but first we need to look at the applications running inside a Virtual Machine.
Please read here: https://www.simple-talk.com/blogs/2013/03/12/let-active-directory-manage-it-please/
Sometimes when you open an Active Directory tool, you might get hit with the “Active Directory Naming Information Could Not Be Located” error message. The error does not provide more information as to what “Naming Information” the tool is referring to. And also, there’s nothing in the event logs to let you know more about the error so you can troubleshoot the issue. What you may not know is, there is a process which active directory tools or utility have to follow to contact a domain controller to get the naming information for an active directory domain. I’ll explain this process in this blog post.
Please read here : https://www.simple-talk.com/blogs/2013/04/29/active-directory-naming-information-could-not-be-located-because/
It is difficult for an architect or an organization to select the right Hyper-V high-availability or migration technology to deploy in the production environment. There are so many choices. In addition to the Hyper-V high-availability & migration technologies that were introduced in Windows Server 2008 RTM and R2, the new Hyper-V Version 3.0 running on Windows Server 2012 Operating System comes with a bunch of new migration technologies. These technologies not only provide the high-availability of virtual machines running on a Hyper-V environment but also help reduce the IT cost. An example of one of these new technologies is the ‘Shared-Nothing Live Migration’ technology, introduced in Windows Server 2012. Not only can you migrate live virtual machines without downtime but without the additional cost of shared storage devices since they aren’t required for this. Similarly, using ‘Hyper-V Replica’ of Windows Server 2012 allows you to configure a disaster recovery scenario without having to configure the ‘Windows Failover Clustering’ service!
Read more here : https://www.simple-talk.com/sysadmin/virtualization/hyper-v-migration-technologies/