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
When collecting data from ESX Servers, you must configure at least one VCM Agent Proxy machine. You
can configure the Collector as the Agent Proxy or configure standalone Agent Proxy machines. The
Collector communicates with the Agent Proxy and the Agent Proxy then directly communicates with the
ESX Servers using SSH and/or Web Services for necessary data collection actions. The data is processed by
the Agent Proxy and relayed to the Collector.
The minimum operating system and hardware requirements for each Agent Proxy machine are based on
the following criteria.
n
Number of machines from which you are collecting data
n
Type of data collected and filters used
n
Frequency of collections
n
Data retention
Minimum Operating System Requirements for Agent Proxy Machines
The Agent Proxy machine must be running Windows Server 2008 R2 or Windows Server 2003 SP2. For
more information to install and configure the Agent Proxy, see the VCM Administration Guide.
Minimum Hardware Requirements for Agent Proxy Machines
The Agent Proxy is installed on the Collector by default. Although the Agent Proxy is available on the
Collector, it requires special configuration to operate. You must configure an Agent Proxy server to collect
data from ESX Servers. If more than 50 ESX Servers are managed, additional Agent Proxy servers must be
configured to maintain the ratio of one agent proxy for each 50 ESX Servers.
The designated VCM for Agent Proxy servers should meet the following minimum requirements for
physical hardware or virtual machines. An Agent Proxy server meeting these requirements can manage
approximately 50 ESX Servers.
Physical Requirements for Virtualization Agent Proxy
n
Processor: Single Xeon or single-core 2GHz minimum
n
RAM: 4GB minimum
n
Disk Space: Each Agent Proxy requires an additional 93MB of disk space, above the 200MB required for
the standard Agent. You will also need:
n
4MB per ESX server for data model storage
n
150MB per ESX server for Agent master files
Virtual Requirements for Virtualization Agent Proxy
n
CPU: One virtual CPU, 2GHz, on a supported ESX host machine.
n
RAM: 4GB minimum reservation on a supported ESX host machine.
n
Storage: Each Agent Proxy requires an additional 93MB of disk space, above the 200MB required for
the standard Agent on a supported ESX platform. You will also need:
n
4MB per ESX server for data model storage
n
150MB per ESX server for Agent master files
Hardware and Operating System Requirements for VCM Managed Machines
VMware, Inc.
164