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
Agent Type Installed
File Size
Data File Size Projected Data File Size
Active Directory Agent VCM Agent
+30MB
See VCM
Agent data file
sizes
The projected data file size
is determined the same as
the default Agent.
VCM Remote Client VCM Agent
+2MB
(installs or
upgrades
Agent)
See VCM
Agent data file
sizes
The projected data file size
is determined the same as
the default Agent.
Patching Agent VCM Agent
+2MB
See VCM
Agent data file
sizes
The projected data file size
is determined the same as
the default Agent.
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.
Hardware and Operating System Requirements for VCM Managed Machines
VMware, Inc.
131