5.6
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 a Windows Server 2008 R2 Operating System
- Install the .NET Framework
- Configuring the Database Components of the VCM Collector
- 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
- Select the SQL Server Agent Service Account
- Establish SQL Server Administration Rights
- Configure the Combined VCM Collector and Web Server
- Three-Tier Split Installation
- 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
CAUTION Do not use Network Service for the SQL Server service account. If you use the Network
Service account for your SQL Server instance, VCM installation could fail. Foundation Checker does
not check for this account during VCM installation.
The LocalSystem account, NT AUTHORITY\System, has unrestricted access to all local system resources.
This account is a member of the Windows Administrators group on the local machine.
If the NT AUTHORITY\System account does not have access to the VCM installation binary files, the
installation results in an access denied error. This situation is not common, but could occur if the
installation files are copied to or extracted in a user's home directory. In this case, you must grant access to
the NT AUTHORITY\System account from the installation source directory, then run the installation
again. A user or user’s group has access when they have full control of the file or folder.
Specify the Collector Services Account
Specify the Collector Service account to use during VCM installation. The account can be a system
administrator account and must exist in the Local Administrators group on the Collector machine. The
account must not be the Local System account.
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.
If the password for the account changes, you must change the password in the Services Management
console and the Component Services DCOM Config console.
Procedure
1. In Server Manager, verify that the Groups menu is open.
If not, expand Configuration, expand Local Users and Groups, and click Groups.
2. Double-click Administrators and verify that the account used for Collector Services is listed as a
member of the Administrators group.
If the user or administrator’s group is not listed, to ensure that the user has Windows administrator
rights issued by the network administrator, add the user or group to the list.
What to do next
Keep Server Manager open to specify the VCM Application Services account in Server Manager. See
"Verify the VMware Application Services Account" on page 23.
Verify the VMware Application Services Account
Verify that the VMware Application Services Account is a domain user.
IMPORTANT Never use this account as a VCM login 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.
vCenter Configuration Manager Advanced Installation Guide
23
VMware, Inc.