5.7
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 Windows Server 2008 R2
- Install the .NET Framework
- Configuring the Database Components of the VCM Collector
- Install SQL Server on the VCM Collector
- Verify and Configure the SQL Server Properties
- Verify Matching SQL Server and Computer Names
- Verify the SQL Server Agent Service Account is a sysadmin
- Verify that the SQL Server Agent Service Starts Automatically
- Select the SQL Server Agent Service Account
- Establish SQL Server Administration Rights
- 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
- Verify that the SQL Server Agent Service Starts Automatically
- Select the SQL Server Agent Service Account
- Establish SQL Server Administration Rights
- Configure the Combined VCM Collector and Web Server
- Three-Tier Split Installation
- Configuring a Three-Tier Split Installation Environment
- Verify that the Installing User is an Administrator
- Install and Configure a Windows Server 2008 R2 Operating System
- Configure the VCM Database Server
- 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
- Verify that the SQL Server Agent Service Starts Automatically
- Select the SQL Server Agent Service Account
- Establish SQL Server Administration Rights
- Configure the Web Server
- Configure the VCM Collector
- 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.7
- Migrate a 64-bit Environment Running VCM 5.3 or Earlier toVCM 5.7
- 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
- Linux, UNIX, and Mac OS Agent Files
- Windows Custom Information Supports PowerShell 2.0
- Supported OS Provisioning Target Systems
- Software Provisioning Requirements
- Linux and UNIX 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
Agent Type Installed File
Size
Data File Size Projected Data File Size
Package Manager (installed
with VCM Agent Extension
for Provisioning), which
includes the database and
cratecache.
Package
Manager 4MB
Database
140KB
Cratecache
0MB
n/a Package Manager. The
application that installs and
removes packages. Size remains
fixed.
Database. Metadata about
packages. Increased size based
on number of installed packages.
For example, installing one
package increased the size from
140KB to 141KB.
Cratecache. Packages
downloaded to the machine
from Software Repository.
Increased size is based on the
number of installed packages
and the size of the packages, and
changes if packages are cleaned
from the cratecache after
package installation or removal.
Package Studio 5MB n/a Increased size of the files
depends on which *.prj and
*.crate files are saved locally.
Software Repository 5KB n/a Increased size of the files is based
on the number of packages
published to the repository from
Package Studio.
Linux and UNIX Machines
The projected data file sizing information for Linux and UNIX machines 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 most likely data types to cause large data growth are File System-File
Structure and System Logs.
The data file size is the estimated amount after an initial data collection with the default filter set.
Agent Type Installed File Size Data File Size
CMAgent.5.7.0.AIX.5 60–80MB 5–20MB
CMAgent.5.4.0.HP-UX.11.pa 120–125MB 45MB
CMAgent.5.7.0.HP-UX.11.pa 80MB 5–16MB
CMAgent.5.4.0.HP-UX.11.ia64 120–125MB 45MB
CMAgent.5.7.0.HP-UX.11.ia64 80MB 5–16MB
CMAgent.5.7.0.Linux 30–50MB 5–70MB
Table 15–12. Linux and UNIX Agents File Sizes
vCenter Configuration Manager Advanced Installation Guide
170
VMware, Inc.