Upgrading an MSM VM Follow this section to upgrade an MSM VM. Note: All the Core VMs must be upgraded before you start the upgrade process for the MSM VM . Child TopicsConfiguring the VMs to use the NTP serverConfigure each MSM VM and Core VM to use an NTP server. Taking a snapshot of the MSM VMBefore upgrading, create a snapshot of the MSM VM. If you encounter problems during the upgrade process, you can revert the virtual machine using the snapshot. Starting an MSM VM upgradeExecute VxBlock-Central_msm_upgrade-<buildnumber>.vce to upgrade. Updating the MSM credential manager service If the root or VxBlock Central user password has been changed on the Core VM, you must update the MSM credential manager service with the new password. Verifying the MSM VM upgrade After completing the upgrade process, use the VxBlock Central dashboard to verify that the version number of the MSM corresponds to the version that you installed. Upload compliance content Use the dashboard to upload and install new compliance content. Reentering the custom display names In a single MSM deployment, custom display names are not retained after an upgrade, you need to reenter the names you defined before you began the upgrade process. Custom display names are retained in a clustered environment. Removing a VM snapshot As a best practice, remove VM snapshots after you successfully upgrade the VMs. If a VM is part of a cluster, do not remove the VM snapshot until all VMs are successfully upgraded. Refer to the VMware documentation for more information. VMware knowledge base article ID 1025279 provides information about best practices for snapshots in a VMware environment.