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
FIPS for VCM Agent Proxies
The VCM Agent Proxy uses the OpenSSL FIPS v1.1.2, which is validated to the 918 certificate.
Agent Sizing Information
The disk space requirements are fairly constant for a Windows, UNIX, Linux, Mac OS X, or AD managed
machine that runs a VCM Agent. Each machine requires no more than 200MB to run an Agent. However,
the recommended memory to run the HP-UX Agent is 1GB.
The following information identifies the data files for default collections only. A 20MB overlap exists
between the Agent Proxy Agent and the Active Directory Agent when both Agents are installed on the
same machine.
Use the following information as a general guideline. Factors such as the types of data collected can affect
the sizing. VMware makes every effort to validate the numbers but cannot guarantee that the quoted
sizing information is accurate for all installations.
Windows Machines
For several components, the projected data file sizing information can vary. The data file size is the
estimated amount after an initial data collection using the default filter set.
Agent Type Installed
File Size
Data File Size Projected Data File Size
VCM Agent used as Managing Agent
This default Agent includes Extension
for Provisioning and Managing
Agent.
130–135MB 200MB–1GB The projected data file
sizing information can
vary depending on the size
of your vCenter Server
instances and the number
of hosts and guests.
Agent Proxy for Virtualization VCM Agent
+40MB
See VCM
Agent data file
sizes
The projected data file size
is determined the same as
the default Agent.
VCM Agent used for Provisioning
This default Agent includes Extension
for Provisioning and Managing
Agent.
130–135MB 10–20MB The projected data file
sizing information can
vary depending on your
collection filter set, and is
determined by collected
data types and actions. The
size can vary from 10–
20MB to more than 100MB.
The File System-File
Structure and System Logs
data types can cause large
data growth.
VCM Agent without Extension for
Provisioning
70–76MB 10–20MB The projected data file size
is determined the same as
the default Agent.
Table 15–10. Windows Agents and Component File Sizes
vCenter Configuration Manager Installation Guide
130
VMware, Inc.