Remotely Manage Server Core 2016 Hyper-V Hosting Domain Controller

by Mike Capps   Last Updated October 23, 2017 17:00 PM

I ran into a little issue this morning and am wondering how I avoid the issue in the future. Fortunately, the issue resolved itself, but this could be a major problem in the future.

My domain environment is virtualized on Server 2016 Core Hyper-V hosts. Our PDC was rebooted this morning and didn't come back online. When attempting to use remote management tools, I could not authenticate into the Hyper-V host to view the console and see what the VM was doing (turns out it was chkdsk on a 4TB volume). No matter how I tried to remotely view this VM, I was greeted with authentication issues due to the PDC being offline. Server Core 2016 doesn't allow minimalist interface like 2012 R2 did, so there aren't any local management tools besides powershell.

Do others have similar setups and have you had any experience managing a system like this? It makes me want to reinstall Server 2016 as a GUI instead of Core just to ensure local vm management tools work.

Answers 1

Yes, what you have is not a smart setup.

In general, when running a minimalistic setup (i.e. no real redundancy) it is smarter to have a UI on the physical host - for the simple reason that you then have A UI. Powershell is powerfull, but I prefer a UI for most simple things.

Server core has a lot of advantages, but I would always make sure I have access to a physical system with a UI as minimum. I do so in remote locations (1-2 servers > all have UI installed) and only deviate when I can make sure to have alternatives available.

October 23, 2017 16:53 PM

Related Questions

Altaro backup warning

Updated February 09, 2017 14:00 PM

Can't connect to WinRM on Domain controller

Updated October 19, 2017 14:00 PM

Event log subscription returns error code (0x138C)

Updated February 20, 2017 14:00 PM