<div>
You've installed the &quot;headless&quot; and specific &quot;role&quot; of the server; however, if you'd like the GUI interface you can install the server with the desktop interface and simply enable the Hyper-V features on the server.<br />
<br />
If you want to keep the server the way it is you can install the Hyper-V manager on Windows 10 Professional:<br />
<br />
<a href="https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v" rel="ugc">https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v</a><br />
<br />
Here is also a reference for managing the system remotely using the Hyper-V manager from the Win 10 system:<br />
<br />
<a href="https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts" rel="ugc">https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts</a>
</div>


<div>
So I don't bother with the Hyper-V standalone option? I guess that needs Hyper-V manager to connect to it (MS Hyper-V manager on Windows 10 or 5nine software etc.).<br />
Do I just need to install a 2016 Server instance and enable the Hyper-V role to create my VM?
</div>


<div>
Yes, I saw reference to Powershell on some of the videos I looked at so I think I'll give that a miss.<br />
I'm looking to configure two servers; AD and SQL. Am I correct in thinking that the first install of 2016 server will give me the AD functionality and then the new VM will give me the SQL functionality?
</div>


<div>
Yes, the standard server can be configured to work as an AD system along with being a Hyper-V system; however, I would keep them separate and create the physical server as a standard install with Hyper-V roles enabled.<br />
<br />
Then create the VM's necessary for AD and SQL. &nbsp;Keep the physical system as Just Hyper-V will enable you to make mistakes on VM configuration without having the possibility of causing issues with the Hyper-V setup.
</div>


<div>
OK, that makes good sense. I will end up with three 2016 servers; Hyper-V manager, AD and SQL. The Hyper-V Manager (as I'm calling it) will just be a basic 2016 server with minimum resources allocated to it.<br />
I bought the system from Dell as a two server system so can I assume the licencing is OK for this config or should I check back with Dell?
</div>


<div>
This is purely an assumption on my part but the way I've interpreted you're comments along with the original question being:<br />
<br />
1. &nbsp;The server was bought with a Server 2016 license<br />
2. &nbsp;Dell provided you with you with a Volume license key as well as an OEM key for the first license. &nbsp;In some cases the OEM key can be the volume key.<br />
<br />
Licensing can be a difficult question and I'm going off of working on it, not having to be responsible for licensing it. &nbsp;To be safe I would check with Dell but my feeling is they understood you because the physical has to have the Hypervisor on it. &nbsp;But that's where another assumption comes in.<br />
<br />
Check with Dell
</div>


<div>
I think this is the best technical solution for me. <br />
The only question is one of licencing but that's not for here but a question for Dell from who I bought the kit.
</div>


<div>
I have two very thorough EE articles on all things Hyper-V:<br />
<br />
<a href="https://www.experts-exchange.com/articles/13256/Some-Hyper-V-Hardware-and-Software-Best-Practices.html" rel="ugc">Some Hyper-V Hardware and Software Best Practices</a><br />
<a href="https://www.experts-exchange.com/articles/31442/Practical-Hyper-V-Performance-Expectations.html" rel="ugc">Practical Hyper-V Performance Expectations</a><br />
<br />
Did the licensed copy come with a DVD? Use CDBurnerXP or the like to rip that to .ISO for your VMs.<br />
<br />
Use Rufus to prep an uEFI flash drive using uEFI/CSM option using that .ISO.<br />
<br />
Use that flash drive to install the host.<br />
<br />
We install the GUI version of the OS on standalone servers and Core for our cluster nodes.
</div>


<div>
The OEM licenses keys are not the VLK keys<br />
<br />
you will get problems while auto activating windows on VMs<br />
<br />
Better provide internet access to guest VMs and run slmgr commands in series to use same OEM key to activate windows<br />
<a href="http://www.dell.com/support/article/in/en/indhs1/sln292120/installation-of-the-proof-of-purchase-from-the-acpi-table-failed-error-code-0xc004f057?lang=en" rel="ugc">http://www.dell.com/support/article/in/en/indhs1/sln292120/installation-of-the-proof-of-purchase-from-the-acpi-table-failed-error-code-0xc004f057?lang=en</a><br />
<br />
Because no matter you use any license, as long as it covers entire server (minimum 8 core licenses in pack of two for single physical CPU OR 16 core licenses in pack of two for double physical CPUs), you are entitled to use TWO VMs free of charge on server acting as *Hyper-V* server
</div>


<div>
<div class="content wysiwyg-content">
I have a new empty server and a licenced copy of Windows 2016 Std Server.<br />
I want to build two virtual servers. I have downloaded and installed Hyper-V 2016 standalone and now I have a non-GUI interface with basic options for domain, network etc. but of course, no GUI to install VMs. Is the standalone version the way to go or is it unnecessary for what I'm trying to do. It seems a bit industrial just for two VMs. <br />
I've seen Internet videos talking about using Hyper-V in Windows 2016 rather than using Hyper-V standalone but doesn't that just give me a Windows 2016 server with a Windows 2016 server inside it? Maybe I'm missing the point.
</div>
</div>


I have a new empty server and a licenced copy of Windows 2016 Std Server.
I want to build two virtual servers. I have downloaded and installed Hyper-V 2016 standalone and now I have a non-GUI interface with basic options for domain, network etc. but of course, no GUI to install VMs. Is the standalone version the way to go or is it unnecessary for what I'm trying to do. It seems a bit industrial just for two VMs. 
I've seen Internet videos talking about using Hyper-V in Windows 2016 rather than using Hyper-V standalone but doesn't that just give me a Windows 2016 server with a Windows 2016 server inside it? Maybe I'm missing the point.

How to configure two Windows 2016 VMs?

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.

Hyper-V

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.