In our previous articles ‘ How to install and configure RSAT on Windows 10 and make it a management workstation that connects to a Hyper-V 2012 R2 core server in a workgroup ’ and ‘ How to install and configure Microsoft Hyper-V Server 2012 R2 ’ we created a base line installation on which we will install a Windows Server 2012 R2 Essentials virtualized. In ‘ A do-it-yourself guide for installing Windows Server 2012 R2 Essentials ’ we describe how to do a basic installation and on our Hyper-V server that is about the same so you should follow that article. For now we focus on creating a new Virtual Machine in Hyper-V. 1. Install File and Storage Services on the Hyper-V Server On our Windows 10 workstation open Server Manager and if you not already have done so and add the Hyper-V server to the server list. Right click the Hyper-V Server and choose Add Roles and Features. Click Next Click Next Click Next Choose File and Storage Service and check all options. Click Next. Click Next Click Install Click Close to finish the installation of File and Storage Services on the Hyper-V. Now we can create storage pools and browse to the Hyper-V like \\hyperv\c$ which is really handy. 2. Create a Virtual Machine on the Hyper-V Server that will run our Windows Server 2012 R2 Essentials Now it is time to create the Virtual Machine that will hold the Windows Server 2012 R2 Essentials server. From the start menu start Hyper-V Manager and click ‘Connect to Server and type in the name of your Hyper-V server. In my case that is HYPERV From the right side choose New –> Virtual Machine Choose Next Give the VM a name and click Next Choose Generation 2 and click Next. If you update this server after finishing the installation it can happen that your server crashes. See this for more information Choose the amount of Ram you want to assign and click Next. Assign a Virtual Switch and click Next Create a Virtual Disk for the OS installation. You can add more disks later if you need them. I always make more disks for users data and shares and keep them separated from the OS. Choose the ISO image for this installation. The image must already be on the Hyper-V server’s drive. Click Finish. After this you are ready to install WSE 2012 R2 Essentials as in ‘ A do-it-yourself guide for installing Windows Server 2012 R2 Essentials ’. 3. Join the Hyper-V Server to the domain As a final step we need to join the Hyper-V Server to the domain of the virtualized Windows Server 2012 R2 Essentials. Normally you will be prompted to boot the server or workstation you join to a domain and this is also the case with the Hyper-V server. You may think that this is a problem for your domain controller but it is not because it will be saved as soon as the Hyper-V Server boots. Logon to the Hyper-V server and choose option 1. Type D for Domain. Type the name of the domain you want to join. Type the name of the Domain Administrator Enter the password for the Domain Admin If you want to change the name of the server click Yes, otherwise click No and reboot the server. Logon to the Hyper-V Server with your Domain Administrator account. BTW, if you have not yet joined the ‘management workstation’ to the domain it is now time to do that and this procedure has been described here ‘ How to join a Windows 10 Pro to a Windows Server 2012 R2 Essentials domain with the connector ’. 4. Set time synchronization on your Hyper-V Server and the virtualized domain controller Open Hyper-V Manager on the ‘management workstation’ and check if ‘Time Synchronization’ is checked in the Integration Services. Click OK to close the Hyper-V Manager. Logon to the Domain Controller and open an elevated command prompt. From that prompt type w32tm /query /source . The output must be ‘VM IC Time Synchronization Provider’. w32tm /query /source From the same elevated command prompt type ' reg add HKLM\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\VMICTimeProvider /v Enabled /t reg_dword /d 0 ’. This effectively enables time synch with the Hyper-V server when the DC reboots but disables it after the DC is up and running. reg add HKLM\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\VMICTimeProvider /v Enabled /t reg_dword /d 0 Now run ‘ w32tm /config /syncfromflags:DOMHIER /update ‘. This will tell the DC to sync time from within the domain. w32tm /config /syncfromflags:DOMHIER /update Now run ‘ net stop w32time & net start w32time ’ to restart Windows Time Service and ‘ w32tm /resync /force ’ net stop w32time net start w32time w32tm /resync /force We will now download a Fixit tool from Microsoft that will set our Hyper-V server and Virtualized DC’s to sync from an internet based time server. The tool is from this knowledge base article https://support.microsoft.com/en-us/kb/816042 at ‘ Configuring the Windows Time service to use an external time source ’. The direct download link is here http://go.microsoft.com/?linkid=9729248 . If we run that tool we are prompted to enter a valid Internet Time Server and you need one here is a list https://support.microsoft.com/en-us/kb/262680 . If you still get ‘Local CMOS Clock’ when checking the time source you need to follow the steps from that KB article and configure your server manually. Sometimes the ‘Fixit’ solutions don’t work…don’t know why.