Windows Server – Hyper-V migration VM’s

Working with Hyper-V and migrating VM’s between VM Hosts can give some surprises now and than.

The IP xxx.xxx.xxx.xxx address you have entered for this network adapter is already assigned to another adapter Microsoft Virtual Machine Bus Network Adapter #2. Microsoft Virtual Machine Bus Network Adapter #2 is hidden from the Network and Dial-up Connections Folder because it is not physically in the computer or is a legacy adapter that is not working If the same address is assigned to both adapters and they both become active, only one of them will use this address. This may result in incorrect system configuration.

Recently I had to migrate a VM running on old Windows OS to a new Hyper-V host.

You would expect to just copy the VM disk for one host to the other. And start it up.

Indeed so far so good. But when the VM had a FIXED IP Address before. You will now see that new copy of the VM has assigned a DHCP IP address ?

The reason is that the the Network Adapter has changed when copying over the VM from one host to the other.

When you try to put back in the same fixed IP ADDRESS you will see this message appear.

Whatever you try it will not accept the same IP Address as before

Which can be problematic for certain applications running on the VM.

SOLUTION :

1. Start a CMD prompt as an admin
2. Type: set devmgr_show_nonpresent_devices=1 and press ENTER
3. Type DEVMGMT.MSC and press ENTER
4. In Device Manager, click VIEW then SHOW HIDDEN DEVICES

1. Expand NETWORK ADAPTORS
2. Right click on each greyed out NIC and select UNINSTALL

1. Close all of the Windows (including your IP, Network and Sharing Center…)
2. Now can assign the again the same fixed IP ADDRESS to the new Adapter that was added to you VM.

Enjoy!

Windows Server 2016 – Altaro Backup Software

Just started using ALTARO Backup software.

This Free edition contains a full featured backup solution for 2 VM guests.

If you look at the high compression rate (63%) it was able to reduce the VM from 11GB to 3.5 GB

Tip :

If you get these kind of warnings VM is NOT Application Consistent.

In the VSS settings you can DISABLE the VSS settings for a specific VM to solve the issue.

Highly recommended as a VM Backup Software for Hyper-V and VMWare …

Enjoy !

Windows Updates – Error Code 66A, 645, …

If you encounter these errors doing updates :

Code 66A, 645, etc

It might just mean that your .NET evironment is corrupt ?

SOLUTION :

Open Control Panel, go to Programs and Features

Select Microsoft .NET Framework Client Profile

Select REPAIR, next reboot the server and install the Windows Updates again.

Errors should be gone …

Success !

Windows Server 2016 – RADIUS Server Config

We had to configure RADIUS authentication on multiple servers 2008r2 / 2012 and 2016

On some of the servers we had already Routing and Remote access service running.

 

When we opened the console it already showed RADIUS ..?

So we where under the impression that this was already installed as part of the Routing and Remote Access Service

But when trying to authenticate nothing was happening …

After al long time trying to figure out what was wrong, we noticed this …. ?

Even if we could open and configure the RADIUS Client config, it was not installed or running …

 

SOLUTION :

Make sure the Network Policy Server is installed and running

You need to see the Service Running

You will see NPS appearing in the Server Manager too afterwards

 

Windows 2012 / 2016 see here :

Check the NPS service is running :

 

No you are ready to configure the RADIUS client policy setup.

And test the the VPN access …

 

TIP : Don’t forget to give the AD user Access Permissions

 

Enjoy !