WS 2016 Essentials as VM in workgroup

Jerry the Computer Guy

Jerry the Computer Guy

Member
Reaction score
4
Location
Dallas, TX
Goal: Install WS2016E as a VM on Hyper-V Server 2016 and create a domain in what's currently a workgroup environment.

Issue: RDP works, but connecting via the Hyper-V Manager in Windows 10 doesn't. I've tried all the PowerShell configuration suggestions I could find, without success. The errors change, but persist.

Questions:
  1. Do I keep fghting to get Hyper-V Manager connected? (I'm thinking no)
  2. Do I attempt installing and configuring the VM via PowerShell from Hyper-V Server itself? (Seems logical)
  3. Does RDP work on a fresh VM? (I've never had to test this before)
  4. Anything else I'm neglecting to consider? (Likely)
 
So, I'm basically going to answer my own questions...
  1. Stop screwing with Hyper-V Manager until the domain is set up.
  2. I have a script that should do exactly what I need and get the VM created and installing WS2016E.
  3. I need to set up an answer file that will configure domain and RDP settings (researching now).
  4. The DVD drive can't be connected to a type-2 VM, making installation from the media kit D&H sent me impossible, so I've downloaded the evaluation iso, which apparently can be activated easily using slmgr and the OEM key.
Still happy hearing any input anyone may have...
 
So....you're installing Hyper V core and then Essentials as a VM, right? I think I would just do it manually instead of struggling with scripts - can't you mount the iso from a flash drive?

Also, there is a dance you need to do on a Win10 workstation to get it to connect with HyperV manager, detailed HERE.
 
I appreciate the assist.

Specifically, Hyper-V Server (I believe Server Core is a separate thing). Already planning to mount an iso, now that I have one. The instructions you link to are more or less what I did, finding them elsewhere. I've since found one site that has far more detail than anywhere else so far. It seems there really is a lot more to it than MS bothers to document. To be clear, I did a ton of research before posting here.

Thanks for helping me think this through. I guess I just needed to hear that I am (or was) on the right track. Letting frustration or setbacks get to me isn't helping anyone.
 
I use RDP to get to my hosts, because the only way the RSAT tools work is if the host is a member of the domain. Since the only DC on the network is a guest machine that just means every time the host reboots you have problems because the network location awareness service detects the wrong network on the host.

So I RDP to the hyperv host and work from there. Going forward Microsoft is also applying pressure to prevent admins from being domain admin to use tools like this, they are all but forcing admins to RDP to the server in question and run tools from there. Which is stupid because it's conflicting with the core GUIless server design thinking they've been shoving around too.

That's why the documentation is everywhere, two divergent idea sets are used in the design of the product.
 
Last edited:
Not clear to me. Is the Hyper-V the free one or did you install a bare metal instance of 2016E and then enable the Hyper-V role. Then install a second instance of 2016E for the domain services. And is this OEM or Retail.
 
Mark, I'm using the actual Hyper-V Server. The free one. I wasn't initially aware that Essentials could be deployed as a Hyper-V host *and* VM, but I still don't prefer to go that route.

Regardless, the site I found and linked to in my previous post took care of the issues I was having. I've now got the domain set up properly and rolled-back the changes I had to make to get Hyper-V Manager running. Now, when logged in as a domain admin, the HVM console works fine. No more headaches!!!

Thank you for the information. I'm recording all the steps I had to take and will be incorporating that into a proper SOP for future use, as I doubt this will be the last non-domain location I end up upgrading to a domain. Odd that it should be this complicated to create a domain in a VM environment, but at least it's done.
 
Good to hear you got it sorted out Jerry. The only reason I pointed out using the purchased license for both is that entitles you to support on both. Don't get that with the free one.
 
Yep... ran into that before. By default you can't connect to a Hyper-V machine that is on another server if it isn't in a domain. I believe it's due to the authentication. There's a workaround, but I've never used it. I don't use the free version of Hyper-V, I like my GUI and remote access tools and I'm sticking to them! Also with MS licensing, you generally get the ability for Hypervisor host anyways.
 
Well, I had no trouble with RDP within the LAN, and I intend to install an RMM agent on both Hyper-V Server and Essentials. The issue was strictly using the Hyper-V Manager in Windows 10. Everything can pretty much be done via Powershell, but I'm not versed enough in setting up VMs that way, so I prefer having a UI, as you said. I don't, however, need one just to configure the VM host. The smaller the attack surface, the better. Setting up the server to be remotely managed only is also preferred, as restricting physical access to the hardware is important. Too many small businesses use their servers as alternate workstations, and that needs to stop. This way, even if they do hook up K/V/M, all they'll get is the Hyper-V host and can't install anything that shouldn't be there. Like games. For their kids... (I wish I was joking. Thankfully not a problem I'm currently dealing with.)
 
You must log in or register to reply here.

Similar threads

HCHTech
VM confusion again
Replies
5
Views
1K
HCHTech
HCHTech
timeshifter
Windows Server 2012 Essentials to Windows Server 2016 Standard
Replies
5
Views
4K
timeshifter
timeshifter
Back
Top