Richard Hooper has been interested in computers since he was very young. His passion for technology continued to grow until he managed to turn it into a career. He has worked in IT for more than 10 years at a variety of companies, including Hewlett Packard Enterprise (HPE). He is currently at the UK's largest Business Energy Consultancy, which is based in Newcastle Upon Tyne. He works with Microsoft technologies: Azure Hyper-V, Failover Cluster Manager, SQL, SCCM, VMM, DPM and many more. Richard holds many Microsoft certifications including MCSE: Cloud Platform and Infrastructure. Follow him on his blog and on Twitter
I have been asked a lot about how to configure time in your domain when all the Domain Controllers (DCs) are virtual and running on Microsoft Hyper-V. People will say just stick to a physical DC. However, sometimes this is not an option. In this article, I am going to walk you through the best way to set up time synchronization.
When Windows Server 2016 was released, Microsoft brought us a new feature I personally have been waiting for since I first started with Hyper-V on Windows Server 2008 R2. That feature is Virtual Machine Start Ordering. Virtual Machine Start Ordering enables us to make dependencies between VMs or Groups of VMs to make sure that they start in the correct order.