5.8
Table Of Contents
- VMware vRealize Configuration ManagerInstallation Guide
- Contents
- About This Book
- Preparing to Install VCM
- Common Prerequisites for All VCM Servers
- VCM Installation
- Post-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
- Linux and UNIX Patch Assessment and Deployment Requirements
- Support for VMware Cloud Infrastructure
- vRealize Operations Manager Integration Features
- FIPS Requirements
- Agent Sizing Information
- Index
VCM Installation Configurations
VCM supports single-tier, two-tier, and three-tier installation configurations. Before installing VCM, decide
on the appropriate configuration for your environment.
Split installations are useful when, for example, site policies limit a VCM user's access to a database server
or Web server. In such cases, you might need a split installation with a separate SQL Server machine, or
one with separate SQL Server and Web server machines.
Figure 1–1. VCM Installation Configurations
n Single Tier. All VCM components reside on a single Windows Server 2008 R2, 2012, or 2012 R2
machine. This configuration includes integrated security by default.
n Two-Tier Split Installation. The VCM SQL Server databases reside on a separate Windows Server
2008 R2, 2012, or 2012 R2 machine.
n Three-Tier Split Installation. The VCM SQL Server databases and the Web server are both installed on
separate Windows Server 2008 R2, 2012, or 2012 R2 machines. To install this configuration, see the VCM
Advanced Installation Guide.
With split installations, encrypted communication between the tiers is recommended for security.
Create VCM Domain Accounts
VCM requires that you create domain accounts with certain permissions. In the VCM Typical Installation,
you have the option to use the built-in Windows accounts in place of some of the accounts.
Before installing VCM, create or identify the domain accounts to use for each of the VCM functions. Keep
the credentials on hand for when the installation prompts for an account username and password.
n All of the accounts must be domain accounts and not local machine accounts.
n If you plan to select the built-in accounts option, you only need to prepare the following:
n The VCM Administrator account for logging in during installation
n If collecting Windows machine data over the DCOM protocol, the Default Network Authority
vRealize Configuration Manager Installation Guide
8
VMware, Inc.