Installation guide
Achieving a Successful
VCMInstallation
1
Achieving a Successful VCMInstallation
Perform the requirements to successfully install VMware vCenter Configuration Manager (VCM), and
then install VCM in any of the supported single-tier, two-tier, or three-tier installation configurations.
Determine your specific hardware and software requirements for VMware vCenter Configuration
Manager (VCM). Perform the preparatory steps to install and configure your physical and virtual
machines for a successful VCM installation.
To determine your hardware and software requirements, begin by answering several questions.
n How many vCenter Server, UNIX, Linux, and Windows servers and workstations will you license?
n How often will you collect data?
n How much data will you collect?
n How long will you retain the collected data and change data?
n What additional VCM components will you use? For available VCM components, see the Download
VMware vCenter Configuration Manager Web site.
n Do you understand the VCM security requirements? See the VCM Security Guide.
To achieve a successful VCM installation, you must understand the hardware and software requirements
for VCM Collector machines and VCM managed machines, prepare your environment for VCM
installation, then install VCM.
Before you install VCM, use the following chapters to prepare for VCM installation. Perform the
prerequisite steps and procedures in the order presented, configure resources, configure your installation
environment, then install VCM.
After you install VCM, set the file growth for your VCMdatabase, then create a maintenance plan.
VCM Collector and Agent OS Platform Support
All Agent and Collector OS platform support is specific to versions and editions indicated in the supported
platforms table.
On the VCM Collector, OS vendor hardening recommendations are tested, and the resulting configuration
is supported. Custom lock downs and hardening beyond the OS vendor recommendations described in
the VCM Security Guide are not tested or supported.
Custom configurations might reduce or block the performance or functionality of VCM components.
Customizations include changes by non-OS vendors, third parties, endpoint security products, site policies,
custom lock downs, or restricted access to or from systems.
VMware, Inc.
11