Platform Services / vCenter Server Upgrade

Walkthrough: Upgrading vCenter Server 6.5 to vCenter Server 6.7

Upgrading vCenter Server 6.5 to vCenter Server 6.7

Upgrading vCenter Server 6.5 to vCenter Server 6.7

 vSphere Upgrade 6.7

Prior to upgrading your vCenter Server, please make sure you are using a supported upgrade path.

vCenter Server 6.7  Update

We always recommend reading the release notes prior to upgrading. The release notes will provide details not only covering What's New, but information on Installation and Upgrade Notes for the release you will be upgrading to.

vSphere Interoperability

 

One last thing to verify prior to upgrading is making sure your upgrade path and vSphere Product Interop is supported. You can utilize our interoperability matrices to validate VMware products are compatible with one another.

 VCSA installer

Download the VCSA installer to your local machine and run the installer from the vcsa-ui-installer directory. You can run the installer from windows, linux or mac OS.

vCenter Server Appliance

Once the installer is launched, we will use the Upgrade option.

 Stage 1 New Appliance

This screen explains how the upgrade process works, it will be a two stage process. Stage 1 a new appliance will be deployed, and Stage 2 is where we will export the data from the old appliance and import it into the new one.

End user license agreement

Accept the End user license agreement

FQDN or IP Address

Enter the FQDN or IP Address of the vCenter Server Appliance you wish to upgrade and hit Connect Source.

ESXi Host or vCenter Server

Enter in the details of the source appliance, here we can use the FQDN or IP address. We will also enter in the SSO administrator username and password, the root OS password for your original appliance and we will input the https port and username/password of the ESXi Host or vCenter Server that is managing the source appliance

Certificate Warning

You will need to accept the SSL thumbprints.

Appliance  deployed.

Here you will specify the destination where you want the new appliance to be deployed.

Certificate Warning

You will need to accept the SSL thumbprints.

VM folder appliance deployed

Select VM folder you wish the appliance to be deployed in

Cluster or Standalone host.

Select the compute resource you would like to deploy the appliance to. You can specify a cluster, or standalone host.

Target Appliance.

Here we will specify the display name for our new appliance in vCenter inventory, it must be unique. We will also set a new root password for the appliance. You do have the option to re-use the same password.

Deployment size and Storage size

We will chose a deployment size and storage size for our new appliance. Please make note you can increase the size from the previous appliance we are upgrading. Note: If you plan to use vCenter High Availability a deployment size of Small or larger is required. vCenter High Availability is not supported on Tiny deployments.

Storage location  Database

Specify the storage location for the new appliance and if you would like it to be thin provisioned you will check the box.

Configure network setting

Specify a VM network and IP that will be used for the temporary network. This is only used during the export and import process. Once the upgrade is complete, the IP will become unused.

Validate Upgrade process.

Validate all the information you entered is complete and we will finalize stage 1 of the upgrade process.

Appliance deployed.

First step of stage 1 is the appliance is deployed.

Additional configuration deployment

Additional configuration to the deployment where RPM's are loaded and installed. Once stage 1 is complete, we can continue the upgrade wizard to start stage 2. If the installer closes or you wish to continue this step later you can re-start the upgrade wizard through the VMware Appliance Management Interface (VAMI) on port 5480 of the temporary IP address.

New appliance.

We will now start the process of migrating data from source appliance to the new appliance.

Pre-upgrade checks result

Pre-upgrade checks will run, and will inform you if you have any errors or warnings. If any errors or warnings occur, you can review the VMware KB or vSphere documentation site for more information.

vRealize Operations or vRealize Log

You can choose to only migrate your configuration and inventory, or if you choose to you can move over the entire dataset from the old appliance. The more information you choose to copy, the longer the upgrade process will take. If you are using vRealize Operations or vRealize Log Insight, this data should already exist in an external system.

 Customer Experience Improvement Program

Specify if you would like to join the Customer Experience Improvement Program (CEIP) or not. CEIP data is completely anonymous and helps us with proactive support and metrics.

Image based (VADP) backup

Acknowledge that you have a backup in place, and continue with the final step of stage 2. With vSphere 6.5 we now have a built in file-based backup utility built into the VAMI. We highly recommend having a file-based or image based (VADP) backup in place in case of error.

Appliance shutdown.

Warning will show you that during this process the source vCenter Server appliance will be shutdown.

Exported source Appliance.

Step 1, the data will be exported from the source appliance.

Configuring FQDN, IP and services.

Step 2, the source appliance will be shutdown, and the new appliance will now maintain the identity of the old appliance configuring FQDN, IP and services.

Import data source appliance.

Step 3 begins, where we import data from the source appliance.

Post-upgrade Message

Post-upgrade tasks will display and inform you if additional action is needed.

vSphere Client

Your upgrade is now complete, and you can now access the vSphere Client!

Next Steps...

Your vCenter Server is now upgraded. Whats Next? We now will proceed on with upgrading the rest of the vSphere infrastructure. You can check the update sequence to update the rest of your remaining products including ESXi, VMware Tools, VM Compatibility and more. See the below links for more information.

 

Walkthrough: Upgrading vCenter Server 6.5 to vCenter Server 6.7 using VCSA CLI

Upgrading vCenter Server 6.5 to vCenter Server 6.7 using VCSA CLI

Upgrading vCenter Server 6.5 to vCenter Server 6.7 using VCSA CLI

This walkthrough will educate you on how to use the VCSA CLI installer to upgrade an Embedded vCenter Server from vSphere 6.5 to vSphere 6.7

Upgrade from vSphere 6.5 Update 2d to vSphere 6.7

Prior to upgrading your vCenter Server we should make sure we have a supported upgrade path. You cannot currently upgrade from vSphere 6.5 Update 2d to vSphere 6.7. http://www.vmware.com/go/interop should be used to check for supported upgrade paths within vCenter Server and other VMware products.

Prepare Your JSON Configuration File for CLI Upgrade

In order to use the vCenter Server Appliance CLI you must use the supplied JSON templates. This section will cover how to prepare your JSON configuration file for CLI based upgrades.

You can read more about the JSON configuration file within our documentation.

Prepare Your JSON Configuration File for CLI Upgrade

To access the CLI JSON templates we first need to navigate to our vCenter Server Appliance ISO and browse to the vcsa-cli-installer folder. Within this folder will be a folder called templates, and then we will drill down to the upgrade template for vcsa6.5. Once here you can see there are different templates for Embedded and External Deployments as well as if you will deploy your new VCSA to an ESXi host or VC.

JSON vCenter Server 6.5

Here is an example of the JSON we will use, it is to upgrade an embedded vCenter Server 6.5 to vCenter Server 6.7. When looking at this template first it may seem overwhelming but do not worry we will cover each section in more depth.

Destination vCenter Server (VC)

The first section we will look at is the section for the destination vCenter Server (VC). When upgrading from vSphere 6.5 to vSphere 6.7 the upgrade is not done in place, we deploy a brand new vCenter Server 6.7 and import the configuration from the vCenter Server 6.5 appliance. This will ask for for information on where you want to deploy the new vCenter Server Appliance 6.7. Here you will enter in the hostname, username, password, deployment network, datacenter, datastore, vm folder and cluster for the destination vCenter Server.

vCenter Server Appliance 6.7.

The next section covers configuring the vCenter Server Appliance 6.7. The JSON prompts for information such as thin provisioning, deployment size, inventory name, ssh status, temporary IP information and which user options you wish to migrate. We recommend using core as it will just move the configuration and inventory. For a full list of options please consult the documentation.

 vCenter Server Appliance 6.5

The next section will gather information about the source vCenter Server Appliance 6.5. We need to input information such as the vCenter Server that is managing our source appliance as well as credentials to access our source vCenter Server Appliance.

CEIP upgrading  advantage of Proactive Health Checks

The last section will ask if you wish to enable CEIP. It is recommended to enable CEIP when upgrading  to take advantage of Proactive Health Checks such as vSAN Health Checks, vSphere Health and Skyline. To learn more about what information is gathered please view: https://www.vmware.com/solutions/trustvmware/ceip.html

Syntax of the CLI Upgrade Command

Once your JSON template is filled out you can now move forward to execute the CLI upgrade. Before we do that lets explore the syntax of the CLI upgrade command.

vcsa-deploy upgrade path_to_the_json_file list_of_arguments

There are quite a few arguments that can be used, but i want to highlight the two most important ones --verify-template-only and --precheck-only.

You can find more about the syntax of the CLI upgrade command within the vSphere Documentation here or by running vcsa-deploy upgrade --help.

Syntax of the CLI Upgrade Command

To investigate how to use the vcsa-cli-installer we can run the vcsa-deploy command using the help option. This will give us syntax help as well as understand what each of the arguments do.

JSON template

Prior to executing our CLI upgrade against our live environment we should use the --verify-template-only argument to make sure we  properly filled out our JSON template. If there are any errors we can remediate them now prior to moving forward to the next step.

VCSA Cli Installer

Once we have successfully ran our template verification we can move forward with a precheck. This precheck is a dry-run of the upgrade that will not impact the live environment. It will run through the upgrade making sure there are no issues. Some of these checks make sure  you have chosen the correct VCSA size and have provided valid credentials Please note to successfully execute the precheck you will need to accept the eula and acknowledge the CEIP if that option was chosen.

Update pre-check

If our pre-check has succeeded we can move forward with the execution of our upgrade. If it has failed, you will be notified in the CLI of the errors and can consult the log files for more details.

Certificate Verification

To execute the upgrade we run the same syntax as previous just removing the --pre-check-only flag. Please note to successfully execute the upgrade you will need to accept the eula and acknowledge the CEIP if that option was chosen.

System Information upgraded appliance

If the upgrade succeeded we will be notified and will be given the system information for the upgraded appliance. If the upgrade failed for whatever reason we would be notified with an error message and the location to the log files

Thank You

Thank you for following along to upgrade your vCenter Server via the CLI. Hopefully this has helped educate you on the process to automate the upgrade of your vCenter Server.

You can find out more about automating the upgrade of the vCenter Server and Platform Services Controller in the following blog:

Blog vSphere

Walkthrough: Windows vCenter Server 6.5 Embedded Migration to VCSA 6.7

Walkthrough: Windows vCenter Server 6.5 Embedded Migration to VCSA 6.7

This walkthrough will cover the ability to migrate a Windows Embedded vCenter Server 6.5 to a VCSA 6.7. The Migration process is not only a migration but also an upgrade from 6.5 to 6.7.

Migration Overview

A vCenter Server Migration allows the Upgrade & Migration of data into the vCenter Server Appliance (VCSA). Migration is able to retain the identity of the source vCenter Server for both embedded and external deployment topologies. 

All supported vCenter Server databases as also supported for migration. As a default, the migration will migrate Inventory & Configuration data and leaves data such as Historical and Performance metrics optional to import. 

vCenter Server data Migrated to upgraded VCSA

A new version VCSA (upgraded) is deployed in Stage 1 and then source vCenter Server data is Migrated to the upgraded VCSA in Stage 2. It is important to understand that a vCenter Server migration is BOTH a Migration and an Upgrade. 

Windows vCenter Server 6.5

Begin by logging in your Windows vCenter Server 6.5

Mount the vCenter Server Appliance 6.7

Mount the vCenter Server Appliance 6.7 ISO to the Windows vCenter Server 6.5.

Migration directory from the vCenter Server Appliance 6.7

Browse to the migration-assistant directory from the vCenter Server Appliance 6.7 ISO 

 VMware-Migration-Assistant

Launch the VMware-Migration-Assistant application.

Administrator vsphere  password

Provide the Administrator@vsphere.local Single Sign-On password and press [Enter].

 Run pre-checks to validate

The migration-assistant will run pre-checks to validate your Windows vCenter Server is compliant and ready for the migration process. Note: Do not close the migration-assistant window at any point or the migration process will need to be restarted.

Windows vCenter Server Topology

The section shown is an environment and settings overview of the source Windows vCenter Server and Migration process. Listed is the source Windows vCenter Server topology, deployment size, and database information. 

Topology will not be changed during the migration process. An embedded deployment will remain the same when migrated. Also listed is information about the Migration settings and steps.

Target vCenter Server Appliance

The next section provides information stating the Windows vCenter Server 6.5 will be shutdown. In case of any issues during the migration, the target vCenter Server Appliance can be powered off and the Windows vCenter Server 6.5 can be powered on. 

During the migration process, no changes are made to the source Windows vCenter Server 6.5 providing easy rollback. Another warning is provided to not close the migration-assistant or the process will need to be restarted.

Run Migration Tool. 

Since the Windows vCenter Server will be shutdown during the migration process a separate Windows VM will be required to run the Migration Tool. 

Login to a separate Windows VM that is on a routable network to the Windows vCenter Server being migrated. 

Migration Tool from vCenter Server Appliance

Mount the vCenter Server Appliance 6.7 ISO. You can run the Migration Tool directly from the vCenter Server Appliance ISO or copy the contents locally and run it directly from the Windows VM.

VCSA Ui Installer

Go to the vcsa-ui-installer directory.

Installer win32 Directory

Go to the win32 directory.

 vCenter Server Appliance 6.7 installer.

Launch the vCenter Server Appliance 6.7 installer.

Migrate from the vCenter Server Appliance 6.7

Select Migrate from the vCenter Server Appliance 6.7 installer.

vCenter Server Appliance

The deployment workflow is a two stage process. The first stage deploys a new vCenter Server Appliance. The second stage configures the Appliance. Click [Next] on the Introduction screen.

License agreement

Review and accept the terms of the license agreement to continue. Click on [Next].

Qualified Domain name (FQDN)

Provide the source Windows vCenter Server fully qualified domain name (FQDN) or IP address and vSphere Single Sign-On password. Click on [Next].

Verify Thumbprint

Accept the SSL SHA1 thumbprint by clicking on [Yes].

Management vCenter Server

Provide the fully qualified domain name (FQDN) of the vSphere ESXi Host or management vCenter Server. This will be the initial deployment target for the appliance. Provide a User Name and Password with privileges to create a VM. Click on [Next].

Certificate Warning

Accept the SSL SHA1 thumbprint by clicking on [Yes].

 datacenter or VM folder VCSA

Select a datacenter or VM folder to create the VCSA 6.7 in.  Click on [Next].

 Migration to VCSA 6.7

Select the compute resource to deploy the VCSA 6.7 in.  Click on [Next].

VM vCenter Server Appliance

Provide a VM name (inventory name) for the vCenter Server Appliance. Enter a secure password and click on [Next].

Appliance Deployed Size

The installer provides the option to select an [Appliance size] and [Storage size].  Select the required appliance deployment size. The installer will default to the current vCenter Server size which can be increased. Optionally, select the appliance [Storage size] to increase the initial disk size for Stats, Events, Alarms, and Tasks. Click on [Next]. Note: The Appliance deployment size can not be set to a size smaller than the initial vCenter Server size. The migration-assistant will display the initial vCenter Server Deployment size. 

vSphere Host

Select a datastore from the list provided by the vSphere Host and click on [Next].

Configure network setting

Select the Network, IP version, Temporary IP address, Subnet mask, Gateway, and DNS servers. Click on [Next].  Note: Ensure that the system name has been provided both A and PTR DNS records for forward and reverse DNS resolution.

Platform Services Controller.

Review the Stage 1 summary settings. Click [Finish] to start the deployment of the VCSA 6.7 with Embedded Platform Services Controller.

Deployment progress.

The installer will begin to deploy the VCSA 6.7 appliance to the vSphere ESXi Host. Monitor the deployment progress.

 vSphere ESXi Host.

The installer will power on the VCSA 6.7 after deployment to the vSphere ESXi Host.

Deployment of vCenter Server Appliance

The deployment of vCenter Server Appliance with an Embedded Platform Services Controller (Stage 1) has completed. Click on [Continue] to proceed to Stage 2. Note: If [Close] is selected Stage 2 can be continued from the VMware vSphere Appliance Management Interface (https://FQDN or IP Address of vCenter Server Appliance:5480).

Embedded Platform Services Controller

Start Stage 2 configuration of the vCenter Server Appliance 6.7 with an Embedded Platform Services Controller by clicking on [Next].

Connect vCenter Server

Connect to the source vCenter Server by providing the Windows Server FQDN name and the Single Sign-On password. Click [Next] to continue. 

Accept Certificate Warning

Accept the certificate, click [Next] to continue. 

Pre- Migration Check

The installer will connect to the source Windows vCenter Server and save all parameters.

Join AD Domain

If the Windows vCenter Sever 6.5 was joined to Active Directory provide an account to update the object information with the vCenter Server Appliance password. Click on [Next].

 vCenter Server configuration inventory

Select which data to migrate from the Windows vCenter Server 6.5 to the vCenter Server Appliance 6.7. By default the vCenter Server configuration, inventory, and alarm data is migrated. Select the other options to migrate events and tasks only or additionally migrate performance and historical data as well. Click on [Next].

 VMware Customer Experience Improvement Program (CEIP)

Join the VMware Customer Experience Improvement Program (CEIP) which enables features such as, vSphere & VSAN Health. To learn more: https://www.vmware.com/solutions/trustvmware/ceip.html After a selection is made, Click [Next].

Embedded Platform Services Controller.

Review the Stage 2 summary settings. Validate a backup of the source Windows vCenter Server 6.5 has been taken. Click [Finish] to start the configuration of the VCSA 6.7 with Embedded Platform Services Controller.

Shutdown Warning

A warning is displayed as a reminder that the source Windows vCenter Server 6.5 will be powered off once the network configuration is enabled on the target VCSA 6.7 appliance. Click [OK] to continue.

NOTE: Once the migration process is started it can not be paused or stopped.

Data Transfer

The data transfer process from the source Windows vCenter Server 6.5 is started. This will copy the configuration data that was selected in a previous step.

Appliance Setup Process

Once the data has been copied from the source Windows vCenter Server 6.5 it will be shutdown. The shutdown will allow the vCenter Server Appliance 6.7 to assume the identity of the source Windows vCenter Server. The identity will include System Name (OS), IP address, UUID, Certificates, etc.

setup of the vCenter Server Appliance 6.7

The setup of the vCenter Server Appliance 6.7 will begin.

Data copied from Windows vCenter Server

Once the vCenter Server Appliance setup is completed the data copied from the source Windows vCenter Server is now imported.

 TLS settings new version of vSphere 6.7

An informational message will appear to update DHCP and TFTP settings for the new version of Auto Deploy. This is only required if the Auto Deploy service will be used.  Also information about TLS settings for the new version of vSphere 6.7 is displayed as TLS 1.0 & 1.1 are now disabled by default. Click on [Close].

vCenter Server Appliance 6.7

The configuration, setup, and data import of the vCenter Server Appliance 6.7 has completed. Click on the links provided by the installer to launch the Getting Started Page. Click on [Close] to exit from the installer.

Launch vSphere Client

From the Getting Started Page. Click on [Launch vSphere Client (HTML5)] to continue. 

Login  vCenter Server Appliance 6.7 

Login to the vCenter Server Appliance 6.7 

Windows vCenter Server 6.5

Once logged in you can verify the installed vCenter Server version from the Summary tab of the vCenter Server view. 

 VMware vSphere Blog

This concludes this walkthrough on vCenter Server 6.5 Embedded Migration to Appliance 6.7. To learn more, visit the VMware vSphere Blog at blogs.vmware.com/vsphere

Walkthrough: Windows External PSC 6.5 Migration to an External PSC 6.7 Appliance

Windows External PSC 6.5 Migration to an External PSC 6.7 Appliance

This walkthrough will cover the ability to migrate a Windows Platform Services Controller (PSC) 6.5 to a PSC Appliance 6.7. The Migration process is not only a migration but also an upgrade from 6.5 to 6.7.

 

Migration Workflow

Steps 1 and 2 of the Migration Workflow will be covered in this Platform Services Controller walkthrough. 

Migration assistant directory.

Mount the vCenter Server Appliance 6.7 ISO to the Windows Platform Services Controller 6.5 server and navigate to the migration assistant directory.

VMware-Migration Assistant.

Launch the VMware-Migration Assistant.exe

Administrator vsphere password

Provide the Administrator@vsphere.local Single Sign-On password and press [Enter].

Windows Platform Services Controller

The migration-assistant will run pre-checks to validate the Windows Platform Services Controller is compliant and ready for the migration process.

Note: Do not close the Migration Assistant window at any point or the migration process will need to be restarted.
Windows Platform Services Controller 6.5

 The migration-assistant output provides an environment and settings overview of the source Windows Platform Services Controller. Also, the migration-assistant provides information about the migration steps and notification stating the Windows Platform Services Controller 6.5 will be shut down. In case of any issues during the migration process, the target Platform Services Controller Appliance can be powered off and the Windows Platform Services Controller 6.5 can be powered on, providing easy rollback. During the migration process, no changes are made to the source Windows Platform Services Controller 6.5 providing easy rollback. Another warning is provided to not close the migration-assistant or the migration process will need to be restarted. 

 vCenter Server Appliance ISO.

Next, connect to an available workstation or jump-box that has access to the same routable network as the Windows Platform Services Controller 6.5 to run the vCenter Server Appliance ISO from. Mount the vCenter Server Appliance ISO.

Migration Tool directly

Mount the vCenter Server Appliance 6.7 ISO. You can run the Migration Tool directly from the vCenter Server Appliance ISO or copy the contents locally and run it directly from the Windows VM.

 VCSA Ui installer directory.

Go to the vcsa-ui-installer directory.

VCSA win32 directory.

Go to the win32 directory.

vCenter Server Appliance 6.7 installer.

Launch the vCenter Server Appliance 6.7 installer.

Migrate from vCenter Server Appliance 6.7

Select Migrate from the vCenter Server Appliance 6.7 installer

Platform Services Controller Appliance

The deployment workflow is a two stage process. The first stage deploys a new Platform Services Controller Appliance. The second stage configures the Appliance. Click [Next] on the Introduction screen.

License agreement

Review and accept the terms of the license agreement to continue. Click on [Next].

 Qualified Domain name (FQDN) or IP

Provide the source Windows Platform Services Controller fully qualified domain name (FQDN) or IP address and vSphere Single Sign-On password. Click on [Next].

Thumbprint of certificate

Accept the SSL SHA1 thumbprint of the certificate by clicking on [Yes].

Target Platform Services Controller 6.7 appliance.

Provide the fully qualified domain name (FQDN) of the vSphere ESXi Host or management vCenter Server. This will be the initial deployment target for the Platform Services Controller 6.7 appliance. Provide a User Name and Password with privileges to create a VM. Click on [Next].

Certificate Warning

Accept the SSL SHA1 thumbprint of the certificate by clicking on [Yes].

Platform Services Controller VM

Select a datacenter or VM folder to create the Platform Services Controller VM in.  Click on [Next].

Deploy Platform Services Controller VM

Select the compute resource to deploy the Platform Services Controller VM.  Click on [Next].

Target Appliance VM

Provide a VM name (inventory name) for the Platform Services Controller Appliance. Enter a secure password and click on [Next].

vSphere Host

Select a datastore from the list provided by the vSphere Host and click on [Next].

Configure network setting

Select the Network, IP version, Temporary IP address, Subnet mask, Gateway, and DNS servers. Click on [Next]. 

Note: Ensure that the system name has been provided both A and PTR DNS records for forward and reverse DNS resolution.

 External Platform Services Controller 6.7.

Review the Stage 1 summary settings. Click [Finish] to start the deployment of the External Platform Services Controller 6.7.

Deployment appliance progress.

The installer will begin to deploy the Platform Services Controller 6.7 appliance to the vSphere ESXi Host. Monitor the deployment progress.

Deployment to vSphere ESXi Host.

The installer will power on the Platform Services Controller after deployment to the vSphere ESXi Host.

VMware vSphere Appliance Management Interface

The deployment of the External Platform Services Controller (Stage 1) has completed. Click on [Continue] to proceed to Stage 2.

Note: If [Close] is selected Stage 2 can be continued from the VMware vSphere Appliance Management Interface (https://FQDN or IP Address of vCenter Server Appliance:5480)

Target Platform Services Controller 6.7

Stage 2 will copy the data from the source Windows 6.5 PSC to the target Platform Services Controller 6.7 appliance. Click [Next] to proceed with Stage 2.

Windows PSC save all Parameters.

The installer will connect to the source Windows PSC and save all parameters.

Platform Services Controller 6.7 appliance

If the Windows Platform Services Controller 6.5 was joined to Active Directory, provide an account that has rights to join computers to the domain so that the target Platform Services Controller 6.7 appliance can also join the same domain.  Click on [Next].

Customer Experience Improvement Program (CEIP)

Join the VMware Customer Experience Improvement Program (CEIP) which enables features such as, vSphere & VSAN Health. To learn more: https://www.vmware.com/solutions/trustvmware/ceip.html After a selection is made, Click [Next].

Windows Platform Services Controller 6.5

Review the Stage 2 summary settings. Validate a backup of the source Windows Platform Services Controller 6.5 has been taken.  Click [Finish] to start the configuration of the Platform Services Controller 6.7 appliance.

Shutdown Warning Displayed

A warning is displayed as a reminder that the source Windows Platform Services Controller 6.5 will be powered off once the network configuration is enabled on the target Platform Services Controller 6.7 appliance. Click [OK] to continue.

NOTE: Once the migration process is started it can not be paused or stopped. 

Data Transfer Process

The data transfer process from the source Windows Platform Services Controller is started. This will copy the configuration data that was selected in a previous step.

Data copied from Windows Platform Services Controller

Once the data has been copied from the source Windows Platform Services Controller it will be shutdown. The shutdown will allow the Platform Services Controller 6.7 appliance to assume the identity of the source Windows Platform Services Controller 6.5. The identity will include System Name (OS), IP address, UUID, Certificates, etc

The Platform Services Controller 6.7 appliance

The setup of the Platform Services Controller 6.7 appliance will begin

Windows Platform Services Controller imported.

Once the Platform Services Controller setup is completed the data copied from the source Windows Platform Services Controller is imported.

New version of vSphere 6.7  TLS Setting

An information message will appear about TLS settings for the new version of vSphere 6.7 as TLS 1.0 & 1.1 are now disabled by default. Click on [Close].

Complete Platform Services Controller 6.7 appliance

The configuration, setup, and data import of the Platform Services Controller 6.7 appliance has completed. Click on the link provided by the installer to launch the Getting Started Page. Click on [Close] to exit from the installer.

Platform Services Controller web interface

The Platform Services Controller web interface (https;//FQDN/psc) is now integrated within the vSphere Client (HTML5) under the Administration section. 

VMware vSphere Blog

This concludes this walkthrough on Windows Platform Services Controller 6.5 External Migration to the PSC 6.7 Appliance To learn more, visit the VMware vSphere Blog at blogs.vmware.com/vsphere.

Walkthrough: Windows vCenter Server 6.5 External Migration to VCSA 6.7

Windows vCenter Server 6.5 External Migration to VCSA 6.7

This walkthrough will cover the ability to migrate a Windows vCenter Server 6.5 to a vCenter Server Appliance (VCSA) 6.7. The Migration process is not only a migration but also an upgrade from vCenter Server 6.5 to 6.7.

vCenter Server Appliance (VCSA)

A vCenter Server Migration allows the Upgrade & Migration of data into the vCenter Server Appliance (VCSA). Migration is able to retain the identity of the source vCenter Server for both embedded and external deployment topologies. All supported vCenter Server databases as also supported for migration. As a default, the migration will migrate Inventory & Configuration data and leaves data such as Historical and Performance metrics optional to import. 

Server migration is BOTH a Migration and an Upgrade

A new version VCSA (upgraded) is deployed in Stage 1 and then source vCenter Server data is Migrated to the upgraded VCSA in Stage 2. It is important to understand that a vCenter Server migration is BOTH a Migration and an Upgrade. 

Migration External Workflow

Steps 4, 5, and 6 of the Migration Workflow will be covered in this vCenter Server walkthrough. 

Windows vCenter Server 6.5.

Begin by logging in your Windows vCenter Server 6.5.

vCenter Server Appliance 6.7 ISO

Mount the vCenter Server Appliance 6.7 ISO to the Windows vCenter Server 6.5.

Migration-assistant directory

The migration-assistant directory on the vCenter Server Appliance 6.7 ISO can be copied locally to the Windows vCenter Server 6.5 or run directly from the ISO. In this example environment, the files were accessed directly from the vCenter Server Appliance 6.7 ISO.

Migration-Assistant application

Launch the Migration-Assistant application (VMware-Migration-Assistant.exe)

Administrator vsphere local password

Provide the Administrator@vsphere.local Single Sign-On password and press [Enter].

Service account credentials

If your Windows vCenter Server service is running as a service account you will be prompted to provide the service account credentials and press [Enter].

vCenter Server Migration process

The migration-assistant will run pre-checks to validate your Windows vCenter Server is compliant and ready for the migration process. Note: Do not close the migration-assistant window at any point or the migration process will need to be restarted

Extensions Registered with vCenter Server.

The migration-assistant output can be broken up into three sections. The first is "Warning". Here there will be information about extensions registered with vCenter Server. Resolutions for each warning are provided. Go through each warning and plan accordingly before proceeding.

Windows vCenter Server and Migration process

The second section is an environment and settings overview of the source Windows vCenter Server and Migration process. Listed is the source Windows vCenter Server topology, deployment size, and database information. Notice of additional products that will be migrated is also shown. In this example, the vSphere Update Manager will also be migrated to the new VCSA 6.7. Topology will not be changed during the migration process. An embedded deployment will remain the same when migrated. Also listed is information about the Migration settings and steps.

Windows vCenter Server 6.5 Easy Rollback

The third and final section provides information stating the Windows vCenter Server 6.5 will be shutdown. In case of any issues during the migration, the target vCenter Server Appliance 6.7 can be powered off and the Windows vCenter Server 6.5 can be powered on. During the migration process, no changes are made to the source Windows vCenter Server 6.5 providing easy rollback. Another warning is provided to not close the migration-assistant or the process will need to be restarted. 

vCenter Server Appliance 6.7

The Windows vCenter Server will be shutdown during the migration process and separate Windows machine will be required to run the Migration Tool. Login to a Windows machine that is on a routable network to the Windows vCenter Server being migrated. Mount the vCenter Server Appliance 6.7 ISO.

VCSA Ui Installer directory.

Go to the vcsa-ui-installer directory.

vSphere win32 directory.

Go to the win32 directory.

Launch vCenter Server Appliance 6.7

Launch the vCenter Server Appliance 6.7 installer.

Migrate from the vCenter Server Appliance 6.7

Select [Migrate] from the vCenter Server Appliance 6.7 installer

 Introduction screen

The deployment workflow is a two stage process. The first stage deploys a new vCenter Server Appliance. The second stage configures the Appliance. Click [Next] on the Introduction screen

License agreement

Review and accept the terms of the license agreement to continue. Click on [Next].

Qualified Domain Name (FQDN) or IP address

Provide the source Windows vCenter Server fully qualified domain name (FQDN) or IP address and vSphere Single Sign-On password. Click on [Next].

Thumbprint  certificate

Accept the SSL SHA1 thumbprint by clicking on [Yes]

Management vCenter Server

Provide the fully qualified domain name (FQDN) of the vSphere ESXi Host or management vCenter Server. This will be the initial deployment target for the appliance. Provide a User Name and Password with privileges to create a VM. Click on [Next].

Certificate Warning VCSA

Accept the SSL SHA1 thumbprint by clicking on [Yes].

 vCenter Server Appliance VM

Select a datacenter or VM folder to create the vCenter Server Appliance VM in.  Click on [Next]

 vCenter Server Appliance VM

Select the compute resource to deploy the vCenter Server Appliance VM.  Click on [Next]

Provide a VM  vCenter Server Appliance

Provide a VM name (inventory name) for the vCenter Server Appliance. Enter a secure password and click on [Next].

vCenter Server Deployment size

The installer provides the option to select an [Appliance size] and [Storage size]. Select the required appliance deployment size. The installer will default to the current vCenter Server size which can be increased. Optionally, select the appliance [Storage size] to increase the initial disk size for Stats, Events, Alarms, and Tasks. Click on [Next]. Note: The Appliance deployment size can not be set to a size smaller than the initial vCenter Server size. The migration-assistant will display the initial vCenter Server Deployment size

 vSphere Host

Select a datastore from the list provided by the vSphere Host and click on [Next]

Configure network setting

Select the Network, IP version, Temporary IP address, Subnet mask, Gateway, and DNS servers. Click on [Next].  Note: Ensure that the system name has been provided both A and PTR DNS records for forward and reverse DNS resolution.

Deployment of vCenter Server Appliance 6.7

Review the Stage 1 summary settings. Click [Finish] to start the deployment of the vCenter Server Appliance 6.7

vCenter Server Appliance deployment progress

The installer will begin to deploy the vCenter Server Appliance to the vSphere ESXi Host. Monitor the deployment progress

vCenter Server Appliance 6.7 after deployment

The installer will power on the vCenter Server Appliance 6.7 after deployment to the vSphere ESXi Host.

VMware vSphere Appliance Management Interface

The deployment of vCenter Server Appliance (Stage 1) has completed. Click on [Continue] to proceed to Stage 2. Note: If [Close] is selected Stage 2 can be continued from the VMware vSphere Appliance Management Interface (https://FQDN or IP Address of vCenter Server Appliance:5480).

Configuration of vCenter Server Appliance 6.7

Start Stage 2 configuration of the vCenter Server Appliance 6.7 by clicking on [Next].

Pre Migration check

The pre-migration check results screen will appear. The same warnings and resolutions that were displayed in the migration-assistant will appear here. Make sure proper planning is in place to resolve these warnings after the vCenter Server Appliance configuration is completed. Click on [Close].

Windows vCenter Sever 6.5 joined

If the Windows vCenter Sever 6.5 was joined to Active Directory provide an account to update the object information with the vCenter Server Appliance password. Click on [Next].

vCenter Server configuration

Select which data to migrate from the Windows vCenter Server 6.5 to the vCenter Server Appliance 6.7. By default the vCenter Server configuration, inventory, and alarm data is migrated. Select the other options to migrate events and tasks only, migrate performance and historical data, or additionally migrate historical data in the background after deployment. Click on [Configuration and historical data (events and tasks)] to continue

Migrate historical data

In this example environment, we will migrate historical data in the background after deployment. Click on [Next].

Validate backup Windows vCenter Server 6.5

Review the Stage 2 summary settings. Validate a backup of the source Windows vCenter Server 6.5 has been taken. Click [Finish] to start the configuration of the vCenter Server Appliance 6.7.

Target vCenter Server Appliance 6.7

A warning is displayed as a reminder that the source Windows vCenter Server 6.5 will be powered off once the network configuration is enabled on the target vCenter Server Appliance 6.7. Click [OK] to continue. NOTE: Once the migration process is started it can not be paused or stopped

Data Transfer Process from Windows vCenter Serve

The data transfer process from the source Windows vCenter Server is started. This will copy the configuration data that was selected in a previous step to the vCenter Server Appliance.

Windows vCenter Server  shutdown

Once the data has been copied from the source Windows vCenter Server it will be shutdown. The shutdown will allow the vCenter Server Appliance 6.7 to assume the identity of the source Windows vCenter Server. The identity will include System Name (OS), IP address, UUID, Certificates, etc

Setup of vCenter Server Appliance

The setup of the vCenter Server Appliance will begin

Data copied from Windows vCenter Server

Once the vCenter Server Appliance 6.7 setup is completed the data copied from the source Windows vCenter Server 6.5 is now imported

TLS settings for new version of vSphere

An information message will appear to update DHCP and TFTP settings for the new version of Auto Deploy. This is only required if the Auto Deploy service will be used. Also information about TLS settings for the new version of vSphere 6.7 is displayed as TLS 1.0 & 1.1 are now disabled by default. Click on [Close].

Data import vCenter Server Appliance 6.7 completed

The configuration, setup, and data import of the vCenter Server Appliance 6.7 has completed. Click on the links provided by the installer to launch the Getting Started Page. Click on [Close] to exit from the installer

Login to vCenter Server Appliance 6.7

Login to the vCenter Server Appliance 6.7

 vCenter Server view.

Once logged in you can verify the installed vCenter Server version from the Summary tab of the vCenter Server view.

 VMware vSphere Blog

This concludes this walkthrough on vCenter Server 6.5 External Migration to Appliance 6.7. To learn more, visit the VMware vSphere Blog at blogs.vmware.com/vsphere

Blog: Upgrading Platform Services Controller and vCenter Server via the CLI Installer

The first topic we will cover in our Automating your vSphere Upgrade series is updating our core infrastructure. Upgrading Platform Services Controller(PSC) and vCenter Server via the CLI installer.

In our workshops one of the common things I hear is that most folks aren’t using the CLI based tools that have been included in the installer. I am a huge fan of these as they make migrations and upgrades seamless–especially when having to perform the task if you have multiple PSC’s and vCenter Servers. Using the CLI tools don’t have to be intimidating, as we go through this blog we will cover some how-to’s and benefits of using the CLI based approach.

 vSphere Upgrade Process

When we start our vSphere Upgrade the first thing we want to do is to upgrade our PSC and vCenter Server before updating other components. If we happen to be using an Embedded PSC deployment the upgrade is simple, we can do the upgrade in one step (Step 1 and Step 2 combined). However, if we are using an External PSC deployment we must upgrade all of our PSC’s within the same SSO domain first prior to upgrading any vCenter Servers–so this becomes a multi-step process.

External PSC deployment

For this upgrade scenario we will be performing an upgrade from an External PSC deployment using appliances on vSphere 6.0 to an External PSC deployment using appliances on vSphere 6.7.

Prepare Your JSON Configuration File for CLI Upgrade

When doing a CLI based upgrade, we use a configuration file template (JSON) that is part of the vCenter Server Appliance (VCSA) ISO. When you mount the ISO you will see a directory labelled vcsa-cli-installer and within that folder is a directory called templates. Once you are here you have the option to see the CLI templates for install, migrate and upgrade. As a reminder a migration is when we are moving from a vCenter Server on Windows, and an upgrade is when we are moving from VCSA to VCSA.

Since we are doing an upgrade we will browse to that folder and we are left seeing a vcsa6.0 and vcsa6.5 directory. The information we need when coming from each version is different so there is a unique set of templates for each version. Since we are upgrading from a vSphere 6.0 deployment we will head into the vcsa6.0 directory.

Once we are in this directory we can see a few different templates. We have a template for an embedded deployment, external PSC and external vCenter Server. Each template has an associated version whether or not we will be connecting to a vCenter Server or an ESXi host directly. The embedded template is for an embedded deployment which does both PSC and vCenter Server at the same time as we mentioned above, and the PSC and VCSA are separate templates as we need to do these one at a time.

PSC_on_VC.json.

Since we have an External PSC deployment and we are using a vCenter Server, we will first open the PSC_on_VC.json.

Platform Services Controller  vCenter Server

When opening this file at first glance you might say WOAH! That looks complicated, but there is quite a bit of extra text explaining each field. Lets fill in the blanks with the required information and take another look.

 PSC’s per SSO Domain

This looks a lot better, we can clearly see the details it is asking for. The vCenter Server to deploy the new appliance to, the appliance information, the temporary IP to use, and then last but not least the source information for the appliance we are upgrading. If we have a deployment where there are multiple PSC’s we could see how easy it would be to make a copy of this file, and edit lines 17 and 41 putting in the second PSC and then re-saving. How much time saving could this be!? With vSphere 6.5 allowing 10 PSC’s per SSO domain and vSphere 6.7 allowing 15 this could be quite a bit of time saved!

Next up, its time to upgrade our vCenter Server. To get our JSON file ready we will head back and grab the vCSA_on_VC.json template. Also remember that if you happen to have multiple VCSA’s to upgrade you can easily update lines 16 ,17 and 40 to upgrade other appliances in your environment.

Upgrade using CLI.

Certain sensitive fields such as passwords can be left blank if chosen. When the CLI installer is run it will prompt for the password during runtime.

Now that we have prepared our templates for our upgrade, the next section we will jump into how to actually perform our upgrade using the CLI.

More information on preparing the JSON template can be found here.

Upgrade a vCenter Server Appliance or Platform Services Controller Appliance by Using the CLI

CLI templates in hand, its now for the fun. Using these templates we will automate our upgrade. vSphere 6.0 originally introduced this concept of a CLI based tool, however its been enhanced with vSphere 6.7. With vSphere 6.7 we now have a “batch template” technology built into the installer. Prior to vSphere 6.7 we had to run the installer against a single JSON file and wait for it to finish, we would then have to manually kick off the second JSON file when the previous one completes. With the batch upgrade we can put multiple JSON files into a single directory and point the installer to the directory and it is smart enough to map out the dependencies and upgrade the PSC’s first and then the vCenter Servers.

Before we actually perform our upgrade, I want to explain some of the benefits of the CLI installer. If we happened to be using the GUI based upgrade, everything in that upgrade would have to be manually entered into the GUI and obviously that is susceptible to typos and errors. Also, if we happened to enter some incorrect information and had to retry our upgrade we would again have to re-type all that information. What if we had a way to perform an upgrade test without ever touching our production environment? With the CLI Installer we do! And its called a pre-check. When running the CLI installer with the –precheck-only flag we have the ability to go through a full dry run of our upgrade. If we happened to have a typo, insufficient capacity or any other errors it would spit this out, and we could easily correct the settings.

To run our CLI based installer we will mount our vSphere 6.7 media as that is the version we are going to. We will again navigate to the vcsa-cli-installer directory. From here depending on the operating system of the machine we are on we will either navigate to the lin64, win32 or mac folder to use the supported installer for that operating system.

Here we will see quite a few files, but the one we want to focus on is vcsa-deploy.exe in the win32 folder since I will be running this from a windows machine. If we run .\vcsa-deploy.exe upgrade it will give us the details on how to properly use the CLI tool.

Execute  vcsa-deploy

As I mentioned previously one of the benefits of using the CLI tool is that you can execute a pre-check of your template against the environment to make sure things will pass. Usually with upgrades and migrations a big issue we see with them failing is due to a smaller appliance size being chosen for the new appliance or insufficient capacity in the vCenter Server environment. In this environment we will execute our vcsa-deploy utilizing the pre-check option and see our results.

To run the pre-check I ran the following command: .\vcsa-deploy.exe upgrade –no-ssl-certificate-verification –accept-eula –acknowledge-ceip –precheck-only C:\scripts\6.7\upg60to67\ 

I chose to point this to the folder to take advantage of the batch upgrade vs pointing it to the individual file, as I mentioned earlier it is smart enough to map out the dependencies as we can see from the below image.

 vCenter Server services

Once the pre-check runs through we will either get a success or failure. In the image below my vCenter Server services were not running so the pre-check failed.

Run Pre Check

Now that we have the service running and re-run our pre-check we can see everything is successful and we can now proceed to remove the –precheck-only flag from our command.

SSL Certificate Verification

.\vcsa-deploy.exe upgrade –no-ssl-certificate-verification –accept-eula –acknowledge-ceip C:\scripts\6.7\upg60to67\ 

The upgrade process is now happening without any additional user input. If you need to step away for lunch or if a co-worker needs you there is no additional action that is needed until the end. If you were using the GUI based approach once Stage 1 where the appliance is deployed is complete you have to manually start Stage 2 to configure the upgraded appliance. With the CLI based installer this is not needed. When our upgrade is complete we will be presented with the vCenter Server and login information as we can see below.

Information on Upgrading
More information on Upgrading your PSC and vCenter Server via the CLI can be found here.

Conclusion

Automating your vSphere Upgrade does not have to be scary or hard, as we went through the steps its actually quite easy. Now that we have our PSC and vCenter Server updated we can now proceed to our next step which is automating the upgrade of our ESXi hosts.

 Article: https://blogs.vmware.com/vsphere/2018/09/upgrading-platform-services-controller-and-vcenter-server-via-the-cli-installer.html

 Date: 2018-10-29

Blog: Upgrading vCenter Server via the GUI Installer

vSphere Upgrade Series Part 2: Upgrading vCenter Server

In part 1 of the vSphere Upgrade Series, Preparing to Upgrade, we covered getting started with our prerequisites, compatibility, and also prepared the vSphere Update Manager (VUM) server to migrate its data to the VCSA 6.7 during the upgrade. In part 2 we will cover the vCenter Server Upgrade to 6.7. Let’s begin.

vCenter Server Upgrade

Now that VUM has passed its Migration Assistant pre-checks, we can move to the vCenter Server Upgrade. I am also assuming here that you have a backup of the vCenter Server prior to upgrading.

We begin by mounting the VCSA installation ISO to an Admin workstation that is on a routable network to the vCenter Server we will be upgrading. Browse the ISO and open the “vcsa-ui-installer” folder then the corresponding folder for your OS. I am running this from a Windows system so I will open the “win32” folder.

Upgrading vCenter Server

Next run the application “installer.exe” with Administrator Rights. This will launch the vCenter Server Appliance Installer to begin Stage 1.

NOTE: The upgrade of the vCenter Server is broken up into two stages, Stage 1 & Stage 2. Stage 1 is the deployment of a new VCSA and Stage 2 is where all of the configuration data and inventory are imported into the newly upgraded vCenter Server.

Begin by clicking Upgrade.

Administrator  vCenter Server

Stage 1

Step 1: This is the introduction and an explanation of the two Stages of the Upgrade. Click Next to continue.

vCenter Server Upgrade

Step 2: Review the EULA, check the box to accept the terms of the license agreement, and then click Next to continue.

License agreement

Step 3a: Enter the source vCenter Server that you will be Upgrading by its FQDN or IP address. Click Connect To Source to reveal the additional fields.

Upgrading  FQDN or IP address

Step 3b: Complete each required field for SSO as well as the information about the ESXi host that manages the source vCenter Server. Then click Next to continue.

ESXi host  vCenter Server.

Step 3c: You will prompted to verify the SSL Certificates. Review and click Yes to continue.

Warning Certificate

Step 4a: Specify the target host or vCenter Server to which the new VCSA will be deployed to. Click Next to continue.

 SSL Certificate and thumbprints

Step 4b: When prompted, review the SSL Certificate and thumbprints then click Yes to continue.

Warning Certificate

Step 5: Specify the Virtual Machine name (this is only the Inventory name) and set the password for the VCSA that will be deployed during the upgrade. Click Next to continue.

NOTE: During an upgrade of the source VCSA, a new VCSA virtual machine is deployed and configurations are imported to the new vCenter Server Appliance. The source VCSA will be powered off and should be either removed from inventory, or have its network adapter disabled after the upgrade completes. 
Storage Size

Step 6: Select the deployment size for the vCenter Server. If more storage is needed than the default sizing, choose the “Storage Size” dropdown for more choices. Storage size changes will be reflected in the table below the selection dropdown in the Storage (GB) column.

It may be necessary to edit the storage size from Default to Large or X-Large if importing the optional Historical & Performance Data (see image for more details).

NOTE: If you plan to use vCenter High Availability (VCHA) after you upgrade your vCenter Server, the smallest deployment size supported for VCHA is Small. 

Click Next to continue.

 vCenter Server Appliance Disk Mode

Step 7: Select the datastore location for the vCenter Server Appliance. The option to also Enable Thin Disk Mode is available, if you require it.

Click Next to continue.

Deploy the new VCSA

Step 8: Configure the temporary network settings that are required to deploy the new VCSA. Be sure to add at least 1 DNS server. Once all required fields are completed, click Next to continue.

Network Configure setting

Step 9: Review all settings of Stage 1 prior to Upgrade. Once verified, click Finish to continue and kick off Stage 1 of the vCenter Server Upgrade.

Deploying new vCenter Server

Stage 1 of deploying the new vCenter Server Appliance is now underway.

 RPM installs

Once the VCSA is deployed and all RPM installs are completed in Stage 1, you can click Continue to move on to Stage 2.

 vSphere Update Manager (VUM)

Stage 2

Stage 2 of the upgrade is when the data from the source vCenter Server as well as vSphere Update Manager (VUM) is imported into the newly deployed VCSA.

Step 1: Review the details of the Stage 2 process and then Click Next to continue.

Kick off series  pre-checks

This will kick off a series of pre-checks on the source vCenter Server.

Pre Updated Check

Step 2: Once pre-checks have completed, results will be shown on screen. Review any warnings given, as well as the resolutions to these warnings. In my upgrade scenario I had a few warnings, one reminding me to change DRS which we did before we began, and others that I validated were ok to proceed in this situation.

Review and click Close to continue.

Inventory & Configuration data

Step 3: Select the data that you will require to be imported. The Inventory & Configuration data is moved by default, any historical data (events, tasks, performance, etc) is optional to import. This is offered to shorten the upgrade and migration of data into the new VCSA. Make the required choice, and then click Next to continue.

 VMware Customer Experience Improvement Program or CEIP

Step 4: Join the VMware Customer Experience Improvement Program or CEIP. Joining this program is optional but when you do join, it helps VMware to improve our products and services, fix problems and advise you on how best to deploy and use our products. CEIP is also required to enable the vSAN health check services.

To understand this better, please review additional information regarding the CEIP and its purpose.

Once a choice has been made, click Next to continue.

Configure CEIP

Step 5: Review all setting choices here and once complete, click Finish to continue.

vCenter Server destination VCSA.

The prompt here is a reminder that the source vCenter Server will be powered down once all network configuration is enabled on the destination VCSA.

Click OK to continue.

Data Exported from vCenter Server

Stage 2 begins. Data is exported from the source vCenter Server and prepared for import.

vCenter Server services

Next, vCenter Server services are started on the destination VCSA.

vCenter Server imported

Last, the copied data from the source vCenter Server is imported to the destination VCSA.

TLS changes in vSphere 6.7

When all data has been imported to the destination VCSA, the process is complete. Messages are presented at this step as informational, such as a notice about TLS changes in vSphere 6.7.

Review these notices then click Close to continue.

 vCenter Server Upgrade

Stage 2 of the vCenter Server Upgrade is now completed.

Click Close to continue.

vCenter Server splash

Closing the installer will launch the vCenter Server splash page allowing you to login via the vSphere Client on HTML5.

Since the vSphere Web Client (Flex) is now deprecated, I will use the HTML5 vSphere Client because it is now our default client and it contains 95% of all workflows as compared to vSphere 6.5 Update 1 that contained 90% of workflows. The HTML5 vSphere Client will be fully featured by the Fall of 2018.

Click the button “Launch vSphere Client (HTML5)” to continue.

Launch vSphere Client (HTML5)

Enter the administrator credentials (SSO administrator or other administrator with access to vSphere) and login to view the vCenter Server and hosts.

Login to view the vCenter Server and hosts.

Now we will verify the vCenter Server is now running on version 6.7. We do this by clicking on the inventory name of the vCenter Server and viewing the Version Information from the Summary tab.

Enable DRS

Enable DRS

Since we disabled DRS during our preparing to upgrade post, it should be enabled once again. We begin this task by highlighting the cluster and then clicking on the Configure tab to view vSphere DRS settings. If you had set DRS to Manual versus disabling, now is the time to change that also.

Next click Edit to continue.

vSphere DRS 

In the Edit Cluster Settings window, click the slider switch to enable vSphere DRS then click OK to save. DRS is now enabled on the cluster.

PowerCLI with Set-Cluster

NOTE: You can also quickly perform these actions via PowerCLI with the ‘Set-Cluster’ cmdlet.

Enable DRS:

Set DRS automation level to Fully Automated:

Final Steps

After the vCenter Server Upgrade is completed, it is important to call out that power off operations only happen automatically for the vCenter Server, the VUM server must be powered off manually.

As a best practice, I suggest removing the Network Card from the old vCenter Server as well as renaming the VM to differentiate it within inventory and mitigate any accidental power on operations. Notice the new VCSA (VCSA67) virtual machine inventory name that was given. Note that renaming the VM does not change the FQDN of the VCSA, this is just the inventory name of the VM.

Lastly, be sure to power off the VUM server since it is no longer required to be running.

DRS automation level to Fully Automated

Rollback

Did your maintenance window close or maybe you encountered another issue during an Upgrade? Not to worry, rollback is quite simple. In this vSphere environment that we just upgraded we have no external PSCs, only the vCenter Server Appliance to worry about. If we did have an external PSC, we would first power off the newly deployed PSC, restore the PSC instance from backup, and if it was joined to an Active Directory domain, re-join it to the domain.

In our case without an external PSC we would, power off the newly deployed vCenter Server Appliance 6.7, bring the old vCenter Server Appliance 6.0 instance online (If already powered off, simply power it on. If not powered off, a restart is required), if it was joined to an Active Directory domain, it may need to be joined again (if your vCenter Server was Windows, be sure to have a local account on the server and do not rely on any cached credentials). Lastly we wait for all vCenter Server services to start and log in to the vSphere Web Client to verify the vSphere inventory.

Please review KB2146453 for more guidance on rollbacks.

Conclusion

Remember; Focus, Plan, Execute!

We have successfully executed our vCenter Server Upgrade! We started by reviewing our prerequisites & compatibility, gathering our data, and then upgrading our vCenter Server and vSphere Update Manager (VUM) from vSphere 6.0 Update3 to 6.7. Our VUM was migrated to the 6.7 VCSA also during this upgrade scenario. In the next vSphere Upgrade Series post, we will move to upgrading our vSphere 6.0 ESXi hosts to vSphere 6.7 by utilizing vSphere Update Manager to remediate.

Please do not hesitate to post questions in the comments section of this blog or reach out to me directly via Twitter @vCenterNerd.

 Article: https://blogs.vmware.com/vsphere/2018/07/vsphere-upgrade-series-part-2-upgrading-vcenter-server.html

 Date: 2018-10-29

Filter Tags