There’s a few things that need to be configured from here. Configuring the ServerĪfter initial installation, and setting an Administrator password, you’re presented with this minimalist screen: not doing anything blatantly insecure like disabling firewalls, trusting wildcards, etc)īelow are the commands I found that work to get remote connections working. I also wanted to do the bare minimum amount of tweaking to my main workstation (i.e. What I wanted to do was be able to remotely connect to and manage the server from my main Windows workstation. So I set about trying to configure Hyper-V to play nice with a WORKGROUP. I don’t have an AD Domain set up in my apartment, and had little desire to spin up a DC and manage a domain for personal use. Remotely managing via PowerShell or the Hyper-V Manager I’m sure works seamlessly if AD is behind it handling authentication and authorization. The crux of my problem is that Hyper-V Server is really intended to be run in an AD Domain environment. I followed the steps in these docs, but still never got it working: Installing Hyper-V server from the ISO was easy, but little did I know I’d burn several days just trying to connect to it. If I could remotely manage my lab with that and PowerShell, I’d be happy. I had played around with Hyper-V on my Windows laptop, and liked the GUI Hyper-V manager as well. ![]() I liked the idea that it was light weight, accessible with PowerShell, and there were lots of cool Github projects that made deploying test AD domains automatic. A few weekends ago, I decided (because apparently I’m a masochist) that I was tired of the free version of ESXi running my home lab and decided to give Microsoft’s Hyper-V Server 2016 a try.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |