Setup Hyper-V Environment in a cheap way

As freelancer I need to use differents environments settings and during this years what I learned from my job is that one laptop is not enought.

At some point situation became unbearable. Three or more kind of version source control software, five or six IDE, I don’t know how many VPN installed. The worst situations was the notification message from Windows.

If you runned in this I suggest you to spend some money in your activity.

Everyone knows virtual machines and is related software to manage it, but I didn’t want to setup a classic virtual machine, I wanted a cheap server! So I took my wallet and with € 860,00 I built my little virtual world!

Ingredients
How to

The most important thing is Hyper-V Server 2019, it is free in core version, so you can download and install everywhere! Pay attention, because is a core version you don’t have any user friendly interface, just a command prompt to configure it, another important point is that Hyper-V Server 2019 doesn’t support Wifi services, that means that you must use a cable to connnect it on Internet.

My experience was painfull with network adapter. It could be possible that Windows doesn’t recognized your network adapter and Intel drivers doesn’t work propertly because a wrong INF file configuration.
What you have to do is download from Intel Download Center or Microsoft Update Catalog your driver (no installer, but inf and dll file) and edit manually INF file, in my case was the section ControlFlags, so I read this article and fix the problem.

But, how to install a driver manually without a setup? Powershell is your answer.

Get-ChildItem "C:\mydrivers\" -Recurse -Filter "*.inf" | 
ForEach-Object { PNPUtil.exe /add-driver $_.FullName /install }

Your server should be connected, now is time to configure it in order to connect on your new server. In this article you will find all detailed steps, following a summary of needed configurations.

  1. Enable remote managing (on HyperV and Client)
  2. Enable CredSSP and WinRM firewall rules (on HyperV)
  3. Install HyperV Manager (on Client)

On my local network I had to configure also a suffix DNS on my router in order to resolve propertly machine names.

Conclusions

Now you are able to create and configure all virtual machines you need! But why two hard disks? Because I use to configure two disks on my virtual machines, first one is used by operating system, second one is used for user-data, all second drivers are stored in a separate hard disk (Barracuda in my configuration). Just in case the first one decide to explode!

Spread your wings and fly away

Queen

Leave a Reply