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
RSAENH Validated Operating
Systems
Validated Versions (Links to
Security Policy)
FIPS
Certificate #
FIPS Version
Validated
Vista Ultimate Edition SP1 6.0.6001.22202 #1002 140–2
Windows Server 2008 6.0.6001.22202 #1010 140–2
Cryptographic DSS Enhanced Validated Modules
The Microsoft Cryptography API (CAPI) supports the following validated versions of DSS enhanced
modules, and the operating systems for which the testing is valid.
DSSENH Validated Operating
Systems
Validated Versions (Links to
Security Policy)
FIPS
Certificate #
FIPS Version
Validated
Windows 2000 5.0.2150.1 #76 140–1
Windows 2000 SP1 5.0.2150.1391 #103 140–1
Windows 2000 SP2 5.0.2195.2228 #103 140–1
Windows 2000 SP3 5.0.2195.3665 #103 140–1
Windows XP 5.1.2518.0 #240 140–1
Windows XP SP2 5.1.2600.2133 #240 140–1
Windows XP Professional SP3 5.1.2600.5507 #990 140–2
Vista Ultimate Edition 6.0.6000.16386 #894 140–2
Vista Ultimate Edition SP1 6.0.6001.18000 #1003 140–2
Windows Server 2008 6.0.6001.18000 #1009 140–2
Table 15–10. DSS Enhanced Validated Modules
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.
vCenter Configuration Manager Advanced Installation Guide
168
VMware, Inc.