I have a small business client that's being spun off to run independently from a larger organization. They want to start from scratch and will be on their own premises. I'll be setting up a new 2012 Domain Controller/File Server and a second 2012 server to host an industry application. The plan is to install Hyper-V core on the bare metal, and then the new DC, creating a new domain, and finally the second app server.
The problem is configuring the Hyper-V core on bare metal. I can't join it to the domain as the domain doesn't exist until I install the new DC. Am I better off installing 2012 standard w/ both Hyper-V and DC roles and then just running the second server as a VM or is there a preferred way to handle this chicken/egg situation?