6.0.2
Table Of Contents
- vSphere Upgrade
- Contents
- About vSphere Upgrade
- Updated Information
- Introduction to vSphere Upgrade
- Upgrade Requirements
- vCenter Server Upgrade Compatibility
- vCenter Server for Windows Requirements
- vCenter Server Appliance Requirements
- Required Ports for vCenter Server and Platform Services Controller
- vCenter Server Database Configuration Notes
- ESXi Requirements
- vSphere DNS Requirements
- vSphere Web Client Software Requirements
- Client Integration Plug-In Software Requirements
- vSphere Client Requirements
- Required Free Space for System Logging
- Before Upgrading vCenter Server
- Verify Basic Compatibility Before Upgrading vCenter Server
- Preparing vCenter Server Databases
- Prepare Oracle Database Before Upgrading to vCenter Server 6.0
- Prepare Microsoft SQL Server Database Before Upgrading to vCenter Server 6.0
- Use a Script to Create and Apply a Microsoft SQL Server Database Schema and Roles
- Prepare PostgreSQL Database Before Upgrading to vCenter Server 6.0
- Database Permission Requirements for vCenter Server
- Verify That vCenter Server Can Communicate with the Local Database
- Verify Network Prerequisites Before Upgrading
- Verify Load Balancer Before Upgrading vCenter Server
- Prepare ESXi Hosts for vCenter Server Upgrade
- Verify Preparations Are Complete for Upgrading vCenter Server
- Required Information for Upgrading vCenter Server for Windows
- Required Information for Upgrading the vCenter Server Appliance
- Upgrading and Updating vCenter Server for Windows
- About the vCenter Server 6.0 for Windows Upgrade Process
- Migration of Distributed vCenter Server for Windows Services During Upgrade to vCenter Server 6.0
- Download the vCenter Server for Windows Installer
- Upgrade vCenter Single Sign-On 5.1 for External Deployment
- Upgrade vCenter Single Sign-On 5.5 for External Deployment
- Upgrade vCenter Server 5.0
- Upgrade vCenter Server 5.1 for Windows
- Upgrade vCenter Server 5.5 for Windows
- Update the Java Components and vCenter Server tc Server with VIMPatch
- Upgrading and Patching the vCenter Server Appliance and Platform Services Controller Appliance
- After Upgrading vCenter Server
- Complete vCenter Server Postupgrade Component Configuration
- Reconfigure Migrated vCenter Server Services After Upgrade
- Install or Upgrade vSphere Authentication Proxy
- Upgrade the vSphere Client
- Configuring VMware vCenter Server - tc Server Settings in vCenter Server
- Setting the vCenter Server Administrator User
- Authenticating to the vCenter Server Environment
- Identity Sources for vCenter Server with vCenter Single Sign-On
- Restore ESXi Certificate and Key Files
- Repoint the Connections Between vCenter Server and Platform Services Controller
- Reconfigure a Standalone vCenter Server with an Embedded Platform Services Controller to a vCenter Server with an External Platform Services Controller
- Reconfigure Multiple Joined Instances of vCenter Server with an Embedded Platform Services Controller to vCenter Server with an External Platform Services Controller
- Verify that the Services of the Embedded Platform Services Controller Instances are Running
- Configure Replication Agreement Between All External Platform Services Controller Instances
- Reconfigure Each vCenter Server Instance and Repoint It from an Embedded to External Platform Services Controller Instance
- Upgrading Update Manager
- Before Upgrading Hosts
- Best Practices for ESXi Upgrades
- Upgrade Options for ESXi 6.0
- Upgrading Hosts That Have Third-Party Custom VIBs
- Using Manually Assigned IP Addresses for Upgrades Performed with vSphere Update Manager
- Media Options for Booting the ESXi Installer
- Download and Burn the ESXi Installer ISO Image to a CD or DVD
- Format a USB Flash Drive to Boot the ESXi Installation or Upgrade
- Create a USB Flash Drive to Store the ESXi Installation Script or Upgrade Script
- Create an Installer ISO Image with a Custom Installation or Upgrade Script
- PXE Booting the ESXi Installer
- Installing and Booting ESXi with Software FCoE
- Using Remote Management Applications
- Download the ESXi Installer
- Upgrading Hosts
- Using vSphere Update Manager to Perform Orchestrated Host Upgrades
- Configuring Host and Cluster Settings
- Perform an Orchestrated Upgrade of Hosts Using vSphere Update Manager
- Configure Host Maintenance Mode Settings
- Configure Cluster Settings
- Enable Remediation of PXE Booted ESXi Hosts
- Import Host Upgrade Images and Create Host Upgrade Baselines
- Create a Host Baseline Group
- Attach Baselines and Baseline Groups to Objects
- Manually Initiate a Scan of ESXi Hosts
- View Compliance Information for vSphere Objects
- Remediate Hosts Against an Upgrade Baseline
- Remediate Hosts Against Baseline Groups
- Installing or Upgrading Hosts by Using a Script
- Enter Boot Options to Start an Installation or Upgrade Script
- Boot Options
- About Installation and Upgrade Scripts
- Install or Upgrade ESXi from a CD or DVD by Using a Script
- Install or Upgrade ESXi from a USB Flash Drive by Using a Script
- Performing a Scripted Installation or Upgrade of ESXi by Using PXE to Boot the Installer
- Using vSphere Auto Deploy to Reprovision Hosts
- Upgrading Hosts by Using esxcli Commands
- VIBs, Image Profiles, and Software Depots
- Understanding Acceptance Levels for VIBS and Hosts
- Determine Whether an Update Requires the Host to Be in Maintenance Mode or to Be Rebooted
- Place a Host in Maintenance Mode
- Update a Host with Individual VIBs
- Upgrade or Update a Host with Image Profiles
- Update ESXi Hosts by Using Zip Files
- Remove VIBs from a Host
- Adding Third-Party Extensions to Hosts with an esxcli Command
- Perform a Dry Run of an esxcli Installation or Upgrade
- Display the Installed VIBs and Profiles That Will Be Active After the Next Host Reboot
- Display the Image Profile and Acceptance Level of the Host
- Upgrade Hosts Interactively
- Using vSphere Update Manager to Perform Orchestrated Host Upgrades
- After You Upgrade ESXi Hosts
- Upgrading Virtual Machines and VMware Tools
- Troubleshooting a vSphere Upgrade
- Collecting Logs for Troubleshooting a vCenter Server Installation or Upgrade
- Collect Logs to Troubleshoot ESXi Hosts
- Errors and Warnings Returned by the Installation and Upgrade Precheck Script
- Restore vCenter Server Services If Upgrade Fails
- VMware Component Manager Error During Startup After vCenter Server Appliance Upgrade
- Microsoft SQL Database Set to Unsupported Compatibility Mode Causes vCenter Server Installation or Upgrade to Fail
- Index
You can deploy a Platform Services Controller instance on the same virtual
machine (VM) or physical server as vCenter Server, which is vCenter Server
with an embedded Platform Services Controller instance. You can also
deploy a Platform Services Controller instance on a separate machine or
physical server, which is vCenter Server with an external
Platform Services Controller instance. See “vCenter Server Deployment
Models,” on page 16.
Enhanced Linked Mode
Starting with vSphere 6.0, the implementation of Linked Mode has changed.
You no longer need to join vCenter Server instances to Linked Mode groups.
You can access the replication functionality provided by Linked Mode in
vSphere 5.5 by registering multiple vCenter Server instances to the same
Platform Services Controller or joining Platform Services Controller instances
in the same vCenter Single Sign-On domain.
To enable high availability between the vCenter Server instances in a single
vCenter Single Sign-On domain, the vCenter Server instances must use the
same site name.
Unlike the original Linked Mode, Enhanced Linked Mode is available and
supported on vCenter Server on Windows and vCenter Server Appliance.
vCenter Server
Component Services
Deployment
Starting with vSphere 6.0, vCenter Server component services are deployed
in either the vCenter Server or Platform Services Controller group of
services. vSphere common services can no longer be upgraded individually
with vCenter Server 6.0.
The vCenter Server upgrade software migrates, upgrades, and congures
existing vCenter Server 5.1 or vCenter Server 5.5 services as needed,
migrating individually deployed vCenter Server 5.0 or vCenter Server 5.1
services to the appropriate service group during the upgrade process.
n
vCenter Single Sign-On credentials, certicates, and ports are now part
of the Platform Services Controller instance.
n
Tagging data and licensing is part of the Platform Services Controller
instance.
n
Other services are part of the vCenter Server instance. For details, see
“Migration of Distributed vCenter Server for Windows Services During
Upgrade to vCenter Server 6.0,” on page 75.
n
You can now choose the destination folder for the upgrade software to
use.
For more details about service deployment, see “About the vCenter Server 6.0
for Windows Upgrade Process,” on page 73.
Simple Upgrade
Process Replaced
Upgrading to vCenter Server 6.0 with an embedded
Platform Services Controller instance replaces the vCenter Server 5.1 or
vCenter Server 5.5 simple upgrade process. The upgrade process migrates
your vCenter Server 5.1 or vCenter Server 5.5 services to a vCenter Server 6.0
deployment with an embedded Platform Services Controller instance.
Custom Upgrade
Process Replaced
Upgrading to vCenter Server 6.0 with an external
Platform Services Controller instance replaces the vCenter Server 5.1 or 5.5
Custom or separate upgrade process. When you upgrade your custom or
distributed vCenter Server 5.1 or 5.5 instance, the upgrade process includes
any vCenter Server 5.1 or 5.5 services that are deployed separately from
vCenter Server. You do not need to upgrade them separately.
vSphere Upgrade
14 VMware, Inc.