5.6
Table Of Contents
- VMware vCenter Configuration Manager Installation Guide
- Contents
- About This Book
- Achieving a Successful VCM Installation
- Hardware Requirements for Collector Machines
- Software and Operating System Requirements for Collector Machines
- Preparing for Installation
- System Prerequisites to Install VCM
- Configure Resources to Install VCM on a Virtual Machine
- Secure Communications Certificates
- Single-Tier Server Installation
- Two-Tier Split Installation
- Three-Tier Split Installation
- Configuring a Three-Tier Split Installation Environment
- Installation Prerequisites for All Servers
- Configuring the VCM Database Server
- Configuring the Web Server
- Verify the Server Role Services on the Web Server
- Verify the IIS Server-Side Includes Role Service
- Verify the ISAPI Extensions
- Install the .NET Framework
- Verify the Authentication Settings
- Install SQL Server on the Web Server
- Install SQL Server 2008 Utilities
- Place the Web Server in the Internet Explorer Trusted Zone
- Configuring SSRS on the Web Server
- Configuring the VCM Collector
- Configuring Additional Components for a Three-Tier Environment
- Installing VCM
- Configuring SQL Server for VCM
- Upgrading or Migrating VCM
- Upgrading VCM and Components
- Upgrading Virtual Environments Collections
- Migrating VCM
- Prerequisites to Migrate VCM
- Migrate Only Your Database
- Replace Your Existing 32-Bit Environment with a Supported 64-bit Environment
- Migrate a 32-bit Environment Running VCM 5.3 or Earlier to VCM 5.6
- Migrate a 64-bit Environment Running VCM 5.3 or Earlier to VCM 5.6
- Migrate a Split Installation of VCM 5.3 or Earlier to a Single-Tier, Two-Tier...
- How to Recover Your Collector Machine if the Migration is not Successful
- Maintaining VCM After Installation
- Hardware and Operating System Requirements for VCM Managed Machines
- VCM Agent Support on Non-English Windows Platforms
- VCM Managed Machine Requirements
- Windows Custom Information Supports PowerShell 2.0
- Supported OS Provisioning Target Systems
- Software Provisioning Requirements
- UNIX and Linux Patch Assessment and Deployment Requirements
- Support for VMware Cloud Infrastructure
- vCenter Operations Manager Integration Features
- FIPS Requirements
- Agent Sizing Information
- Hardware and Software Requirements for the Operating System Provisioning Server
- Installing, Configuring, and Upgrading the OS Provisioning Server and Components
- Index
The Time of Day settings are based on your user time zone. All VCM jobs run based on the VCM
database time zone. Account for the time and date differences between your VCM user time and your
VCM database time. For example, if your VCM database server is in the Eastern time zone, and your
VCM user is in the Pacific time zone, to run your job at midnight, enter 9 PM.
15. Click Next and Finish.
What to do next
Upgrade your UNIX Agents using a remote package. See "Upgrade UNIX Agents Using a Remote
Package" on page 96.
Upgrade UNIX Agents Using a Remote Package
Use VCM remote commands and a remote Agent package to upgrade the VCM UNIX Agent on the UNIX
platforms in your environment.
The UNIX Agents use Transport Layer Security (TLS) and the Enterprise Certificate is embedded in the
Agent package. If multiple Collectors must communicate with a single Agent, all of the Collectors must
share an Enterprise Certificate. If the Collectors have different Enterprise Certificates, the Enterprise
Certificate from each Collector must be uploaded to the Agent. See the VCM Security Guide.
The UNIX remote commands use existing configuration settings to upgrade the UNIXAgents using a
remote Agent package. VCM sends the Agent package to the target machine.
The remote package sends the UNIXAgent upgrade package with the remote command to execute on the
UNIX machine. The following remote upgrade packages are designed specifically for the various
operating systems where the Agents can be upgraded.
n
AIX 5 Agent Upgrade
n
HP-UX (Itanium) Agent Upgrade
n
HP-UX (PA-RISC) Agent Upgrade
n
Mac OSX Agent Upgrade
n
Red Hat Enterprise 3.0, 4.0, 5.0, 5.1, 5.2, and SUSE Enterprise 9 and above Agent Upgrade
n
Solaris (SPARC) Agent Upgrade
n
Solaris (x86) Agent Upgrade
Older machines use the following packages.
n
For AIX 4.3.3 Agent Upgrade, use only CMAgent.5.1.0.AIX.4.
n
For Red Hat Enterprise 2.1 Agent Upgrade, use only CMAgent.5.1.0.Linux.2.1.
The following procedure upgrades the UNIX Agents using one of the remote upgrade packages.
Prerequisites
n
Install the VCM UNIXAgent on the managed machines to upgrade.
vCenter Configuration Manager Installation Guide
96
VMware, Inc.