Upgrade Win2008 server to Win2012 with Hyper-V
Hi, we have two physical servers. Both running Win2008 (non-R2). Server1 has a Hyper-V with 3 VMs running Win2008 svr and Server2 has Hyper-V with one VM running Win2008 with Terminal Services for RDP users.
We would like to upgrade Server2 host OS to Win2012 R2 and the VM to Win2012 R2. Would there be any repercussion because we'll be mixing Win2008 and Win2012 R2 environment.
Also, I assume we'll require new CAL and RDP client licenses?
We would like to upgrade Server2 host OS to Win2012 R2 and the VM to Win2012 R2. Would there be any repercussion because we'll be mixing Win2008 and Win2012 R2 environment.
Also, I assume we'll require new CAL and RDP client licenses?
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
No, you shouldn't see any repercussions. Server 2008 and 2012 R2 get along very well together.
Don't know about the licenses.. I'd contact Microsoft Sales to see about that.
Don't know about the licenses.. I'd contact Microsoft Sales to see about that.
Steps to in-place upgrade,
Complete patch-up through Windows Update
Backed up the entire server
Shut Down all running virtual machines
Launch Windows Setup and after providing the basic information, I was notified that I needed to update my Schema. I opened an Administrative CMD prompt, then ran the following from the Windows Server 2012 R2 source media Z: drive
Z:\support\adprep\adprep /forestprep
Z:\support\adprep\adprep /domainprep
Check for errors & start Windows Setup and continued through to the file copy phase. then start rebooting -
These lasted another 30 minutes before I was presented with the standard Ctrl+Alt+Del Logon! (approximately of 45 minutes for the upgrade to complete).
Login via an RDP session (since that is how I normally admin this server) to check out critical services and event logs -
The only issue you will see in the event logs pertained to the Net.Tcp Listener Adapter if everything is smooth -
The Net.Tcp Listener Adapter service depends on the Net.Tcp Port Sharing Service service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Start Net.Tcp Port Sharing Service will be disabled. set to automatic, start and, then started the Listener. Your Dashboard will be all green
I dont buy inplace upgrade, but the best way is migrating from one hardware to another server
Migration Steps for Existing Source Hyper-V Server 2008 R2
Backup the original source Hyper-V Server 2008 R2 server as a precaution. We won't be making any changes to this box during the migration, but it never hurts to be safe! :-)
Shutdown running virtual machines on original source Hyper-V Server 2008 R2 server.
Review each virtual machine for snapshots - any snapshots taken of a running virtual machine should be merged by using the "Delete Snapshot ..." guest action in Hyper-V Manager. Snapshots of running VM's are not supported for migration due to hardware and software architectural differences on the source and target servers.
Review each virtual machine and ensure that any Saved States are removed using the "Delete Saved State ..." guest action in Hyper-V Manager. Saved states of VM's are not supported for migration due to hardware and software architectural differences on the source and target servers.
Important! If there are important changes saved in a VM's saved state that you wish to capture, start and gracefully shutdown the VM rather than simply deleting it's saved state.
Set the MAC address option in the settings of each VM to "Static" prior to migrating. This allows the guest OS to maintain a fixed relationship between virtual NIC and MAC address even after migrating to the target Hyper-V Server 2012 server and prevents you from needing to potentially reconfigure virtual NICs post-migration.
Export each VM using the "Export ..." action in Hyper-V Manager to an external storage location or network location that is reachable from both the new target Hyper-V Server 2012 box and your remote administration PC.
Migration Steps for New Target Hyper-V Server 2012
Import each exported VM on the new target Hyper-V Server 2012 box using the "Import Virtual Machine ..." host action in Hyper-V Manager.
Important! When using the new Import Virtual Machine wizard, you will be prompted to "Register", "Restore", or "Copy" the virtual machine when importing. You will want to select the "Restore" option and confirm the path on the new Hyper-V host to which the VM will be restored.
Review the settings of each imported VM using the "Settings ..." guest action in Hyper-V Manager. Hyper-V Server 2012 provides the ability to assign more virtual processors (up to 64 per VM), more virtual memory (up to 1TB per VM) and new virtual hardware options, such as Virtual Fiber Channel HBAs and network offloading/security. For some VMs, you may wish to take advantage of these new capabilities by adding virtual hardware resources.
Start each VM using the "Start" guest action in Hyper-V Manager to confirm that the VM starts successfully.
Connect to the console of each VM using the "Connect ..." guest action in Hyper-V Manager to confirm successful guest OS boot.
Login at the console of each VM and confirm that all services have started
Update the Hyper-V Integration Services for each VM by using the "Action -> Insert Integration Services Setup Disk" option on the menu bar of each Virtual Machine Connection window..
Complete patch-up through Windows Update
Backed up the entire server
Shut Down all running virtual machines
Launch Windows Setup and after providing the basic information, I was notified that I needed to update my Schema. I opened an Administrative CMD prompt, then ran the following from the Windows Server 2012 R2 source media Z: drive
Z:\support\adprep\adprep /forestprep
Z:\support\adprep\adprep /domainprep
Check for errors & start Windows Setup and continued through to the file copy phase. then start rebooting -
These lasted another 30 minutes before I was presented with the standard Ctrl+Alt+Del Logon! (approximately of 45 minutes for the upgrade to complete).
Login via an RDP session (since that is how I normally admin this server) to check out critical services and event logs -
The only issue you will see in the event logs pertained to the Net.Tcp Listener Adapter if everything is smooth -
The Net.Tcp Listener Adapter service depends on the Net.Tcp Port Sharing Service service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Start Net.Tcp Port Sharing Service will be disabled. set to automatic, start and, then started the Listener. Your Dashboard will be all green
I dont buy inplace upgrade, but the best way is migrating from one hardware to another server
Migration Steps for Existing Source Hyper-V Server 2008 R2
Backup the original source Hyper-V Server 2008 R2 server as a precaution. We won't be making any changes to this box during the migration, but it never hurts to be safe! :-)
Shutdown running virtual machines on original source Hyper-V Server 2008 R2 server.
Review each virtual machine for snapshots - any snapshots taken of a running virtual machine should be merged by using the "Delete Snapshot ..." guest action in Hyper-V Manager. Snapshots of running VM's are not supported for migration due to hardware and software architectural differences on the source and target servers.
Review each virtual machine and ensure that any Saved States are removed using the "Delete Saved State ..." guest action in Hyper-V Manager. Saved states of VM's are not supported for migration due to hardware and software architectural differences on the source and target servers.
Important! If there are important changes saved in a VM's saved state that you wish to capture, start and gracefully shutdown the VM rather than simply deleting it's saved state.
Set the MAC address option in the settings of each VM to "Static" prior to migrating. This allows the guest OS to maintain a fixed relationship between virtual NIC and MAC address even after migrating to the target Hyper-V Server 2012 server and prevents you from needing to potentially reconfigure virtual NICs post-migration.
Export each VM using the "Export ..." action in Hyper-V Manager to an external storage location or network location that is reachable from both the new target Hyper-V Server 2012 box and your remote administration PC.
Migration Steps for New Target Hyper-V Server 2012
Import each exported VM on the new target Hyper-V Server 2012 box using the "Import Virtual Machine ..." host action in Hyper-V Manager.
Important! When using the new Import Virtual Machine wizard, you will be prompted to "Register", "Restore", or "Copy" the virtual machine when importing. You will want to select the "Restore" option and confirm the path on the new Hyper-V host to which the VM will be restored.
Review the settings of each imported VM using the "Settings ..." guest action in Hyper-V Manager. Hyper-V Server 2012 provides the ability to assign more virtual processors (up to 64 per VM), more virtual memory (up to 1TB per VM) and new virtual hardware options, such as Virtual Fiber Channel HBAs and network offloading/security. For some VMs, you may wish to take advantage of these new capabilities by adding virtual hardware resources.
Start each VM using the "Start" guest action in Hyper-V Manager to confirm that the VM starts successfully.
Connect to the console of each VM using the "Connect ..." guest action in Hyper-V Manager to confirm successful guest OS boot.
Login at the console of each VM and confirm that all services have started
Update the Hyper-V Integration Services for each VM by using the "Action -> Insert Integration Services Setup Disk" option on the menu bar of each Virtual Machine Connection window..
First of all you have to verify if your HW is win2012R2 supported.
Then update BIOS and all Firmware.
Uninstall all integration services on VM's.
Copy your folder with VM's to different location.
Make Clean Install of windows server host to windows server 2012R2
Convert all VM's to VHDX (powershell)
Import VM's to hyper-v.
Install new integration services.
Then upgrade your VM to server 2012 r2.
BR, Benjamin
Then update BIOS and all Firmware.
Uninstall all integration services on VM's.
Copy your folder with VM's to different location.
Make Clean Install of windows server host to windows server 2012R2
Convert all VM's to VHDX (powershell)
Import VM's to hyper-v.
Install new integration services.
Then upgrade your VM to server 2012 r2.
BR, Benjamin
Premium Content
You need an Expert Office subscription to comment.Start Free Trial