Hi to everyone,
In this blog post I’d like to explain how to add new name to your Nano Server. Why I would like to do that? Because, when you create Nano Server image from the Nano Server Image Builder, during the setup process you need to enter the name of the Nano Server, also if you want to create few of Nano Servers, you will have the same name on the every machine what’s not good, right?
As you can see from the picture below, the recovery console doesn’t have an option to rename the hostname.
The only way to rename Nano Server is using PowerShell Remote Session or PowerShell Direct from the Hyper-V host.
In this case I’ll use PowerShell Direct, and as you can see on the picture below I haven’t network adapter on the Nano Server because I have one Nano Server on my network with the same host name and want to avoid collision.
Open PowerShell in elevated mode and type:
Enter-PSSession –VMName “nano server name” –Credentials administrator
Where “nano server name” is the name of your Nano Server.
Rename-Computer –NewName “New Name” –PassThru
Where “New Name” is the name of your Nano Server.
After you are done, logon to your renamed Nano Server, enable network adapter and enjoy the day.
Have a nice weekend!
I had a honor to be Hyper-V 2016 Best Practices book reviewer written by my two colleagues, Benedict Berger and Romain Serre. I believe that you will learn a lot about Hyper-V on Windows Server 2016 from this great book. The book is available on Packt site.
In this blog post I’d like to explain how to create Hyper-V virtual machine on Windows 10 to be compatible with Windows Server 2012 R2!
In the last couple of months my users are using Windows 10 on the local machines, (desktops and laptops) and sometime they need to move virtual machines created on the Windows 10 to Hyper-V hosts which have been using Windows Server 2012 R2 as OS.
When you create virtual machine on Windows 10, Configuration Version is 7.0 and you cannot change that or during virtual machine creation choose configuration version.
From the other side, virtual machine configuration version on Windows Server 2012 R2 is 5.0 and we cannot import virtual machine created on Windows 10 to Windows Server 2012 R2 because of differences on configuration version.
So, what we can do in that case?
The first; if we have virtual machine with configuration version 7.0, we can copy .VHDX on Hyper-V host with WS2012 R2, create new virtual machine and add copied virtual disk. But, we lost virtual machine configuration and checkpoints.
The second; we can create virtual machine on Windows 10 through PowerShell, where can choose virtual machine configuration version.
Here is an example, and full script you can download .ps1.