Hyper-V on 2008 R2 to 2016 issue

[Joanne]

OK this get's a bit confusing!

 

I have a VM on a 2008 R2 installation. The VM is a DC, server 2012 R2 with sophos and netsupport installed on it.

 

I want to transfer this VM from my 2008R2 server to my shiny new 2016 server.

 

I have tried exporting, copying to new server, converting vhd to vhdx, the server boots, but I get various errors, first one being that it cannot connect to my desktop on the current PDC. I try and open netsupport and it says server not found.

 

I've followed this: Quick Migration of Windows Server 2008 R2 Hyper-V to Windows Server 2012 or 2016 | Amixa Blog - Website & IT services in Western Pennsylvania

 

I've tried just using the original vhd, but same issues apply.

 

Is there a piece of software that can do it? I've been told it's possible to go 2008 R2 - 2012 R2 - 2016, but I don't have a machine I can install 2012 on, unless I use an old laptop....

 

Option B is to install a new VM with 2016 and get Sophos and NetSupport on there... might be easier, however, this morning I had a couple of machines which failed trust relationship with the domain, and I wonder if it was because this 2012 DC was switched off?

 

Bit of a quandary. Please can you throw some ideas at me?

[Steve21]

So the "new" VM boots up fine, just got network issues?

 

It could be if you haven't reset the MAC address to the same as it was on the old NIC, most VMs normally have dynamic MACs assigned.

 

Also did you reset up all the ip info etc if it wiped it from a legacy adapter to the newer sort?

 

I'm assuming you've done things like setup the virtual HyperV switch and that's functioning ok on the new host?

 

Steve

[Joanne]

Oooohhhh didn't consider MAC address. I changed all the IP settings. The Hyper-V switch is fine on the new server, set up a DC which will be my new PDC once I've swapped FSMO files over. I'll check that out.

 

So the VM on the 2008 box has a dynamic MAC. Should I change this to static and then ensure it is the same on the new box?

Edited January 9, 2018 by Joanne

[PotNoodleTech]

Hi - you will need to manually set up the IP address subnet etc on the new VM as it doesn't transfer those over - can you confirm you've re-set everything up?

[Steve21]

If they were dynamic before it shouldn't be a problem. You just find some software (especially for licensing) like to use the MAC as part of their "oh you didn't copy this illegally" kind of keys, and as dynamics change every time they're started it upsets them but if you have dynamic before it shouldn't affect anything really.

 

So can your desktop ping the new VM at all currently (or vice versa)? Or is there no connection at all between the two. If none, and you setup another VM on the server with windows etc can that ping the server?

 

Steve

[Joanne]

I can ping it fine. It's not the correct version of the VM though... sophos and netsupport aren't installed!! D'oh.

 

OK just spinning up the proper version with the vhdx file. Going to check the settings on the IP, check I can ping. Could a DNS flush do anything?

 

It is whinging about activation. I activated my new PDC with a KMS key, so should I just wait for that to kick in?

 

Just installing updates and rebooting now. Will check on it after dinner.

Edited January 9, 2018 by Joanne

[TwistedHelixis]

Cant remember but there is a tick box in adaptor settings in hyper-v gui that shares the host adapter with the guest, what is that on?

 

Also have you set static ip or left as dhcp the physical adapter that the hosts will use?

[Joanne]

Host has static IP address. Other VM on this host functions as expected.

 

VM has a static IP address.

VM can ping current PDC via IP and name.

VM cannot UNC onto the PDC - "The specified network name is no longer available"

When I go onto file explorer on the VM and go to the PDC, it says "[servername] is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The target name is incorrect."

Edited January 9, 2018 by Joanne

[Joanne]

getting certificate errors on the 2012VM on the new server.

 

Getting quite a few little niggly problems like redirects not working and stuff...

 

I've put a legacy NIC on the VM to see if that makes any difference. So far it hasn't. Installing updates to see if anything changes.

Edited January 9, 2018 by Joanne