VMware vRealize Configuration Manager - 5.8 Installation Manual

VMware vRealize Configuration Manager

Advanced Installation Guide

vRealize Configuration Manager 5.8

This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see

http://www.vmware.com/support/pubs.

EN-001816-00

vRealize Configuration Manager Advanced Installation Guide

You can find the most up-to-date technical documentation on the VMware Web site at:

http://www.vmware.com/support/

The VMware Web site also provides the latest product updates.

If you have comments about this documentation, submit your feedback to:

docfeedback@vmware.com

http://www.vmware.com/go/patents.

VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.

VMware, Inc.

3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com

VMware, Inc.

About This Book 7

Achieving a Successful VCMInstallation 9

VCM Collector and Agent OS Platform Support 9

Hardware Requirements for Collector Machines 11

Determine the Size of Your Environment 11 Identify Your Specific Hardware Requirements 12

Database Sizing for Managed vCenter Server Instances 12 Hardware and Disk Requirements By Number of Managed Machines 13

Software and Operating System Requirements for Collector Machines 17

Sizing Impact on Software Edition Requirements 17 Software Installation and Configuration Overview 18

Preparing for Installation 19

VCM Installation Configurations 19

System Prerequisites to Install VCM 21

Establish Local Administration Rights 22 Verify Browser Compatibility 22 Verify the Default Network Authority Account 22 Specify the Collector Services Account 23 Verify the VCM Agent is Not Installed 24 Verify the SQLXML Version 25

Configure Resources to Install VCM on a Virtual Machine 27

Configure the Disk to Install VCM on a Virtual Machine 28 Configure the CPU to Install VCM on a Virtual Machine 28 Configure the Memory to Install VCM on a Virtual Machine 29

Secure Communications Certificates 31

Authenticating the Server to the Client 31

Enterprise and Collector Certificates 32 Delivering Initial Certificates to Agents 32

Single-Tier Server Installation 35

Configure a Single-Tier Installation Environment 36 Verify that the Installing User is an Administrator 37 Install and Configure Windows Server Operating System 38

Disable the Remote Desktop Session Host 39 Enable DCOM 40

Install the .NET Framework 40

Verify the ASP.NET Client System Web Version 41 Verify the ASPRole Service 41 Verify the ASP.NETRole Service 41

Configuring the Database Components of the VCM Collector 41

Install SQL Server on the VCMCollector 42

VMware, Inc.

vRealize Configuration Manager Advanced Installation Guide

Verify and Configure the SQL Server Properties 46 Verify Matching SQL Server and Computer Names 47 Verify the SQLServer Agent Service Account is a sysadmin 47 Verify that the SQLServer Agent Service Starts Automatically 48 Select the SQLServer Agent Service Account 48 Establish SQL Server Administration Rights 49

Configure the Web Components 49

Configuring IIS 51 Verify the ISAPI Extensions 53

Configure SSRS on the VCMCollector 54

Back Up Your SSRS Key 54 Disable IE Protected Mode for SSRS 54 Configure SSRS 54 Configure Basic Authentication on the Report Server 56 Configure Kerberos Authentication 57

Configure the VCM Collector Components 59

Two-Tier Split Installation 61

Configuring a Two-Tier Split Installation Environment 62 Verify that the Installing User is an Administrator 63 Install and Configure Windows Server Operating System 63

Disable the Remote Desktop Session Host 64 Enable DCOM 65

Configuring the VCM Database Server 65

Disable the Firewall or Add an Exception for SQL Server Port 1433 66 Install SQL Server on the Database Server 66 Verify and Configure the SQL Server Properties 70 Verify Matching SQL Server and Computer Names 71 Verify the SQLServer Agent Service Account is a sysadmin 72 Verify that the SQLServer Agent Service Starts Automatically 72 Select the SQLServer Agent Service Account 72 Establish SQL Server Administration Rights 73

Configure the Combined VCM Collector and Web Server 74

Install the .NET Framework 74 Configure the Web Components 75 Installing and Configuring SSRS on the Combined VCM Collector and Web Server 79 Configure Kerberos Authentication 86 Configure the VCM Collector Components 88

Three-Tier Split Installation 91

Configuring a Three-Tier Split Installation Environment 92 Verify that the Installing User is an Administrator 92 Install and Configure Windows Server Operating System 93

Disable the Remote Desktop Session Host 94 Enable DCOM 95

Configure the VCM Database Server 95

Install SQL Server on the Database Server 96 Verify and Configure the SQL Server Properties 100 Verify Matching SQL Server and Computer Names 100 Verify the SQLServer Agent Service Account is a sysadmin 101 Verify that the SQLServer Agent Service Starts Automatically 101 Select the SQLServer Agent Service Account 102 Establish SQL Server Administration Rights 103

Configure the Web Server 103

Configuring IIS 105 Verify the ISAPI Extensions 107 Place the Web Server in the Internet Explorer Trusted Zone 107

VMware, Inc.

Contents

Access to Patch Download Folder for Windows Patch Deployment 107 Installing and Configuring SSRS on the Web Server 109 Configure Kerberos Authentication 116 Modify the SQLCMD Path Variable 119

Configure the VCM Collector 119

Install the .NET Framework 120 Using VCM Remote 121

Installing VCM 125

Single-Tier Configuration 125 Two-Tier Split Configuration 125 Three-Tier Split Configuration 125 DCOM and Port Requirements for VCM 126 Install VCM using Advanced Installation 126 File System Permissions 127 Change Permissions On Machine Certificate Keys 128 Verify VCM Remote Virtual Directory Permissions 129

Configuring SQL Server for VCM 131

About VCM Databases 131 SQL Server Database Settings 131 SQL Server Processor Settings 132

Configure SQL Server Processor Settings 132

SQL Server I/O Configuration 133

Using the RAID Levels with SQLServer 134 Disk Interface and Disk Drive Performance 134 Use SQLIO to Determine I/O Channel Throughput 135

Upgrading or Migrating VCM 137

Upgrading VCM and Components 137

Upgrade VCM 138 Upgrade a Two-Tier Split VCM Configuration 139 Upgrade a Three-Tier Split VCM Configuration 140 Upgrade Existing Windows Agents 141 Upgrade Existing VCM Remote Clients 142 Red Hat Server and Workstation Licensing 143 Upgrade Existing UNIX Agents 143

Upgrading Virtual Environments Collections 146

Upgrade the Managing Agent 146 Upgrading the vSphere Client VCM Plug-In 146 Upgrading Agent Proxy Machines 147

Migrating VCM 149

Prerequisites to Migrate VCM 150 Migrate Only Your Database 152 Replace Your Existing 32-Bit Environment with a Supported 64-bit Environment 153 Migrate a 32-bit Environment Running VCM 5.3 or Earlier to VCM 5.8 154 Migrate a 64-bit Environment Running VCM 5.3 or Earlier toVCM 5.8 155 Migrate a Split Installation of VCM 5.3 or Earlier to a Single-Tier, Two-Tier, or Three-Tier Server Installation 157 How to Recover Your Collector Machine if the Migration is not Successful 159

Maintaining VCM After Installation 161

Customize VCM and Component-Specific Settings 161 Configure Database File Growth 163 Database Recovery Models 163 Configure Database Recovery Settings 164 Create a Maintenance Plan for SQL Server 164

VMware, Inc.

vRealize Configuration Manager Advanced Installation Guide

Incorporate the VCM Database into Your Backup and Disaster Recovery Plans 166

Hardware and Operating System Requirements for VCM Managed Machines 167

VCM Agent Support on Non-English Windows Platforms 167 VCM Managed Machine Requirements 167 Linux, UNIX, and Mac OS Agent Files 170 Windows Custom Information Supports PowerShell 2.0 171 Linux and UNIX Patch Assessment and Deployment Requirements 171 Support for VMware Cloud Infrastructure 172

Cloud and Virtualization Infrastructure Platforms 172 Managing Agent Requirements 172

Agent Proxy Requirements for VMware ESX and ESXi 172 vRealize Operations Manager Integration Features 173 FIPS Requirements 173

FIPS for Windows 174

FIPS for VCM Agent Proxies 175 Agent Sizing Information 175

Windows Machines 176

Linux and UNIX Machines 177

Mac OS X Machines 178

Index 179

VMware, Inc.

About This Book

The VCM Advanced Installation Guide describes the steps to install vRealize Configuration Manager (VCM) in all supported installation configurations. This document includes detailed information that does not appear in the VCM Installation Guide.

This document contains the following information:

n Hardware requirements for VCM Collector machines

n Software and operating system requirements for VCM Collector machines

n System prerequisites to install VCM

n Secure Communication Certificates

n Single-tier, two-tier, and three-tier installation configurations

n Configuring SQLServer for VCM

n Hardware requirements for VCM managed machines

Read this document and follow the procedures to successfully install VCM on existing physical or virtual machines in your environment. The example procedures in this guide are based on Microsoft SQL Server 2008 R2, 2012, and 2014 versions.

The VCM Advanced Installation Guide applies to VCM 5.8, Foundation Checker 5.8, and Service Desk Connector 1.3.0.

Intended Audience

This information is written for experienced Linux, UNIX, Mac OSX, and Windows system administrators who are familiar with managing network users and resources and with performing system maintenance.

To use this information effectively, you must have a basic understanding of how to configure network resources, install software, and administer operating systems. You also need to fully understand your network topology and resource naming conventions.

Document Feedback

VMware welcomes your suggestions for improving our documentation. If you have comments, send your feedback to docfeedback@vmware.com.

VMware VCM Documentation

The VCM documentation consists of the VCM Installation Guide, VCM Administration Guide, VCM Advanced InstallationGuide, VCM online help, and other associated documentation.

VMware, Inc.

vRealize Configuration Manager Advanced Installation Guide

Technical Support and Education Resources

The following technical support resources are available to you. To access the current version of this book and other books, go to http://www.vmware.com/support/pubs.

Online and Telephone Support

To use online support to submit technical support requests, view your product and contract information, and register your products, go to

http://www.vmware.com/support.

Customers with appropriate support contracts should use telephone support for priority 1 issues. Go to

http://www.vmware.com/support/phone_support.html.

Support Offerings To find out how VMware support offerings can help meet your business

needs, go to http://www.vmware.com/support/services.

VMware Professional Services

VMware Education Services courses offer extensive hands-on labs, case study examples, and course materials designed to be used as on-the-job reference tools. Courses are available onsite, in the classroom, and live online. For onsite pilot programs and implementation best practices, VMware Consulting

Services provides offerings to help you assess, plan, build, and manage your virtual environment. To access information about education classes, certification programs, and consulting services, go to

http://www.vmware.com/services.

VMware, Inc.

Achieving a Successful VCMInstallation

Perform the requirements to successfully install VMware vRealize Configuration Manager (VCM), and then install VCM in any of the supported single-tier, two-tier, or three-tier installation configurations.

Determine your specific hardware and software requirements for VMware vRealize Configuration Manager (VCM). Perform the preparatory steps to install and configure your physical and virtual machines for a successful VCM installation.

To determine your hardware and software requirements, begin by answering several questions.

n How many vCenter Server, UNIX, Linux, and Windows servers and workstations will you license?

n How often will you collect data?

n How much data will you collect?

n How long will you retain the collected data and change data?

n What additional VCM components will you use? For available VCM components, see the Download

VMware vRealize Configuration Manager Web site.

n Do you understand the VCM security requirements? See the VCM Security Guide.

To achieve a successful VCM installation, you must understand the hardware and software requirements for VCM Collector machines and VCM managed machines, prepare your environment for VCM installation, then install VCM.

Before you install VCM, use the following chapters to prepare for VCM installation. Perform the prerequisite steps and procedures in the order presented, configure resources, configure your installation environment, then install VCM.

After you install VCM, set the file growth for your VCMdatabase, then create a maintenance plan.

VCM Collector and Agent OS Platform Support

All Agent and Collector OS platform support is specific to versions and editions indicated in the supported platforms table.

On the VCM Collector, OS vendor hardening recommendations are tested, and the resulting configuration is supported. Custom lock downs and hardening beyond the OS vendor recommendations described in the VCM Security Guide are not tested or supported.

Custom configurations might reduce or block the performance or functionality of VCM components. Customizations include changes by non-OS vendors, third parties, endpoint security products, site policies, custom lock downs, or restricted access to or from systems.

VMware, Inc.

vRealize Configuration Manager Advanced Installation Guide

Troubleshooting and support of VCM components in custom reconfigured or locked down environments is not included under the standard product maintenance agreement, but support for such environments is available through an additional Professional Services engagement.

For details about VCM Collector machines, see "Hardware Requirements for Collector Machines" on

page11 and "Software and Operating System Requirements for Collector Machines" on page17.

For details about VCM managed machines, see "Hardware and Operating System Requirements for VCM

Managed Machines" on page167.

VMware, Inc.

Hardware Requirements for Collector Machines

Your VCM Collector hardware requirements depend on the number of physical and virtual managed machines in your environment.

Disk space requirements vary based on the following factors.

n Number of machines from which you collect data

n Type of data collected and filters used

n Frequency of collections

n Data retention

Determine the Size of Your Environment

In VCM, the term “managed machines” refers to the servers and workstations that VCM manages, and from which VCM collects data. If you use VCM for Microsoft Active Directory (AD), this total should also include AD objects that you plan to have in your environment in the next 12 to 24 months.

VCM hardware requirements are recommended based on whether your environment contains 1–1000, 1001–2000, 2001–5000, or more managed machines. To determine the number of managed machines on which to base your collector size, consider the number of vCenter Server instances, Windows servers and workstations, Linux or UNIX machines, and virtual machines that you are licensing. Identify any other VCM components that you are licensing.

VMware, Inc.

To determine your total number of managed machines, enter data for your enterprise in the sizing worksheet. In the following example, an enterprise environment contains machines and objects that represent 1377 managed machines.

vRealize Configuration Manager Advanced Installation Guide

Table 2–1. Sample Sizing Worksheet

Product Description Anticipated Number of Managed

VCM Windows Servers 92

vSphere/ESX/ESXi Servers 5

Virtual Machines 50

Linux or UNIX 100

Mac 100

Windows Workstations 920

Machin es in the Next 12–24 Month s

VCM for Active Directory

Divide total number of AD objects by 100 to determine the approximate "machine count" for your AD environment.

Total Managed Machines: 1377

10,000 AD Objects/100 = 100 managed machines to accommodate VCM for AD

Use the blank worksheet to calculate and record the managed machines in your environment.

Table 2–2. Blank Sizing Worksheet

Product Description Anticipated Number of Managed

Machin es in the Next 12–24 Month s

VCM Windows Servers

vSphere/ESX/ESXi Servers

Virtual Machines

Linux or UNIX

Mac

Windows Workstations

VCM for Active Directory

Divide total number of AD objects by 100 to determine the approximate "machine count" for your AD environment.

Total Managed Machines:

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 SQLServer database depending on the number of hosts and guests per vCenter Server managed by VCM. Guest collections include only the virtual machine data that vCenter provides and do not include any in-guest data. In-guest collections are separate from vCenter collections.

VMware, Inc.

Hardware Requirements for C ollector Machines

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.

Table 2–3. VCMDatabase Sizing per vCenter Server Instance

Host s Guests Est. Daily Ch ang e Data Reten tio n in Days Data Size

25 250 10% 15 3GB

50 500 10% 15 6GB

250 2500 10% 15 30GB

The best practice in production environments is to have the Managing Agent process requests for a single vCenter Server. Dedicate one Managing Agent machine for each vCenter Server. In a single vCenter Server instance environment, the VCM Collector can be the Managing Agent.

A single Managing Agent can manage multiple vCenter Server instances depending on your collection schedules and when potential job latency is not an issue, such as when a single Managing Agent must process multiple requests serially. A single Managing Agent can manage multiple vCenter Server instances as long as only one vCenter Server is collected at a time.

When job latency is not a problem, and depending on your collection schedules, you might dedicate a single Managing Agent for every five vCenter Server instances or 100 hosts. You could dedicate one Managing Agent to a vCenter Server that manages 100 hosts, or a collection of four vCenter Server instances that each manage 10 hosts could share a Managing Agent.

Hardware and Disk Requirements By Number of Managed Machines

Use the Minimum Hardware Requirements and Minimum Disk Configuration Requirements tables to determine your hardware and disk configuration requirements for a single-tier server installation.

Use the total number of managed machines from the Sizing Worksheet to locate your environment size (1–1000, 1000–2000, 2000–5000, or more). If you have more than 5000 machines in your environment, contact VMware Technical Support to help you determine your hardware requirements.

If you run SQLServer on a virtual machine, see Microsoft SQL Server on VMware Best Practices Guide at

http://www.vmware.com/files/pdf/sql_server_best_practices_guide.pdf. If you run SQL Server in a Hyper-

V environment, see Best Practices and Performance Considerations for Running SQL Server 2008 in a Hyper-V Environment on the Microsoft Web site.

The requirements listed in the following tables are based on the following assumptions.

n Daily VCM collections using the default filter set with additional Microsoft AD security descriptors

collected using VCM for AD.

n 15 days retention of change data.

n Simple recovery mode only.

n Daily VCM Patching collections.

n No applications other than VCM are running on your server.

VCM for AD collections cause the TempDB database to grow significantly. If you have a fully populated Microsoft Active Directory and plan to perform frequent AD collections, increase your hardware requirements.

VMware, Inc.

Longer data retention, additional WMI, registry filters, and custom information collections also add to the requirements.

vRealize Configuration Manager Advanced Installation Guide

Table 2–4. Minimum Hardware Requirements to Support 1–1000 Managed Machines

Single Tier 2-Tier

Datab ase

2-Tier Web/Co llector

3-Tier Datab ase

3-Tier Web

3-Tier Collector

Processor Dual Xeon or

single Dual Core 2GHz

Dual Xeon or single Dual Core 2GHz

Single processor 2GHz

RAM 8GB 8GB 4GB 8GB 4GB 4GB

Separate

2 2 1 2 1 1

Disk Channels

Table 2–5. Minimum Hardware Requirements to Support 1001–2000 Managed Machines

Single Tier 2-Tier

Processor Quad Xeon

or two Dual Core 2GHz

Datab ase

Quad Xeon or two Dual Core 2GHz

2-Tier Web/Co llector

Dual Xeon or single Dual Core 2GHz

3-Tier Datab ase

Quad Xeon or two Dual Core 2GHz

3-Tier Web

Single processor 2GHz

3-Tier Collector

Dual Xeon or single Dual Core 2GHz

RAM 12GB 12GB 4GB 12GB 4GB 4GB

Separate

3 3 2 3 1 2

Disk Channels

Table 2–6. Minimum Hardware Requirements to Support 2001–5000 Managed Machines

Single Tier 2-Tier

Processor Eight-way

Xeon or four Dual Core 2GHz

Datab ase

Eight-way Xeon or four Dual Core 2GHz

2-Tier Web/Co llector

Dual Xeon or single Dual Core 2GHz

3-Tier Datab ase

Eight-way Xeon or four Dual Core 2GHz

3-Tier Web

Single processor 2GHz

3-Tier Collector

Dual Xeon or single Dual Core 2GHz

RAM 16GB 16GB 8GB 16GB 4GB 8GB

Separate

4 4 2 4 1 2

Disk Channels

The space allocations in the following table do not include space for backups. Allocate backup space that is equal to the size of the VCM data for a single full backup, or larger to keep multiple partial backups.

VMware, Inc.

Hardware Requirements for C ollector Machines

Table 2–7. Minimum Disk Configuration Requirements by Number of Managed Machines

Number of VCM Managed Machin es

RAID Channel and RAID Level Partitions Usable

Space

1–500 Channel 0 – RAID 1 OS 36GB

Collector Data

36GB

Files

TempDB 36GB

SQL Log Files 28GB

Channel 1 – RAID 0+1 (recommended) or

SQL Data Files 56GB

RAID 10

501–1000 Channel 0 – RAID 1 OS 36GB

Collector Data

36GB

Files

Channel 1 – RAID 1 TempDB 56GB

SQL Log Files 56GB

Channel 2 – RAID 0+1 (recommended) or

SQL Data Files 113GB

RAID10

1001–2000 Channel 0 – RAID 1 OS 36GB

Collector Data

54GB

Files

Channel 1 – RAID 1 TempDB 113GB

Channel 2 – RAID 1 SQL Log Files 113GB

Channel 3 – RAID 0+1 (recommended) or

SQLData Files 227GB

RAID 10

2001–5000 Channel 0 – RAID 1 OS 36GB

Collector Data

113GB

Files

Channel 1 – RAID 1 TempDB 227GB

Channel 2 – RAID 1 SQL Log Files 227GB

Channel 3 – RAID 0+1 (recommended) or

SQLData Files 456GB

RAID 10

VMware, Inc.

vRealize Configuration Manager Advanced Installation Guide

VMware, Inc.

Software and Operating System Requirements for Collector Machines

Your VCM environment software configuration must meet the requirements to install VCM 5.8. The software requirements are based on the number of managed machines in your environment and your installation configuration.

The software requirements are organized into steps. You must perform the steps in the order specified to ensure a successful VCM installation.

All software requirements apply to the server in your single-tier installation. For more information about installation configurations, see "VCM Installation Configurations" on page19.

Sizing Impact on Software Edition Requirements

Use the total number of managed machines that you identified in "Determine the Size of Your

Environment" on page11 to locate your environment size: 1–1000, 1001–2000, 2001–5000, or more. If you

have more than 5000 machines in your environment, contact VMware Technical Support for your specific requirements.

VCM supports Standard, Enterprise, and Datacenter editions of SQL Server 2008 R2, 2012, or 2014 versions.

NOTE Do not run VCM in a production environment when using only an evaluation version of SQL Server. Evaluation versions are not supported for production.

Table 3–1. Minimum Software Edition Requirements by Number of VCM Managed Machines

Soft ware Compo nen t

Operating System

SQL Version

SSRS Version

Number of Managed Machines

1–1000 1001–2000 2001–5000

Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2

SQL Server 2008 R2, 2012, or 2014, Standard, Enterprise, or Datacenter Edition (64-bit)

SQL Server 2008 R2, 2012, or 2014 Reporting Services

Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2

SQL Server 2008 R2, 2012, or 2014, Standard, Enterprise, or Datacenter Edition (64-bit)

SQL Server 2008 R2, 2012, or 2014 Reporting Services

Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2

SQL Server 2008 R2, 2012, or 2014, Standard, Enterprise, or Datacenter Edition (64-bit)

SQL Server 2008 R2, 2012, or 2014 Reporting Services

VMware, Inc.

vRealize Configuration Manager Advanced Installation Guide

Software Installation and Configuration Overview

VCM supports the Collector running on a Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2 operating system. Complete the preparatory steps to prepare your Windows Server 2008 R2, 2012, or 2012 R2 machine for a successful VCM installation. When you use VCM Installation Manager to install VCM, the system checks will run without error, indicating that you have met all of the requirements to install VCM.

VCM supports several installation configurations including single-tier, two-tier, and three-tier. You use Installation Manager to install VCM in these configurations.See "Preparing for Installation" on page19.

To understand the requirements to upgrade or migrate your environment to the latest version of VCM, see "Upgrading or Migrating VCM" on page137.

VMware, Inc.

Preparing for Installation

Prepare your environment for a VCMinstallation by performing the prerequisites to include hardware, software, and physical and virtual machines before you install VCM components and tools.

VCM Installation Configurations

VCM supports several installation configurations including single-tier, two-tier, and three-tier. Use Installation Manager to install VCM in these configurations.

n Single-Tier Server Installation

In a single-tier server installation, the VCM database server, Web server, and the VCM Collector components reside on a single Windows Server 2008 R2, 2012, or 2012 R2 machine, which is referred to as the VCM Collector. The installation installs all of the core VCM components, including the databases, console, and services. This configuration enables integrated security by default.

n Two-Tier Split Installation

In a two-tier split installation, the VCM database resides on a Windows Server 2008 R2, 2012, or 2012 R2 database server machine, and the VCM Collector and Web components reside together on a separate Windows Server 2008 R2, 2012, or 2012 R2 machine.

n Three-Tier Split Installation

In a three-tier split installation, the VCM databases, the Web applications, and the VCM Collector components reside on three different Windows Server 2008 R2, 2012, or 2012 R2 machines.

To perform the prerequisite steps for VCM installation, see "System Prerequisites to Install VCM" on

page21.

VMware, Inc.

vRealize Configuration Manager Advanced Installation Guide

VMware, Inc.

System Prerequisites to Install VCM

Perform the system prerequisites to prepare your physical or virtual machine for VCM installation. The prerequisites ensure that your machine meets the requirements for your environment to support a successful VCM installation.

After you perform the system prerequisites, during VCM installation the Installation Manager runs system checks on the database server, Web server, and VCM Collector machine in your installation configuration. These system checks verify that you have satisfied all of the prerequisites for a successful VCM installation. During the system checks, Foundation Checker verifies component-specific issues against VCM, captures common issues, and identifies any problems with the version of VCM being installed.

Foundation Checker might generate warnings, which you must review. In some cases, you might need to resolve the warnings before you install VCM, even though the warnings will not prevent you from starting the installation.

If Foundation Checker generates errors, you must resolve them before you install VCM. For more information about Foundation Checker, see the VCM Foundation Checker User's Guide.

Use the following topics to verify your system requirements.

n Verify that your environment meets the security requirements. See the VCM Security Guide.

n "Establish Local Administration Rights" on the next page

Verify that the user account of the person who performs the VCM installation, upgrade, or migration has all of the required rights.

n "Verify Browser Compatibility" on the next page

Verify that the target VCM Collector machine, and any other machines that will access the VCM Web console interface on the VCM Collector, have a compatible Web browser installed.

n "Verify the Default Network Authority Account" on the next page

Define the network authority account in the Local Administrators group on the Collector machine before you install VCM. The network authority account must be a domain account. VCM uses the default network authority account to collect data from Windows Agent machines.

n "Specify the Collector Services Account" on page23

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.

n "Verify the VCM Agent is Not Installed" on page24

VMware, Inc.

vRealize Configuration Manager Advanced Installation Guide

The target Windows machine must not have a VCM Agent installed before you install VCM. If an Agent is installed, you must uninstall the Agent for VCM to install.

n "Verify the SQLXML Version" on page25

SQLXML provides client-side XML functionality and enhancements to existing SQL features. Verify that the correct version is installed.

Establish Local Administration Rights

Verify that the user account of the person who performs the VCM installation, upgrade, or migration has all of the required rights.

The following rights are required.

n System administrator on the machines on which the installation or upgrade is performed.

n System administrator on the database instance to be used.

n Member of a domain.

The installing user account should not be the account used for VCM services, because the login of the VCM service account is disabled during installation.

After installation, do not create a VCM user that uses the SQL Server services account credentials.

What to do next

Verify the compatibility of your browser. See "Verify Browser Compatibility" below.

Verify Browser Compatibility

Verify that the target VCM Collector machine, and any other machines that will access the VCM Web console interface on the VCM Collector, have a compatible Web browser installed.

VCM supports the following browsers.

n Internet Explorer version 8 and 9.

n Internet Explorer version 10 and 11 in compatibility mode.

n Mozilla Firefox version 34 or later with the Internet Explorer IE Tab add-on. This add-on requires

supported Internet Explorer to be installed on the machine.

What to do next

Verify the default Network Authority account. See "Verify the Default Network Authority Account"

below.

Verify the Default Network Authority Account

You specify the default network authority account during VCM installation. The default network authority account can be a system administrator account, such as a Domain Admin in the Local Admin Group.

VMware, Inc.

System Prerequisites to Install VCM

It is acceptable, but not preferred, to use the same account for the Collector, VCM Remote, vSphere Client VCM Plug-in, and Tomcat service accounts. If you use a single account, the permissions required for the Collector service account are sufficient. The account must be a local administrator, should not be a domain administrator, has bulk-insert permissions in SQL, and is a dbo of the VCM databases. In general, the Default Network Authority should be a different account, possibly a Domain Administrator with rights on more systems in the environment.

Procedure

1. On the Collector, right-click Computer and select Manage to open Server Manager.

2. Expand Configuration, expand Local Users and Groups, and click Groups.

3. Double-click Administrators and verify that the network authority account is listed as a member of the

Administrators group.

If the user or administrator’s group is not listed, add the user or group to the list. Verify that the user has Windows administrator rights issued by the network administrator.

To change the network authority account after installing VCM, click Administration and select Settings > Network Authority.

What to do next

Keep Server Manager open to specify the Collector Services account. See "Specify the Collector Services

Account" below.

Specify the Collector Services 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

Verify that the VCM Agent is not installed on the Collector machine. See "Verify the VCM Agent is Not

Installed" on the next page.

VMware, Inc.

vRealize Configuration Manager Advanced Installation Guide

Verify the VCM Agent is Not Installed

The VCM Collector installation includes an updated Agent. The target Windows machine must not have a VCM Agent installed before you install VCM. If an Agent is installed, you must uninstall the Agent for VCM to install.

Procedure

1. To determine whether a VCM Agent is installed on the Windows machine, verify whether the following folder exists.

%windir%\CMAgent

The %windir% environment variable specifies the directory where Windows is installed. This folder is the default location. The Agent installation directory is accessible in the registry at the following location.

HKLM\Software\Configuresoft\ECM\4.0\Common\PathsRootDir

2. If a VCM Agent is installed, remove the Agent from the target Windows machine.

a. If a working VCM Collector exists, use the VCM Web console to unlicense this machine and

remove the VCM Agent.

b. If a working VCM Collector does not exist, uninstall the Agent manually.

3. To uninstall the Agent manually, determine if the Agent was installed using the MSI installer.

a. Search for the string CMAgent under the following registry key.

HKEY_LOCAL_

MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall

If an Uninstall registry subkey exists that has a GUID-named key and reference to the VCM Agent, such as {7C51E2CA-C932-44EF-8B77-3C03356A24CC}, the VCM Agent was installed using the MSI Installer.

b. Examine the uninstall data to confirm that this is the VCM Agent.

c. Open the setting UninstallString and copy the value.

An example value is as follows.

MsiExec.exe /X{7C51E2CA-C932-44EF-8B77-3C03356A24CC}

d. If an Uninstall GUIDregistry key that references the VCM Agent does not exist, the Agent was

installed using the manual installer.

4. Uninstall the VCM Agent.

a. If the Agent was installed using the MSI installer, to uninstall the Agent click Start and click Run to

execute the command line using the UninstallString registry value.

An example value is as follows.

MsiExec.exe /X{7C51E2CA-C932-44EF-8B77-3C03356A24CC}.

b. If the Agent was installed using the manual installer, run the following command to uninstall the

Agent.

%windir%\CMAgent\Uninstall\Packages\CMAgentInstall\UnCMAgentInstall.exe /S

INSTALL.LOG

What to do next

Verify that the correct version of SQLXML is installed. See "Verify the SQLXML Version" below.

VMware, Inc.

Verify the SQLXML Version

SQLXML provides client-side XML functionality and enhancements to existing SQL features. Verify that the correct version is installed.

Procedure

1. Click Start and click Control Panel.

2. Click Programs and select Programs and Features.

3. Verify that SQLXML 4.0 SP1 appears in the list of installed programs.

4. If SQLXML 4.0 SP1 does not appear, install it from the Microsoft Download Center.

What to do next

n If you will install VCM on a virtual machine, configure the disk, CPU, and memory resources. See

"Configure Resources to Install VCM on a Virtual Machine" on page27.

n Understand the use of secure communications certificates and be prepared to specify the certificates

during VCM installation. See Secure Communications Certificates in the VCM Installation Guide.

System Prerequisites to Install VCM

VMware, Inc.

vRealize Configuration Manager Advanced Installation Guide

VMware, Inc.

Configure Resources to Install VCM on a Virtual Machine

To install VCM on a virtual machine, you must prepare the virtual machine to be used as a VCM Collector. Because VCM can place heavy workloads on the database, you must understand your environment workloads to determine the resource requirements.

For the VCM Collector to operate properly on a virtual machine, the virtual machine must satisfy several prerequisites to run SQL Server on a VMware virtual machine.You should provision the VCM virtual machine similar to a high throughput OLTP database application.

Use these guidelines to install VCM in development, test, or IT environments. For large scale environments, you might need to alter the requirements.

IMPORTANT Do not install VCM on a virtual machine on an ESX server that has over-allocated resources.

Prerequisites

n Follow the requirements for physical hardware.See the VCM Installation Guide.

n Perform the system prerequisite tasks. See the VCM Installation Guide.

n Follow the best practices to install SQLServer. See the Microsoft SQL Server on VMware Best Practices

Guide available on the VMware Web site at http://www.vmware.com.

VMware, Inc.

Procedure

1. "Configure the Disk to Install VCM on a Virtual Machine" on the next page

Configure the disk for the virtual machine. For large scale environments, you might need to alter the requirements.

2. "Configure the CPU to Install VCM on a Virtual Machine" on the next page

Configure the CPU for the virtual machine. For large scale environments, you might need to alter the requirements.

3. "Configure the Memory to Install VCM on a Virtual Machine" on page29

Allocate the memory for the virtual machine. For large scale environments, you might need to alter the requirements.

What to do next

Familiarize yourself with the certificate names in advance so that you can select them during installation. See the VCM Installation Guide.

vRealize Configuration Manager Advanced Installation Guide

Configure the Disk to Install VCM on a Virtual Machine

Configure the disk for the virtual machine. For large scale environments, you might need to alter the requirements.

Prerequisites

n Prepare the virtual machine to be used as a VCM Collector. See "Configure Resources to Install VCM

on a Virtual Machine" on the previous page.

n Keep the spindle count consistent and allocate a sufficient number of spindles to the database files when

you migrate VCM from a physical machine to a virtual machine.

n Place the database data files on multiple logical unit numbers (LUNs).

n Create a TEMPDB data file for each virtual CPU that is allocated to the VCM Collector.

n Use paravirtual SCSI (PVSCSI) controllers for the database disks to provide greater throughput and

lower CPU utilization, which improves VCM performance.

n Maintain a 1:1 mapping between the number of virtual machines and the number of LUNs on a single

ESX host to avoid disk I/O contention.

Procedure

1. Start vCenter Server.

2. Select your virtual machine.

3. Click the Resource Allocation tab.

4. In the CPU pane, click Edit.

5. In the Virtual Machine Properties dialog box, click the Resources tab.

6. In the Resource Allocation pane, click Disk and update the disk resource allocation to meet the needs of your environment.

7. Click OK.

What to do next

Configure the CPUfor the virtual machine. See "Configure the CPU to Install VCM on a Virtual Machine"

below.

Configure the CPU to Install VCM on a Virtual Machine

Configure the CPU for the virtual machine. For large scale environments, you might need to alter the requirements.

Prerequisites

n Prepare the virtual machine to be used as a VCM Collector. See "Configure Resources to Install VCM

on a Virtual Machine" on the previous page.

n Test the workload in your planned virtualized environment to verify that the physical CPU resources

on the ESX host adequately meet the needs of guest virtual machines.

n Provision multiple virtual CPUs only if the anticipated workload will use them. Over-provisioning

might result in higher virtualization overhead.

n Install the latest version of VMware Tools on the guest operating system.

VMware, Inc.

Configure Resources to Install VCM on a Virtual Machine

Procedure

1. Start vCenter Server.

2. Select your virtual machine.

3. Click the Resource Allocation tab.

4. In the CPU pane, click Edit.

5. In the Virtual Machine Properties dialog box, click the Resources tab.

6. In the Resource Allocation pane, click CPU and change the CPU resource allocation.

7. Click OK.

What to do next

Configure the memory for the virtual machine. See "Configure the Memory to Install VCM on a Virtual

Machine" below.

Configure the Memory to Install VCM on a Virtual Machine

Allocate the memory for the virtual machine. For large scale environments, you might need to alter the requirements.

Prerequisites

n Prepare the virtual machine to be used as a VCM Collector. See "Configure Resources to Install VCM

on a Virtual Machine" on page27.

n Verify that the ESX host has sufficient cumulative physical memory resources to meet the needs of the

guest virtual machines. Do not install VCM on an ESX server that has over allocated resources.

n On the ESX host, enable memory page sharing and memory ballooning to optimize memory.

n To reduce or avoid disk I/O, increase the database buffer cache.

Procedure

1. Start vCenter Server.

2. Select your virtual machine.

3. Click the Resource Allocation tab.

4. In the Memory pane, click Edit.

5. In the Virtual Machine Properties dialog box, click the Resources tab.

6. In the Resource Allocation pane, click Memory and change the memory resource allocation.

7. Click OK.

What to do next

Prepare your single-tier, two-tier, or three-tier installation configuration. See "Single-Tier Server

Installation" on page35, "Two-Tier Split Installation" on page61, or "Three-Tier Split Installation" on page91.

VMware, Inc.

vRealize Configuration Manager Advanced Installation Guide

VMware, Inc.

+ 154 hidden pages