5.7
Table Of Contents
- VMware vCenter Configuration Manager Installation 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
- 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
- Index
IMPORTANT Never use the service accounts for logging in to the VCM Console or for any other purpose.
Logging in to VCM using a service account can lead to unexpected or inconsistent behavior. Services that
use the same account as a logged in user might modify the logged in user's current role or the machine
group, or log the user out of the system.
Collector Service Account
The Collector service account is the account under which the VCM Collector, VCM Database, and VCM
Patch Management services run. At installation, VCM configures the Collector service account with dbo
rights and bulk insert rights in SQL Server for the VCM databases.
If the account password changes, update all three services so that they can continue to log in. If you
replace the account, configure the new account for login as a service, give it the same permissions, and add
it to the CSI_COMM_PROXY_SVC group. Also update all three services to use the new account.
VCM Remote Service Account
The VCM Remote service account is used by the VCM Remote client for anonymous access to the
VCMRemote virtual directory on the Web server.
If you change the account or its password, reconfigure anonymous access for the VCMRemote virtual
directory by using IIS Manager.
VCM Tomcat Service Account
The Tomcat service account serves as the VCM application programming interface for SQL login to the
VCM database server.
vSphere Client VCM Plug-in Service Account
The vSphere Client VCM Plug-in (VCVP) account provides vSphere access over HTTP to VCM managed
machines.
The VCM Advanced Installation option prompts for credentials for the VCVP account. Typical Installation
does not.
CSI_COMM_PROXY_USR Account
VCM creates a local account called CSI_COMM_PROXY_USR, under which the CM Communication Proxy
service runs. The CM Communication Proxy service is used for collection from ESX systems. Note that
ESX collections are for logs and kernel data only, and only on ESX, not ESXi.
If the account password changes, update the service so that it can continue to log in. If you replace the
account, configure the new account for login as a service, give it the same permissions, and add it to the
CSI_COMM_PROXY_SVC group. Also update the CM Communication Proxy service to use the new
account.
The CSI_COMM_PROXY_SVC group grants the rights needed for the service to access the data and
binaries that it needs.
IIS Application Pool Identity Account
CMAppPool and CMServices are IIS application pools used for VCM virtual directories and Web services.
They run under the built-in IIS ApplicationPoolIdentity account. No special configuration or password
management is needed for this built-in account.
Preparing to Install VCM
VMware, Inc.
11