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
Hardware and Software Requirements for
the Operating System Provisioning Server
16
Hardware and Software Requirements for the
Operating System Provisioning Server
VCM operating system provisioning supports one instance of VCM with one or more instances of
Operating System Provisioning Server (OS Provisioning Server).
Configure the server to meet the requirements.
Supported OS Provisioning Server Platform
The OS Provisioning Server can be installed on Red Hat Enterprise Linux version 5.2, 5.4, or 5.5, 32-bit or
64-bit.
OS Provisioning Server System Requirements
The machine on which you are installing the OS Provisioning Server must meet the following minimum
requirements:
n
Memory: For physical machines, 4GB RAM is the minimum requirement. 8GB RAMis recommended.
For virtual machines, assign 1GB to 4GB to the virtual machine.
n
CPU: For physical and virtual machines, two or more processors are recommended. The multitasking
required to do OS provisioning is better served by a multiprocessor server.
n
Disk Space: For physical and virtual machines, 100GB minimum disk space to store the OS provisioning
application and the repository database. Each imported ISO distribution requires additional space. Use
the following sizing information to determine the additional disk space required for each distribution.
Base Family Disk Space (GB)
Windows 3
Red Hat Enterprise Linux (RHEL) 5.x 4
Red Hat Enterprise Linux (RHEL) 6.0 i386 14
Red Hat Enterprise Linux (RHEL) 6.0 x86_64 20
SUSE Linux Enterprise Server (SLES) 3
n
Networking: For optimal functionality, configure two network interfaces. One interface on the public
network, and the second interface on the private provisioning network. Also, as a requirement of the
system license policy, the host name of the OS Provisioning Server must resolve to an IP address when
pinged. The address can be assigned using DNS or specified in the /etc/hosts file as appropriate for your
local network requirements.
VMware, Inc.
133