5.6
Table Of Contents
- VMware vCenter Configuration Manager Advanced 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
- Configure a Single-Tier Installation Environment
- Verify that the Installing User is an Administrator
- Install and Configure a Windows Server 2008 R2 Operating System
- Install the .NET Framework
- Configuring the Database Components of the VCM Collector
- Configure the Web Components
- Configure SSRS on the VCM Collector
- Configure the VCM Collector Components
- Two-Tier Split Installation
- Configuring a Two-Tier Split Installation Environment
- Verify that the Installing User is an Administrator
- Install and Configure a Windows Server 2008 R2 Operating System
- Configuring the VCM Database Server
- Disable the Firewall or Add an Exception for SQL Server Port 1433
- Install SQL Server on the Database Server
- Verify and Configure the SQL Server Properties
- Verify Matching SQL Server and Computer Names
- Verify the SQL Server Agent Service Account is a sysadmin
- Select the SQL Server Agent Service Account
- Establish SQL Server Administration Rights
- Configure the Combined VCM Collector and Web Server
- Three-Tier Split Installation
- 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
new Remote virtual directory as used in your previous installation.
If you change the Remote virtual directory name, you must update all corresponding Agents to use
the new virtual directory.
10. Select your existing databases to migrate them to VCM 5.6.
If Installation Manager requests that you create a new database, select the previous wizard page and
verify that your existing database, which you attached, is selected.
11. Do not select SSL unless your machine is already configured for SSL.
12. After the upgrade is finished, copy the content of WebConsole\L1033\Files from your existing 64-
bit Collector to your new 64-bit Collector.
Any existing remote commands, discovery files, and imported template files in this directory are
available on the 64-bit Collector.
13. On your 64-bit Collector, run your script to import your VCM scheduled jobs.
14. On your 64-bit Collector, run your script to import your VCM membership logins.
15. Re-import any custom SQL Server Reporting Service Report Definition Language (RDL) files.
What to do next
n
Configure the SQL Server settings to tune your VCM database in SQL Server Management Studio,
including the VCM database file growth and database recovery. See "Maintaining VCM After
Installation" on page 150.
n
Log in to VCM.
Migrate a Split Installation of VCM 5.3 or Earlier to a Single-Tier, Two-Tier, or
Three-Tier Server Installation
Migrate an existing split installation to a single-tier, two-tier, or three-tier installation configuration for
VCM 5.6.
In a previous split installation, the VCM databases were installed on separate Windows machines. The
Collector machine hosted the VCM_Coll database only, and the database server machine hosted the VCM,
VCM_UNIX, ReportServer, master, and msdb databases.
In VCM 5.6, you can migrate a previous split installation to any of the following configurations.
n
"Single-Tier Server Installation" on page 34
In a single-tier server installation, the VCM database server, Web server, and the VCM Collector
components reside on a single Windows Server 2008 R2 machine, which is referred to as the VCM
Collector. The installation installs all of the core VCM components, including the databases, console,
and services. This configuration enables integrated security by default.
n
"Two-Tier Split Installation" on page 60
In a two-tier split installation, the VCM database resides on the Windows Server 2008 R2 database
server machine, and the VCM Collector and Web components reside on the second Windows Server
2008 R2 machine.
n
"Three-Tier Split Installation" on page 86
In a three-tier split installation, the VCM databases, the Web applications, and the VCM Collector
components reside on three different Windows Server 2008 R2 machines.
vCenter Configuration Manager Advanced Installation Guide
145
VMware, Inc.