Upgrade from SCVMM 2012 R2 to 2016

Requirements and limitations

  • SCVMM 2012 R2 should be running with UR 9 and above.
  • Ensure that the server meets all requirements for SCVMM 2016.
  • Supported SQL for SCVMM 201 start’s from SQL Server 2012 SP1

Upgrade Standalone SCVMM.

  • Uninstall VMM and select to retain the database. Make sure you remove both the VMM management server and the console.
  • On the current VMM server, upgrade the operating system to Windows Server 2016.
  • Install VMM 2016. In the main setup page, click Install.
  • In Select features to install, select VMM management server > Next. The VMM console is automatically installed.
  • In Product registration information, provide the appropriate information > Next. If you don’t enter a product key, VMM will be installed as an evaluation version that expires 180 days after installation.
  • In Please read this license agreement, specify that you’ve read the terms, and click Next.
  • In Usage and Connectivity Data, select the option you want, and click Next.
  • If Microsoft Update appears, select whether you want to install VMM updates with Microsoft Update, and then click Next.
  • In Installation location, use the default path or type a different installation path for the VMM program files, and then click Next. The computer you’re upgrading is checked to ensure it complies with prerequisites.
  • In Database configuration:
  • If you’re using a remote SQL Server instance, specify the name of the remote SQL Server computer.
  • Learn more about upgrading the SQL Server database if required.
  • If SQL Server will run on the VMM server, type the VMM server name, or type localhost. If the SQL Server is in a cluster, type the cluster name.
  • Don’t specify a Port value if you’re using a local SQL Server, or if the remote SQL Server uses the default port (1443).
  • Select Existing Database, and select the database you backed up from your previous installation. Provide credentials with permissions to access the database. Click Yes to upgrade.
  • In Configure service account and distributed key management, specify the account that the VMM service will use. You can’t change the identity of the VMM service account after installation.
  • Under Distributed Key Management, select whether to store encryption keys in Active Directory. Choose settings carefully for the service account and distributed key management. Depending on what you choose encrypted data such as passwords in templates might not be available after the upgrade and you’ll need to enter them manually.
  • In Port configuration, use the default port number for each feature or provide a unique port number that is appropriate in your environment. To change the ports that you assign during the VMM installation, you need to uninstall and reinstall the VMM server. Don’t configure port 5986, because it’s preassigned.
  • In Library configuration, select whether to create a new library share or to use an existing library share on the computer.
  • The default library share that VMM creates is named MSSCVMMLibrary, and the folder is located at %SYSTEMDRIVE%\ProgramData\Virtual Machine Manager Library FilesProgramData is a hidden folder, and you cannot remove it.
  • After the VMM management server is installed, you can add library shares and library servers.
  • In Upgrade compatibility report, review settings > Next.
  • In Installation Summary, review settings and click Install to upgrade the server. Installing features page appears and displays the installation progress.
  • In Setup completed successfully page, click Close to finish the installation.
  • If there’s an issue with  setup,check the %SYSTEMDRIVE%\ProgramData\VMMLogs folder. ProgramData is a hidden folder.

 

 

Advertisements