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
Product Description Anticipated Number of Managed
Machines in the Next 12-24
Months
VCM Windows Servers
ESXi Servers
Guest Virtual Machines
Linux or UNIX
Mac
Windows Workstations
VCM
for AD
Divide total number of AD objects by 100 to determine the
approximate "machine count" for your AD environment.
Total Managed Machines: _______
Table 2–1. Sizing Worksheet
In the following example, an enterprise environment contains machines and objects that represent 1377
managed machines, which places it in the 1000–2000 managed machines category.
Product Description
Anticipated Number of Managed
Machines in the Next 12-24 Months
VCM Windows Servers 92
vSphere/ESX/ESXi Servers 5
Virtual Machines (VM) 50
Linux or UNIX 100
Mac 100
Windows Workstations 920
VCM
for
AD
Divide total number of AD objects by 100 to determine
the approximate "machine count" for your AD
environment.
10,000 AD Objects/100 = 100 managed
machines to accommodate VCM for
AD
Total Managed Machines: 1377
Table 2–2.
Example of Sizing Worksheet with Sample Data
Identify Your Specific Hardware Requirements
Size your VCM Collector and database based on the requirements for managed vCenter Server instances
and the number of machines managed by VCM.
Database Sizing for Managed vCenter Server Instances
Use the following requirements to size your SQLServer database depending on the number of hosts and
guests per vCenter Server managed by VCM. These requirements are in addition to the base VCM
storage requirements, and are based on an estimated 10% data change per day times 15 days of data
retention.
vCenter Configuration Manager Installation Guide
12
VMware, Inc.