Setup:
Goal:
Issues:
Migrating VM's from 2012R2 to 2016: 1. Open Powershell in Windows 2016, and create root certificate: PS> New-SelfSignedCertificate -Type "Custom" -KeyExportPolicy "Exportable" -Subject "CN=<<WINDOWS 2016 LOCALHOST SERVER NAME>>" -CertStoreLocation "Cert:\LocalMachine\My" -KeySpec "Signature" -KeyUsage "CertSign" 2. Create and sign certificates for all three servers. You will need to modify the text for your thumbprint from above. PS> New-SelfSignedCertificate -type "Custom" -KeyExportPolicy "Exportable" -Subject "CN=<<SERVER NAMES>>" -CertStoreLocation "Cert:\LocalMachine\My" -KeySpec "KeyExchange" -TextExtension @("2.5.29.37={text}1.3.6.1.5.5.7.3.1,1.3.6.1.5.5.7.3.2") -Signer "Cert:LocalMachine\My\<<INSERT THUMBPRINT HERE>>" -Provider "Microsoft Enhanced RSA and AES Cryptographic Provider" 3. Export all server certificates with private key. You'll need to enter a password to save them appropiately. I didn't select any other options. 4. Export Root certificate. The private key doesn't need to be included here, however, I did include it so both Windows 2016 Server have the root key. 5. Import the server certificates into the Personal certificate folder, and the root certificate into the Trusted Root Certification Authorities folder. 6. Fix the certificate revocation list: on all of the servers in powershell, enter the following to add a registry key: PS> REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization\Replication" /v DisableCertRevocationCheck /d 1 /t REG_DWORD /f 7. Now, in Hyper-V you should be able to enable replication between the windows 2012R2 server and the windows 2016 server. 8. Once replication is setup, I recommend, configuring the VM's to the correct Ethernet Ports so the VM's will become active using the correct ports. 9. Issue a failover test for the VM's to become active in the windows 2016 server with minimal downtime. Configure Windows Server 2016: 1. Once the replication is complete, you should test that all functionality of your VM's work under the new server and fix where appropriate. 2. To remove the replication and still keep the VM's on Windows Server 2016, issue the following command: PS> Remove-VMReplication * Or to remove replication on specific machines, issue: PS> Remove-VMReplication VM01 3. Upgrading Configuration Version to 8.0 The benefit of using Hyper-V 8.0 vs 2012R2's version 5.0 can be detailed in the link below, but to upgrade the VM needs to be turned off, and then an option will appear under the actions to upgrade the version, that simple. :-) SOURCE: https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/upgrade-virtual-machine-version-in-hyper-v-on-windows-or-windows-server https://charbelnemnom.com/2016/12/how-to-upgrade-the-vm-configuration-version-in-windows-server-2016-hyper-v-cluster-with-powershell-hyperv-ws2016/ Your comment will be posted after it is approved.
Leave a Reply. |
AuthorJames Benson is an IT professional. Archives
August 2022
Categories
All
|