By now, I’m sure everyone has heard of Nano server, it is the next big or rather small thing form Microsoft. If you just started you looking into Nano server, the process is quite confusing, as it is well not a standalone server, but more like a self build mini server version.

Here my script how to build one from scratch, super easy.

 

 

A virtual machine in Hyper-V consists of a few files that account for its virtual hardware configuration and the virtual storage (VHD and VHDX files).  By default the virtual machine configuration files are stored inC:\ProgramData\Microsoft\Windows\Hyper-V, and the virtual hard drives are stored in C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks.

One slight improvement in Hyper-V (in Windows Server 2012) is that during the installation process (GUI mode only) it gives you the option of changing these defaults.  However the defaults are still the same as they used to be… on the C drive.

Being cheap I only have a ‘tiny’ SSD (ok folks I bought it years ago and it felt like it was a fortune back then…) as C:\, all other data is still on rusty spindles on my home lab.

VMs, I know are important but are small are still on the C:\ however others I had to move off.

Now tiering storage is fine, it is a PITA to find where which VHD/VHDX is stored via GUI. The fastest way I found to scavenger your lost treas… um VHDs is of course Powershell.

then being a little OCD…, I like to sort it after names. An example can look like this:

Now, that is not bad, what if I need more info, let’s say also the VMID so you can quickly RDP into the VM (see my post about RDCMan).

Easy, Get-VMHardDiskDrive does not have the info about the VMID, Get-VM however does, so we can just pipe that in it like so:

That will give us a nice list with the VMname, VMID and VHD(x) path.

Another thing to mention. if you wan to change the default location of your VM Disks, or even of the machines, Powershell can do that as well:

or via GUI of course in the Hyper-V settings:

2016-01-10_17-31-06

I am a big fan of MSFT’s Remote Desktop Connection Manager, I have dozens of servers in it at my work, so I started tinkering around with it at home, especially in mind connecting to all my VMs  on my Hyper-V test lab.

Turns out, is is not as straight forward as you’d think it’d be.

Here is how to get it to work:

  1. There are issues with the authentication. Adding the following registry keys fixes that:
  2. Even though you might be a local admin on the Hyper-V Host, add your account to the ‘Hyper-V Administrators’ Group.
  3. Get the ID of the VM you want to connect to
  4. Now we can go to the RDCMan man and add a new server
    – Server name: Is the name of your Hyper-V Host (NOT the VM)
    – Check ‘VM console connect’ and paste the ID we got via PowerShell
    – You can put whatever you want as ‘Display Name’
    2015-12-30_10-11-04
  5. Test and see if you can connect. To connect you have to provide the credentials to log in to the HYPER-V HOST, not the VM.

Now you should be able to use RdcMan to connect to your VMs, be it Window Linux, or anything else you can run as a VM. :o)

I was today stuck in a 2003 VM for a while…. no intergration AGHr…. here some things that are REALLY helpful. :o)