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
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
2
VMware, Inc.
Contents
About This Book7
Achieving a Successful VCMInstallation9
VCM Collector and Agent OS Platform Support9
Hardware Requirements for Collector Machines11
Determine the Size of Your Environment11
Identify Your Specific Hardware Requirements12
Database Sizing for Managed vCenter Server Instances12
Hardware and Disk Requirements By Number of Managed Machines13
Software and Operating System Requirements for Collector Machines17
Sizing Impact on Software Edition Requirements17
Software Installation and Configuration Overview18
Preparing for Installation19
VCM Installation Configurations19
System Prerequisites to Install VCM21
Establish Local Administration Rights22
Verify Browser Compatibility22
Verify the Default Network Authority Account22
Specify the Collector Services Account23
Verify the VCM Agent is Not Installed24
Verify the SQLXML Version25
Configure Resources to Install VCM on a Virtual Machine27
Configure the Disk to Install VCM on a Virtual Machine28
Configure the CPU to Install VCM on a Virtual Machine28
Configure the Memory to Install VCM on a Virtual Machine29
Secure Communications Certificates31
Authenticating the Server to the Client31
Enterprise and Collector Certificates32
Delivering Initial Certificates to Agents32
Single-Tier Server Installation35
Configure a Single-Tier Installation Environment36
Verify that the Installing User is an Administrator37
Install and Configure Windows Server Operating System38
Disable the Remote Desktop Session Host39
Enable DCOM40
Install the .NET Framework40
Verify the ASP.NET Client System Web Version41
Verify the ASPRole Service41
Verify the ASP.NETRole Service41
Configuring the Database Components of the VCM Collector41
Verify and Configure the SQL Server Properties46
Verify Matching SQL Server and Computer Names47
Verify the SQLServer Agent Service Account is a sysadmin47
Verify that the SQLServer Agent Service Starts Automatically48
Select the SQLServer Agent Service Account48
Establish SQL Server Administration Rights49
Configure the Web Components49
Configuring IIS51
Verify the ISAPI Extensions53
Configure SSRS on the VCMCollector54
Back Up Your SSRS Key54
Disable IE Protected Mode for SSRS54
Configure SSRS54
Configure Basic Authentication on the Report Server56
Configure Kerberos Authentication57
Configure the VCM Collector Components59
Two-Tier Split Installation61
Configuring a Two-Tier Split Installation Environment62
Verify that the Installing User is an Administrator63
Install and Configure Windows Server Operating System63
Disable the Remote Desktop Session Host64
Enable DCOM65
Configuring the VCM Database Server65
Disable the Firewall or Add an Exception for SQL Server Port 143366
Install SQL Server on the Database Server66
Verify and Configure the SQL Server Properties70
Verify Matching SQL Server and Computer Names71
Verify the SQLServer Agent Service Account is a sysadmin72
Verify that the SQLServer Agent Service Starts Automatically72
Select the SQLServer Agent Service Account72
Establish SQL Server Administration Rights73
Configure the Combined VCM Collector and Web Server74
Install the .NET Framework74
Configure the Web Components75
Installing and Configuring SSRS on the Combined VCM Collector and Web Server79
Configure Kerberos Authentication86
Configure the VCM Collector Components88
Three-Tier Split Installation91
Configuring a Three-Tier Split Installation Environment92
Verify that the Installing User is an Administrator92
Install and Configure Windows Server Operating System93
Disable the Remote Desktop Session Host94
Enable DCOM95
Configure the VCM Database Server95
Install SQL Server on the Database Server96
Verify and Configure the SQL Server Properties100
Verify Matching SQL Server and Computer Names100
Verify the SQLServer Agent Service Account is a sysadmin101
Verify that the SQLServer Agent Service Starts Automatically101
Select the SQLServer Agent Service Account102
Establish SQL Server Administration Rights103
Configure the Web Server103
Configuring IIS105
Verify the ISAPI Extensions107
Place the Web Server in the Internet Explorer Trusted Zone107
4
VMware, Inc.
Contents
Access to Patch Download Folder for Windows Patch Deployment107
Installing and Configuring SSRS on the Web Server109
Configure Kerberos Authentication116
Modify the SQLCMD Path Variable119
Configure the VCM Collector119
Install the .NET Framework120
Using VCM Remote121
Installing VCM125
Single-Tier Configuration125
Two-Tier Split Configuration125
Three-Tier Split Configuration125
DCOM and Port Requirements for VCM126
Install VCM using Advanced Installation126
File System Permissions127
Change Permissions On Machine Certificate Keys128
Verify VCM Remote Virtual Directory Permissions129
Configuring SQL Server for VCM131
About VCM Databases131
SQL Server Database Settings131
SQL Server Processor Settings132
Configure SQL Server Processor Settings132
SQL Server I/O Configuration133
Using the RAID Levels with SQLServer134
Disk Interface and Disk Drive Performance134
Use SQLIO to Determine I/O Channel Throughput135
Upgrading or Migrating VCM137
Upgrading VCM and Components137
Upgrade VCM138
Upgrade a Two-Tier Split VCM Configuration139
Upgrade a Three-Tier Split VCM Configuration140
Upgrade Existing Windows Agents141
Upgrade Existing VCM Remote Clients142
Red Hat Server and Workstation Licensing143
Upgrade Existing UNIX Agents143
Upgrading Virtual Environments Collections146
Upgrade the Managing Agent146
Upgrading the vSphere Client VCM Plug-In146
Upgrading Agent Proxy Machines147
Migrating VCM149
Prerequisites to Migrate VCM150
Migrate Only Your Database152
Replace Your Existing 32-Bit Environment with a Supported 64-bit Environment153
Migrate a 32-bit Environment Running VCM 5.3 or Earlier to VCM 5.8154
Migrate a 64-bit Environment Running VCM 5.3 or Earlier toVCM 5.8155
Migrate a Split Installation of VCM 5.3 or Earlier to a Single-Tier, Two-Tier, or Three-Tier
Server Installation157
How to Recover Your Collector Machine if the Migration is not Successful159
Maintaining VCM After Installation161
Customize VCM and Component-Specific Settings161
Configure Database File Growth163
Database Recovery Models163
Configure Database Recovery Settings164
Create a Maintenance Plan for SQL Server164
Incorporate the VCM Database into Your Backup and Disaster Recovery Plans166
Hardware and Operating System Requirements for VCM Managed Machines167
VCM Agent Support on Non-English Windows Platforms167
VCM Managed Machine Requirements167
Linux, UNIX, and Mac OS Agent Files170
Windows Custom Information Supports PowerShell 2.0171
Linux and UNIX Patch Assessment and Deployment Requirements171
Support for VMware Cloud Infrastructure172
Cloud and Virtualization Infrastructure Platforms172
Managing Agent Requirements172
Agent Proxy Requirements for VMware ESX and ESXi172
vRealize Operations Manager Integration Features173
FIPS Requirements173
FIPS for Windows174
FIPS for VCM Agent Proxies175
Agent Sizing Information175
Windows Machines176
Linux and UNIX Machines177
Mac OS X Machines178
Index179
6
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 SQLServer 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 OSX, 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
InstallationGuide, VCM online help, and other associated documentation.
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 OfferingsTo 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.
8
VMware, Inc.
Achieving a Successful
VCMInstallation
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.
1
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 VCMdatabase, 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.
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
page11 and "Software and Operating System Requirements for Collector Machines" on page17.
For details about VCM managed machines, see "Hardware and Operating System Requirements for VCM
Managed Machines" on page167.
10
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.
2
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.
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
ProductDescriptionAnticipated Number of Managed
Machin es in the Next 12–24 Month s
VCMWindows 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 SQLServer 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.
12
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. VCMDatabase Sizing per vCenter Server Instance
Host sGuestsEst. Daily Ch ang eData Reten tio n in DaysData Size
2525010%153GB
5050010%156GB
250250010%1530GB
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 SQLServer 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-VEnvironment 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.
Table 2–4. Minimum Hardware Requirements to Support 1–1000 Managed Machines
Single Tier2-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
Dual Xeon or
single Dual
Core 2GHz
Dual Xeon or
single Dual
Core 2GHz
Single
processor
2GHz
Single
processor
2GHz
RAM8GB8GB4GB8GB4GB4GB
Separate
221211
Disk
Channels
Table 2–5. Minimum Hardware Requirements to Support 1001–2000 Managed Machines
Single Tier2-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
RAM12GB12GB4GB12GB4GB4GB
Separate
332312
Disk
Channels
Table 2–6. Minimum Hardware Requirements to Support 2001–5000 Managed Machines
Single Tier2-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
RAM16GB16GB8GB16GB4GB8GB
Separate
442412
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.
14
VMware, Inc.
Hardware Requirements for C ollector Machines
Table 2–7. Minimum Disk Configuration Requirements by Number of Managed Machines
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 page19.
Sizing Impact on Software Edition Requirements
Use the total number of managed machines that you identified in "Determine the Size of Your
Environment" on page11 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.
3
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–10001001–20002001–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
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 page19.
To understand the requirements to upgrade or migrate your environment to the latest version of VCM,
see "Upgrading or Migrating VCM" on page137.
18
VMware, Inc.
Preparing for Installation
Prepare your environment for a VCMinstallation 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.
4
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
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.
5
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 page23
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 page24
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 page25
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
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.
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.
22
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
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
Verify that the VCM Agent is not installed on the Collector machine. See "Verify the VCM Agent is Not
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.
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.
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 SQLServer. See the Microsoft SQL Server on VMware Best Practices
Guide available on the VMware Web site at http://www.vmware.com.
6
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 page29
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.
During VCM installation, specify the Collector and Enterprise certificates. VCM uses Transport Layer
Security (TLS) to secure all UNIX Agents and all Windows Agents using HTTP, and TLS uses certificates to
authenticate the Collector and Agents to each other.
If you use your own certificates, you must familiarize yourself with the certificate names in advance so
that you can select them during installation.
A valid Collector certificate must have the following attributes.
n Located in the local machine personal certificate store.
n Valid for Server Authentication. If any Enhanced Key Usage extension or property is present, it must
include the Server Authentication OID 1.3.6.1.5.5.7.3.1. If the Key Usage extension is present, it
must include DIGITAL_SIGNATURE.
n Active, and not expired.
If you do not want to use your own certificates, you can have Installation Manager generate the Collector
and Enterprise certificates for you, select the Generate option during the installation.
If you install more than one Collector that will communicate with the same Agents, or if you plan to
replace or renew your certificates, follow the special considerations to generate and select certificates in
VCM Installation Manager. See the VCM Security Guide.
7
Authenticating the Server to the Client
VCM supports Server Authentication to authenticate the server to the client. In VCM environments where
TLS is used, VCM Agents verify the identity of the Collectors by verifying the certificates. If you use your
own certificates, you must familiarize yourself with the certificate names in advance so that you can select
them during installation.
The server typically authenticates a client or user by requiring information such as a user name and
password. When Server Authentication is used, the client or user verifies that the server is valid. To
accomplish this verification, the server provides a certificate issued by a trusted authority, such as Verisign.
If your client Web browser has the Verisign Certified Authority certificate in its trusted store, the Web
browser can trust that the server is actually the Web site you access.
To guarantee the identity of servers and clients, TLS uses certificates that are managed by a public key
infrastructure (PKI). A certificate is a package that contains a public key, information that identifies the
owner and source of that key, and one or more certifications (signatures) to verify that the package is
authentic. To sign a certificate, an issuer adds information about itself to the information that is already
contained in the certificate request. The public key and identifying information are hashed and signed
using the private key of the issuer’s certificate.
Certificates are defined by the X.509 RFC standard, which includes fields that form a contract between the
creator and consumer. The Enhanced Key Usage extension specifies the use for which the certificate is
valid, including Server Authentication.
Enterprise and Collector Certificates
An Enterprise Certificate and one or more Collector Certificates enable secure HTTP Collector and Agent
communication in VCM. The Enterprise Certificate enables VCM to operate in a multi-Collector
environment. Agents have the Enterprise Certificate in their trusted certificate stores, and they use the
Enterprise Certificate to validate any certificate issued by the Enterprise Certificate. All Collector
Certificates are expected to be issued by the Enterprise Certificate, which is critical in environments where
a single Agent is shared between multiple Collectors.
Server authentication is required to establish a TLS connection with an Agent. All VCM Collectors should
have a common Enterprise Certificate. Each Collector Certificate is issued by the Enterprise Certificate,
and is capable of Server Authentication. Collector Certificates in VCM must adhere to the requirements
for secure communications certificates. See "Secure Communications Certificates" on the previous page.
n The Collector Certificate initiates and secures a TLS communication channel with an HTTP Agent. The
Agent must be able to establish that the Collector Certificate can be trusted, which means that the
Collector Certificate is valid and the certification path starting with the Collector Certificate ends with a
trusted certificate. By design, the Enterprise Certificate is installed in the Agent’s trusted store. The trust
chain ends with the Enterprise Certificate.
n Self-signed Agent Certificates are generated during Agent installation, upon first contact from the
Collector. Agent Certificates are used for Mutual Authentication only. VCM support for Mutual
Authentication requires the administrator to manually verify the fingerprint of each Agent's certificate
before marking those Agents as trusted in Administration > Certificates.
n The Collector Certificate and associated private key must be available to the Collector. This certificate is
stored in the local machine personal system store.
Delivering Initial Certificates to Agents
VCM Agents use the Enterprise Certificate to validate Collector Certificates. The Agent must have access
to the Enterprise Certificate as a trusted certificate. In most cases, VCM delivers and installs the Enterprise
Certificate as needed during the HTTP Agent installation.
When you manually install Windows HTTP or VCM Remote client components, you must specify a path
to the PEM file that provides the Enterprise Certificate and the Collector's public key.
Installing the Agent from a Disk (Windows only)
The VCM Installation DVD does not contain customer-specific certificates. If HTTP is specified, the manual
VCM installer requests the location of the Enterprise Certificate file during the installation. You must have
the Enterprise Certificate file available at installation time. You can copy the certificate file, which has a
.pem extension, from the CollectorData folder on the Collector. You must copy the certificate file
when you run the manual installer directly using CMAgentInstall.exe or when you use the AgentOnly option in the DVD auto-run program.
32
VMware, Inc.
Secure Communications Certificates
Using CMAgentInstall.exe to install the Agent (Windows only)
The CMAgentInstall.exe or CMAgent[version].msi is the manual Agent installer program. The
manual installer requests the location of the Enterprise Certificate file when HTTP is specified. You must
have the Enterprise Certificate file available at installation time. You can copy the certificate file from the
CollectorData folder on the Collector. For information about using the EXE and command line options
to install the Agent, see the VCM Administration Guide.
Using the MSI Install Package
When you specify HTTP, the MSI Agent install package also requires access to the .pem file. For
information about using the MSI and command line options to install the Agent, see the VCMAdministration Guide.
Installing the Agent for Linux and UNIX
See Install the Agent on Linux and UNIX Machines in the VCM Administration Guide.
What to do next
Configure your installation configuration. See "Single-Tier Server Installation" on page35, "Two-Tier Split
Installation" on page61, or "Three-Tier Split Installation" on page91.
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. Integrated security, also
referred to as Windows Authentication or NT Challenge Response authentication, provides trusted logon
to the Web console without having to configure Kerberos.
VCM 5.8 supports 64-bit environments that include 64-bit hardware, the 64-bit Windows Server 2008 R2,
Windows Server 2012, or Windows Server 2012 R2 operating system, and SQL Server 2008 R2, or 2012, or
2014.
Figure 8–1. Single-Tier Server Installation Components
VCM Agent Proxies for Virtualization can be installed on the VCM Collector, which is the default
installation, or on one or more separate Windows Servers.
n If the Agent Proxy is installed on the VCM Collector, which is the default installation, the Collector
communicates directly with the ESX Servers.
n If the Agent Proxy is installed on a separate Server, which is optional, the VCM Collector communicates
with the Agent Proxy Server, which communicates with the ESX Servers.
Configure a Single-Tier Installation Environment
In a single-tier installation configuration, you configure the single Windows Server 2008 R2, 2012, or 2012
R2 machine for the Database, Web, and VCM Collector components, then install VCM. The machine can
be a physical or virtual Windows machine.
Prerequisites
n Perform the general system prerequisites. See "System Prerequisites to Install VCM" on page21.
n Connect the single Windows Server 2008 R2, 2012, or 2012 R2 VCM Collector machine to your domain.
n Obtain the installation media for the Enterprise, Standard, or Datacenter edition of SQL Server 2008 R2,
2012, or 2014, or verify access to a file share where the installer resides.
n Verify that the single-tier server machine has at least 11 GB of free disk space and 2GB of RAM.
36
VMware, Inc.
Single-Tier Server Installation
Procedure
1. "Verify that the Installing User is an Administrator" below
The user who installs Windows Server 2008 R2, 2012, or 2012 R2 operating system must be an
Administrator and a domain account.
2. "Install and Configure Windows Server Operating System" on the next page
Install the Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2 operating
system on each Windows machine that serves as a tier in your configuration.
3. "Install the .NET Framework" on page40
To support library and language interoperability, the VCMCollector must have the required versions
of the .NET Framework installed.
4. "Configuring the Database Components of the VCM Collector" on page41
To ensure that the installation creates the VCM databases, you must configure the database
components of the VCM Collector before you install VCM. In a single-tier installation configuration,
the VCM database resides on the VCM Collector. The databases include VCM, VCM_Coll, VCM_Raw,
and VCM_UNIX.
5. "Configure the Web Components" on page49
The Web components of the VCM Collector contain Web applications such as IIS and SQL Server
Reporting Services (SSRS), other services, and VCM software components. Before you install VCM,
you must configure the Web components of the VCM Collector.
6. "Configure SSRS on the VCMCollector" on page54
SQL Server Reporting Services (SSRS) is a server-based report generation software system that is
administered using a web interface and used to deliver VCM reports.
7. "Configure the VCM Collector Components" on page59
The VCM Collector contains the VCM software application and VCM services. To prepare the VCM
Collector components for VCM installation, configure the required utilities.
What to do next
Review the DCOMand port requirements, and use VCM Installation Manager to install the VCM
components. See "Installing VCM" on page 125.
Verify that the Installing User is an Administrator
The user who installs Windows Server 2008 R2, 2012, or 2012 R2 operating system must be an
Administrator and a domain account.
a. Click Start and select All Programs > Administrative Tools > Computer Management.
b. Expand System Tools, expand Local Users and Groups, and click Users.
c. Right-click the user and click Properties.
d. Click the Member Of tab and verify that Administrators is listed.
e. If Administrators is not listed, add the user to the Administrators group.
f. Click Check Names and click OK.
2. Verify that the user is a domain account.
a. Click Groups.
b. Right-click Administrators and click Properties.
c. Verify that the Domain User is listed in the Members area.
What to do next
Prepare your Windows machine for VCM installation. See "Install and Configure Windows Server
Operating System" below.
Install and Configure Windows Server Operating System
Install the Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2 operating system
on each Windows machine that serves as a tier in your configuration.
Prerequisites
n Determine whether you require Windows Server 2008 R2, 2012, or 2012 R2 operating system. See
"Sizing Impact on Software Edition Requirements" on page 17.
n The user who installs Windows Server 2008 R2, 2012, or 2012 R2 operating system must be an
Administrator and a domain account. See "Verify that the Installing User is an Administrator" on page
37.
n Decide on a valid DNS computer name with no underscores for use when the Windows installation
prompts for a machine name. If you attempt to change the machine name after a machine is identified
as a Collector, problems might occur with VCM, SQL Server, and SQL Server Reporting Services.
38
VMware, Inc.
Single-Tier Server Installation
Procedure
1. Install Microsoft Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2 on your
Windows machine.
2. During the installation, you can configure several options.
OptionDescription
Regional and
Language
Determines how numbers, dates, currencies, and time settings appear.
n Language: Setting for your language. The default is English.
Options
n Time and currency format: Determines how numbers, dates, currencies, and time
settings appear. The default is English (United States).
n Keyboard or input method: Allows text entry for multiple languages. The default
is US.
Disk
Configuration
Allows you to separate the machine disk drive into partitions to store data in
different partitions. You can create new disk partitions and delete existing partitions.
After you configure the disk, select a partition on which to install Windows Server
2008 R2, 2012, or 2012 R2 Edition.
Product KeyWhen the installation prompts, enter your product key.
Licensing
Modes
Administrator
Password
Windows Server 2008 R2, 2012, or 2012 R2 supports a single license that is included
with the product key.
The installation setup creates an account called administrator. To log in, you must
create a password that complies with the criteria. The password must have the
following attributes.
n Minimum of six characters
n Does not contain “administrator” or “admin”
n Contains uppercase letters
n Contains lower case letters
n Contains numbers
n Contains at least one non-alphanumeric character
3. Perform the initial configuration tasks to set the time zone and the computer name.
Disable the Remote Desktop Session Host
A Remote Desktop Session Host server hosts Windows-based programs for Remote Desktop Services
clients.
If the Remote Desktop Session Host role service is enabled, you must disable it to avoid changes to
settings for new connections, modifications of existing connections, or removal of connections.
1. Click Start and select All Programs > Administrative Tools > Server Manager.
2. In the navigation pane, expand Roles and click Remote Desktop Services.
3. In the Remote Desktop Services pane, scroll down to Role Services.
4. Click the Remote Desktop Session Host role service to highlight it.
5. Click Remove Role Services.
6. Deselect the Remote Desktop Session Host role service and follow the prompts to finish disabling the
Remote Desktop Session host role.
Enable DCOM
The Distributed Component Object Model (DCOM) protocol allows application components to interact
across Windows machines. DCOM must be enabled on the Windows machine to install and run VCM.
Although DCOMis enabled by default when Windows Server 2008 R2, 2012, or 2012 R2 is installed,
DCOMmight have been disabled by a custom installation or a lock-down script.
Procedure
1. Click Start and select All Programs > Administrative Tools > Component Services to open
Component Services.
2. In the Component Services navigation pane, expand Component Services and expand Computers.
3. Right-click the computer and click Properties.
4. Click the Default Properties tab.
5. Select Enable Distributed COM on this computer and click OK.
What to do next
Install the .NET framework. See "Install the .NET Framework" below.
Install the .NET Framework
To support library and language interoperability, the VCMCollector must have the required versions of
the .NET Framework installed.
VCM 5.8 requires the .NET 3.5.1 Framework. If you use Package Studio, the VCM Collector must have
.NET 3.5.1 installed. If you use Package Manager, the VCM Collector must have .NET 3.5.1 or .NET 4.0
installed.
Determine the installed version of the .NET Framework. If one of the .NET Framework versions is
missing, install the version from the Microsoft download Web site.
Procedure
1. Click Start and select All Programs > Administrative Tools > Server Manager.
2. Click Features.
3. Verify that .NET Framework 3.5.1 appears in the feature summary.
4. If .NET Framework 3.5.1 does not appear, under Features select Add Features and select .NET 3.5.1.
40
VMware, Inc.
Single-Tier Server Installation
Verify the ASP.NET Client System Web Version
To support client programming, verify the ASP.NET Client System Web version to confirm that the .NET
framework is installed correctly, and install it if the version is not correct.
1. Click Start and select All Programs > Administrative Tools > Internet Information Services (IIS)Manager.
2. Expand <server name> and click Sites.
3. Expand Default Web Site, expand aspnet_client, and expand system_web.
4. Verify that the version is 2_0_50727.
Verify the ASPRole Service
To support client programming, verify the status of the ASP Role Service to confirm that the .NET
framework is installed correctly.
Procedure
1. Click Start and select All Programs > Administrative Tools > Server Manager.
2. Expand Server Manager (<server name>) and expand Roles.
3. Click Web Server (IIS).
4. Scroll down to Role Services.
5. Locate ASP and verify whether the role service is installed.
6. If the role service is not installed, click Add Role Services and add the ASP role service.
Verify the ASP.NETRole Service
To support client programming, verify the status of the ASP.NET Role Service to confirm that the .NET
framework is installed correctly.
Procedure
1. Click Start and select All Programs > Administrative Tools > Server Manager.
2. Expand Server Manager (<server name>) and expand Roles.
3. Click Web Server (IIS).
4. Scroll down to Role Services.
5. Locate ASP.NET and verify that the role service is installed.
6. If the role service is not installed, click Add Role Services and add the ASP.NET role service.
What to do next
Configure the database components. See "Configuring the Database Components of the VCM Collector"
below.
Configuring the Database Components of the VCM Collector
To ensure that the installation creates the VCM databases, you must configure the database components
of the VCM Collector before you install VCM. In a single-tier installation configuration, the VCM database
resides on the VCM Collector. The databases include VCM, VCM_Coll, VCM_Raw, and VCM_UNIX.
Use of a shared SQL Server is supported for VCM. However, VCM makes heavy use of SQL Server for
query and transaction processing. You must ensure that you have or can add enough capacity to a shared
SQL Server so that VCM and any other databases on the shared server do not experience poor
performance.
VCM operates with a Standard, Enterprise, or Datacenter edition of SQL Server. You must install the 64-bit
SQL Server 2008 R2, or 2012, or 2014 version on your designated database server machine and verify that
the settings are configured correctly for a VCM installation.
If you plan to change the communication port that SQL Server uses from the default port of 1433 to a
nonstandard port number, make the changes during the installation of SQL Server and SQL Server
Reporting Services (SSRS). Changing the port after you install SSRS disables SSRS communication with
SQL Server, which causes an SSRS validation error during the VCM installation process. If you change the
port after installation, you must configure additional SSRS settings to repair the configuration.
Install SQL Server on the VCMCollector
In a single-tier installation configuration, the VCM database server resides on the same server on which
you install VCM. The database server contains the VCM, VCM_Coll, VCM_Raw, and VCM_UNIX
databases. You must configure the VCM database server before you install VCM in a single-tier
installation configuration.
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.
Prerequisites
n Obtain the installation media for the Enterprise, Standard, or Datacenter edition of SQL Server 2008 R2,
2012, or 2014, or verify access to a file share where the installer resides.
Procedure
1. Start the SQLServer installation.
2. Perform the following actions to install SQL Server.
For SQL Server 2008 R2
Wizard PageAction
SQL Server
Click New installation or add features to an existing installation.
Installation
Center
Setup Support
Rules
Setup Support
Click Install and verify that all of the rules pass. To view the detailed system
configuration check report, click the link.
Click Install to install the setup support files.
Files
Setup Support
Verify that all of the rules passed.
Rules – for
SQL Server
Setup support
files
Product KeyVerify that the product key is entered.
License Terms Accept the license terms.
42
VMware, Inc.
Wizard PageAction
Setup RoleSelect SQL Server Feature Installation.
Single-Tier Server Installation
Feature
Selection
Installation
Rules
Instance
Configuration
Disk Space
Requirements
Server
Configuration
Select the following features.
Instance Features:
n Database Engine Services
n Reporting Services
Shared Features:
n Client Tools Connectivity
n SQL Server Books Online
n Management Tools - Basic
and Management Tools - Complete
Verify that the rules passed. To view the detailed system configuration check
report, click the link.
Select Default Instance. If an instance of SQL Server is not installed, the installation
creates a default instance. If an instance of SQLServer is already installed, select
Named Instance and assign a name.
Review the disk usage summary.
Click Use the same account for all SQL Server services and enter the NT
AUTHORITY\SYSTEM account and password.
It is possible to use a domain account for SQL Server services. A domain account
might be required for split installations, because the SQL Server Agent might need
access to the Collector for some activities. If you use a domain account, you should
use a local administrator on the SQL Server machine to access DBServices.
Otherwise, you must grant manual permissions.
VMware, Inc.
Database
Engine
Select Windows authentication and click Add Current User to add the account to
the SQL Server administrators.
Configuration
Reporting
Services
Specify the reporting services configuration mode. Select Install the native mode
default configuration.
Configuration
Error
Review the summary information.
Reporting
Installation
Configuration
Verify that the rules passed. To view the detailed system configuration check
report, click the link.
Rules
Ready to
Install
Review the summary of features and click Install to install SQL Server. When the
installation is finished, click the link to view the log file.
Click New SQL Server stand-alone installation or add features to an existing
installation.
Center
Setup Support
Rules
Product
Updates
Install Setup
Click Install and verify that all of the rules pass. To view the detailed system
configuration check report, click the link.
Check for SQL Server updates.
Verify that all rules are passed.
Files
Setup Support
Verify that all of the rules passed.
Rules – for
SQL Server
Setup support
files
Product KeyVerify that the product key is entered.
License Terms Accept the license terms.
Setup RoleSelect SQL Server Feature Installation.
Feature
Selection
Select the following features.
Instance Features:
Installation
Rules
Instance
Configuration
Disk Space
Requirements
Server
Configuration
n Database Engine Services
n Reporting Services
Shared Features:
n Client Tools Connectivity
n Management Tools - Basic
and Management Tools - Complete
Verify that the rules passed. To view the detailed system configuration check
report, click the link.
Select Default Instance. If an instance of SQL Server is not installed, the installation
creates a default instance. If an instance of SQLServer is already installed, select
Named Instance and assign a name.
Review the disk usage summary.
Browse the accounts for all SQL services and enter the NT AUTHORITY\SYSTEM
account.
It is possible to use a domain account for SQL Server services. A domain account
might be required for split installations, because the SQL Server Agent might need
access to the Collector for some activities. If you use a domain account, you should
use a local administrator on the SQL Server machine to access DBServices.
Otherwise, you must grant manual permissions.
44
VMware, Inc.
Wizard PageAction
Single-Tier Server Installation
Database
Engine
Select Windows authentication and click Add Current User to add the account to
the SQL Server administrators.
Configuration
Reporting
Specify the reporting services configuration mode. Select Install and Configure.
Services
Configuration
Error
Review the summary information.
Reporting
Installation
Configuration
Verify that the rules passed. To view the detailed system configuration check
report, click the link.
Rules
Ready to
Install
Review the summary of features and click Install to install SQL Server. When the
installation is finished, click the link to view the log file.
For SQL Server 2014
Wizard PageAction
SQL Server
Installation Center
Click New SQL Server stand-alone installation or add features to anexisting installation.
Product KeyVerify that the product key is entered.
License TermsAccept the license terms.
Microsoft UpdateUse this option to check for Microsoft updates.
Install Setup FilesVerify that all rules are passed.
Setup RoleSelect SQL Server Feature Installation.
Feature SelectionSelect the following features.
Instance Features:
n Database Engine Services
n Reporting Services
Shared Features:
n Client Tools Connectivity
n Management Tools - Basic
and Management Tools - Complete
Instance
Configuration
Select Default Instance. If an instance of SQL Server is not installed, the
installation creates a default instance. If an instance of SQLServer is already
installed, select Named Instance and assign a name.
Browse the accounts for all SQL services and enter the NT
AUTHORITY\SYSTEM account.
It is possible to use a domain account for SQL Server services. A domain
account might be required for split installations, because the SQL Server
Agent might need access to the Collector for some activities. If you use a
domain account, you should use a local administrator on the SQL Server
machine to access DBServices. Otherwise, you must grant manual
permissions.
Database Engine
Configuration
Reporting Services
Configuration
Select Windows authentication and click Add Current User to add the
account to the SQL Server administrators.
Specify the reporting services configuration mode. Select Install andConfigure.
Ready to InstallReview the summary of features and click Install to install SQL Server. When
the installation is finished, click the link to view the log file.
What to do next
n Reboot the single-server machine.
n Configure the SQLServer properties. See "Verify and Configure the SQL Server Properties" below.
Verify and Configure the SQL Server Properties
To ensure that SQLServer will operate with VCM, verify the SQLServer property settings and set the
server-wide SQL database settings in preparation to install VCM. For information about server-wide and
database-specific SQL Server database settings, see the VCM Administration Guide.
Procedure
1. Launch SQL Server Management Studio.
2. Right-click the SQL instance and select Properties.
3. Confirm the General page server property of Version as 10.50.1600.1 or some later build of version
10.50.
4. Select and confirm the Security page server properties.
a. Select Windows Authentication mode, which is recommended.
b. Although SQL Server and Windows Authentication mode is acceptable for VCM, select Windows
Authentication mode, which is recommended.
5. Select and confirm the Database Settings page server properties.
a. For Default index fill factor, type or select a percentage value, which specifies the amount of free
space in each index page when the page is rebuilt.
Set the fill factor to 80% to keep 20% free space available in each index page.
b. For Recovery interval (minutes), type or select 5.
6. Click OK to save your changes.
46
VMware, Inc.
Single-Tier Server Installation
What to do next
To ensure that SQLServer and VCMoperate correctly together, verify that the SQLServer name matches
the Windows machine name. See "Verify Matching SQL Server and Computer Names" below.
Verify Matching SQL Server and Computer Names
To ensure that SQLServer and VCM operate correctly together, you must verify that the SQLServer
name matches the Windows machine name. If you recently installed SQL Server, you do not need to
verify that the names match. If you obtained a machine that was renamed after the operating system and
SQL Server were installed, verify and reset the SQLServer server name.
Procedure
1. Launch SQL Server Management Studio.
2. Click Database Engine Query.
3. In the SQL Query pane, type SELECT @@Servername and click Execute.
4. Verify that the resulting SQL Server name matches the Windows machine name.
5. If the SQL Server name does not match the Windows machine name, reset the SQL Server name.
a. In the SQL Query pane, type the following command and replace NewServerName with the server
Verify that the SQL Server Agent service is configured to start automatically. See "Verify that the
SQLServer Agent Service Starts Automatically" below.
Verify that the SQLServer Agent Service Starts Automatically
VCM uses the SQL Server Agent service to run all scheduled jobs and SSRS reports, including dashboards.
Set the service to automatically start on the VCM server.
Procedure
1. On the VCM server, click Start and select Administrative Tools > Services.
2. Right-click SQL Server Agent, and select Properties.
3. From the Startup type menu, select Automatic.
4. Click OK, and close the Services window.
What to do next
Select the SQL Server Agent service account See "Select the SQLServer Agent Service Account" below.
Select the SQLServer Agent Service Account
SQL Server Agent is a service that runs scheduled jobs in SQLServer and runs as a specific user account.
Verify that the SQL Server Agent service account that you provided during the SQL Server installation is a
SQL Server sysadmin.
Prerequisites
n Verify that the account you provide for the SQL Server Agent service has permission to log in as a
service and the required additional permissions. See the online Microsoft Developer Network for more
information.
n Understand the supported service account types for non-clustered and clustered servers. VCM 5.8
supports Active/Active SQL clusters. See the online Microsoft Developer Network for more
information.
n Verify that the account you will use for the SQL Server Agent service account has the sysadmin
privilege. See "Verify the SQLServer Agent Service Account is a sysadmin" on page 47.
Procedure
1. On the VCMdatabase server machine, click Start and select All Programs.
2. Click Microsoft SQL Server {version} > Configuration Tools > SQL Server ConfigurationManager.
48
VMware, Inc.
Single-Tier Server Installation
3. Click SQL Server Services.
4. Right-click SQL Server Agent (MSSQLSERVER) and click Properties.
5. On the Log On tab, select a log in option and provide the account information.
OptionDescription
Built-in accountIn a single-tier installation, you can select the Local System account,
which has unrestricted access to all system resources. In a split
installation environment, do not select the built-in Local System
account. This account is a member of the Windows Administrators
group on the local machine.
This accountIn a split installation, the SQLServer Agent must be running as a user
account. Select a Windows domain account for the SQL Server Agent
service account.
This option provides increased security. Select this option for jobs that
require application resources across a network, to forward events to
other Windows application logs, or to notify administrators through
email or pagers.
6. Type or select an account name that has the sysadmin privilege.
7. Click OK.
What to do next
Establish SQLServer administration rights. See "Establish SQL Server Administration Rights" below.
Establish SQL Server Administration Rights
Members of the SQLServer sysadmin fixed server role can perform any activity in the server. The user
who installs VCM must have SQL Server sysadmin rights.
Procedure
1. Launch SQL Server Management Studio.
2. Expand the server instance, select Security and select Logins.
3. Right-click the login ID of the user who installs VCM and select Properties.
4. In the Select a page area, select Server Roles.
5. In the Server roles area, select the sysadmin check box.
6. Click OK to save the settings and close the window.
What to do next
Configure the Web components of the VCM Collector. See "Configure the Web Components" below.
Configure the Web Components
The Web components of the VCM Collector contain Web applications such as IIS and SQL Server
Reporting Services (SSRS), other services, and VCM software components. Before you install VCM, you
must configure the Web components of the VCM Collector.
The Windows machine that hosts the Web components must be running Internet Information Services
(IIS) 7.5. IIS is installed when you install Windows Server 2008 R2, 2012, or 2012 R2.
The SQL Server license includes SQL Server Reporting Services (SSRS). In your installation configuration,
when you run SSRS and SQL Server on the same machine, the SQL Server database machine can take on
the role of the Report Server (SSRS).
VCM 5.8 supports running SSRS on the Web server or on the database server in a split installation.
Depending on the separation of services in your environment, you might want to install SSRS on the Web
server machine in a split installation, because SSRS has its own Web server.
If you install SSRS on the Web server, it requires an additional SQL Server license, because you are
installing SSRS on a Windows Server 2008 R2, 2012, or 2012 R2 machine that is separate from the SQL
Server database services. If you run SQL Server Enterprise Edition, all SQL Server services running in
guests on a single virtual machine host are covered by the Enterprise Edition license.
Prerequisites
n Perform the prerequisite tasks for your installation configuration.
n Place the Web server in the Internet Explorer Trusted Zone so that Internet Explorer can delegate the
VCM user's credentials to the Web service for use with SQL Server. See "Place the Web Server in the
Internet Explorer Trusted Zone" on page 107.
n If the domain firewall is turned on, verify that any required ports are open. If the database server is
blocked from communicating with the Collector, problems can occur when you submit jobs. VCM
displays an error about the SAS service, and the VCM Debug Event Log displays failures when calling
ecm_sp_collector_control.
n Verify that .NET Framework 3.5.1 is installed on Windows Server 2008 R2, 2012, or 2012 R2 machines
where Package Studio will be installed.
n Verify that you have an Internet connection to check for patch bulletin updates.
n On the Windows Server 2008 R2, 2012, or 2012 R2 Web server machine, verify that the following .NET
Framework components are installed.
n Windows Process Activation Service
n Process Model
n .NETEnvironment
n Configuration APIs
Procedure
1. Restart the Web server machine.
2. Click Start and select All Programs > Administrative Tools > Server Manager.
3. Click Roles and verify that the Web Server (IIS) role appears.
4. If the Web Server (IIS) role does not appear, in the Roles Summary area, click Add Roles and add the
Web Server (IIS) role.
5. On the Select Server Roles page, select Web Server (IIS) and select the Web Server components to
add.
50
VMware, Inc.
OptionAction
Common HTTPFeaturesSelect these options:
n Static Content
n Default Document
n Directory Browsing
n HTTP Errors
Application DevelopmentSelect these options:
n ASP .NET
n .Net Extensibility
n ASP
n ISAPI Extensions
n ISAPI Filters
n Server Side Includes
Health and DiagnosticsSelect these options:
Single-Tier Server Installation
n HTTP Logging
n Request Monitor
SecuritySelect these options:
n Basic Authentication
n Request Filtering
PerformanceSelect:
n Static Content Compression
Configuring IIS
To ensure that the Web components are correctly configured, verify that the correct role services are
enabled, the bindings are set correctly, and the default Web site is correct.
Verify the IIS 7.5 Ro le Services are Enabled
Verify that the correct IIS 7.5 Role Services are enabled on the VCM Collector.
Procedure
1. On the Collector, click Start and select All Programs > Administrative Tools > Server Manager.
2. Expand Roles and click Web Server (IIS).
3. If the Web Server (IIS) role does not appear in the list of Roles, scroll to Role Services, click Add Role
Services and add the Web Server (IIS) Role.
VMware, Inc.
When you installed IIS, the ASP Role Service, ASP.NET Role Service, and IIS ServerSideIncludes Role
Service were installed.
4. In the Web Server (IIS) pane, scroll to Role Services and verify that the status is set to Installed for the
following Role Services.
Role Service CategoryRole Service
Common HTTP FeaturesStatic Content
Application DevelopmentASP.NET
Health and DiagnosticsHTTP Logging
Default Document
Directory Browsing
HTTPErrors
HTTPRedirection
.NET Extensibility
ASP
ISAPIExtensions
ISAPI Filters
Server Side Includes
Logging Tools
Request Monitor
Tracing
SecurityBasic Authentication
Windows Authentication
Digest Authentication
URL Authorization
Request Filtering
IP and Domain Restrictions
PerformanceStatic Content Compression
Dynamic Content Compression
Management ToolsIISManagement Console
IIS Management Scripts and Tools
Management Service
5. If any of the Role Services are not installed, click Add Role Services, select the check boxes of the
services to install, and click Install.
Con figure the IIS 7.5 Settings
IIS settings configure the information required for requests to communicate with a Web site. To support
VCMinteraction with IIS, configure the settings for the IIS 7.5 bindings on the VCMCollector machine to
ensure that the settings are correct.
52
VMware, Inc.
Single-Tier Server Installation
Procedure
1. Click Start and select All Programs > Administrative Tools > Internet Information Services (IIS)
Manager.
2. Expand <server name>, expand Sites, and click Default Web Site.
3. In the Actions pane, under Manage Web Site and Browse Web Site, click Advanced Settings.
4. Expand Connection Limits and set Connection Time-out (seconds) to 3600.
5. Click OK.
Verify the IIS 7.5 Def ault Web Site
IIS 7.5 provides a default Web site that defines the default authentication settings for applications and
virtual directories. Verify that the IIS 7.5 default Web site has the correct settings.
Procedure
1. Click Start and select All Programs > Administrative Tools > Internet Information Services (IIS)
Manager.
2. Expand <server name>, expand Sites, and click Default Web Site.
3. In the Default Web Site Home pane, locate the IIS options.
4. Double-click Authentication and set the authentication.
OptionAction
Anonymous Authentication Set to Disabled.
ASP.NET ImpersonationSet to Disabled.
Basic AuthenticationSet to Enabled.
Forms AuthenticationSet to Disabled.
Verify the ISAPI Extensions
The ISAPI Extensions role provides support for dynamic Web content development. You must verify that
the role service is installed, and install it if needed.
Procedure
1. Click Start and select All Programs > Administrative Tools > Server Manager.
2. Expand Server Manager (<server name>) and expand Roles.
3. Click Web Server (IIS).
4. Scroll to Role Services.
5. Locate ISAPI Extensions and verify that the role service is installed.
6. If the role service is not installed, click Add Role Services and add the ISAPI Extensions role service.
VMware, Inc.
What to do next
Prepare SQL Server Reporting Services (SSRS) to generate VCM reports. See "Configure SSRS on the
SQL Server Reporting Services (SSRS) is a server-based report generation software system that is
administered using a web interface and used to deliver VCM reports.
Back Up Your SSRS Key
The rskeymgmt utility manages the symmetric keys used by a report server. This utility provides a way to
delete encrypted content that can no longer be used if you cannot recover or apply the key.
Use the Microsoft command-line utility to back up the symmetric key to an encrypted file.
Prerequisites
n See the online Microsoft Support center for details about how to use the rskeymgmt utility.
Procedure
1. On the Collector file system, locate the rskeymgmt.exe utility at c:\Program Files (x86)
\Microsoft SQLServer\100\Tools\Binn or the directory where you installed SQLServer.
2. To copy your SSRS key set to a removable media device and store it in a secure location, open a
command line prompt and run the rskeymgmt.exe utility with the appropriate options.
Disable IE Protected Mode for SSRS
On the VCM Collector, when User Account Control (UAC) is turned on and Internet Explorer Protected
Mode is enabled, SSRS user permissions errors and Web service errors on dashboards and node
summaries can occur. UAC and Internet Explorer Protected Mode also block access to the
http://localhost/reports SSRS administration interfaces. If you use another machine to access the VCM Web
console interface, this problem does not occur.
CAUTION Do not use the VCM Collector Web console interface for general Internet access, because
doing so causes VCM SSRS dashboard errors. If you access the Internet through the VCM Collector
Web console interface, to enable the SSRS dashboards you must either disable Internet Explorer
Protected Mode for the zone of the Collector or run Internet Explorer as administrator.
Do not modify the Internet Explorer Protected Mode setting in other circumstances, because doing
so reduces the protection on the Collector and can increase the exposure of the Collector to attacks
through Internet Explorer.
Procedure
1. In Internet Explorer, click Tools.
2. Click Internet Options and click the Security tab.
3. Click Local intranet and deselect the Enable Protected Mode (requires restarting Internet Explorer)
check box.
4. Click Apply and OK, and close all instances of Internet Explorer.
Configure SSRS
Configure SSRS manually in your installation configuration, because the SSRS command-line configuration
tool does not perform these steps.
54
VMware, Inc.
Single-Tier Server Installation
SSRS might require HTTPS during installation. If HTTPSis required, you manually export a self-signed
certificate and import it to the VCM Collector machine’s root certificate store. If you do not manually
export the certificate, a manual import of a VCM report might fail. If the manual import fails, run the
import from the VCM Collector machine. For more information, see the Microsoft IIS Resource Kit Tools.
Prerequisites
n Back up your SSRS key. See "Back Up Your SSRS Key" on the previous page.
n Disable the Internet Explorer Protected Mode. See "Disable IE Protected Mode for SSRS" on the
previous page.
Procedure
1. On your single server, start SQLServer 2008 R2, 2012, or 2014 Reporting Services Configuration
Manager.
a. Click Start, select Run, and type rsconfigtool.exe.
b. In the Reporting Services Configuration Connection dialog box, click Connect to connect and log in
to SQL Server Reporting Services.
2. Update the SQL Server database.
a. In the navigation pane, click Database and click Change Database.
b. In the Report Server Database Configuration pane, verify that Action is selected.
c. On the Change Database page, select Create a new report server database and click Next.
d. Change the server name of your database server to the database machine and database instance
where SSRS will connect.
e. Verify that the authentication type is set to Current User – Integrated Security and click Test
Connection.
f. When the test message is successful, close the Test Connection dialog box and click Next.
g. On the Database pane, enter a name for the Database.
h. Set the Report Server Mode to Native Mode and click Next.
i. In the Credentials pane, change the Authentication Type to Windows Credentials, specify an
account, and click Next.
Specify an account that has permission to connect from the Web service on the single server to the
database on the single server, and specify the password for the account.
j. In the Summary pane, review the selections and click Next.
k. In the Progress and Finish pane, resolve any errors, and click Finish.
3. Update the encryption keys.
a. In the navigation pane, click Encryption Keys.
b. In the Delete Encrypted Content area, click Delete and accept the prompt to delete all encrypted
data.
VMware, Inc.
c. In the Change area, click Change to replace the encryption key, and click OK.
b. Verify or configure the settings and click Apply to activate the Report Server Web Service URL.
OptionAction
Virtual DirectorySet to ReportServer.
IP AddressSet to All Assigned (Recommended).
TCP PortSet to 80 if you are not using HTTPS.
SSLCertificateNot Selected
c. In the Results area, confirm that the virtual directory is created and that the URL is reserved.
5. Confirm the Report Manager URL.
a. In the navigation pane, click Report Manager URL and click Apply to activate the Report Manager
URL.
b. Verify that the virtual directory was created and that the URL was reserved in the Results area.
c. Click the default URL and verify that it opens SQLServer Reporting Services.
6. Click Exit to close SQLServer 2008 R2, 2012, or 2014 Reporting Services Configuration Manager.
What to do next
To authenticate users and client applications against the report server, configure Basic Authentication on
the report server. See "Configure Kerberos Authentication" on page 57.
Configure Basic Authentication on the Report Server
SQL Server Reporting Services (SSRS) provides several options to authenticate users and client applications
against the report server. When you install VCM in a single-tier split installation and use Basic
authentication, you must allow direct access to the Reports virtual directory.
Update the rsreportserver.config file so that VCM can authenticate users who use the VCM Web
console, and users can launch SSRS reports. To configure Basic authentication on the report server, edit the
XML elements and values in the RSReportServer.config file.
Procedure
1. On the Windows machine where you installed SSRS, stop the SSRS service.
2. Navigate to the rsreportserver.config file.
By default: C:\Program Files\Microsoft SQL Server\{reporting-services-instance}
5. Replace any existing <AuthenticationTypes> parameters with one <RSWindowsBasic/>
parameter.
<Authentication>
<AuthenticationTypes>
<RSWindowsBasic/>
</AuthenticationTypes>
...
</Authentication>
6. Save and close rsreportserver.config.
7. Start the SSRS service.
What to do next
To authenticate VCM reports with Kerberos, see "Configure Kerberos Authentication" below.
Configure Kerberos Authentication
The Kerberos network protocol uses secret-key cryptography to ensure security in your VCM
applications. To authenticate VCM Reports, you must use Basic Authentication with HTTPS or Kerberos
Authentication.
When you configure Kerberos Authentication in your installation, configure it on the database server.
Prerequisites
n Verify that your Windows Server 2008 R2, 2012, or 2012 R2 machine has Active Directory management
tools installed. If the tools are not installed, install them. See Microsoft TechNet online. This
configuration requires an Active Directory domain running at Windows Server 2003 or later domain
functional level.
n If SQL Server Reporting Services is running on a different Windows machine than the VCM Collector in
a single-tier installation, verify that the Application Pool account is a local administrator.
Procedure
1. Log in to your Windows Server 2008 R2, 2012, or 2012 R2 machine as a user who has domain
administrator privileges.
2. Start Active Directory Domain Services and select Active Directory Users and Computers.
3. Verify whether AD accounts exist in your domain for the SQLServer service and the VCM IIS
Application Pool.
4. If the accounts do not exist, create them.
a. Set the database account to be a local administrator on the database server.
b. Make the Application Pool account a local administrator on the VCM Collector in a single-tier
installation.
VMware, Inc.
5. Select the Computers container and locate the Web system.
a. Open the properties for Web system.
b. Click the Delegation tab.
c. Select Trust this computer for delegation to any service.
6. Open IIS manager and set the identity of the CMAppPool application pool to the IISaccount.
7. In Reporting Services Configuration Manager, configure the SQL Server Reporting Services service to
run as the IISApplication Pool account.
8. Change SQL Server to run as the SQLServerDomain account.
a. In Reporting Services Configuration Manager, click Encryption Keys and click Delete to delete
encrypted content.
b. In the navigation pane, click Service Account and enter the app_pool_account account for the
database connection.
9. Open a command prompt to set the service principal names directory property for the Active
Directory service accounts.
a. Click Start, select All Programs > Accessories, right-click Command Prompt, and select Run as
administrator.
b. Type: Setspn -a MSSQLSvc/db_server_name domain\sql_server_account_name and press Enter.
c. Type: Setspn -a MSSQLSvc/db_server_name:1433 domain\sql_server_account_name and press
Enter.
d. Type: Setspn -a MSSQLSvc/db_server_fqdn domain\sql_server_account_name and press Enter.
e. Type: Setspn -a MSSQLSvc/db_server_fqdn:1433 domain\sql_server_account_name and press
Enter.
10. Verify whether SSRSis running on the SQLServer and if it is not running, locate and update the
Report Server configuration file named rsreportserver.config.
a. Locate the AuthenticationTypes XML element.
b. Remove <RSWindowsNTLM/> and <RSWindowsBasic/>.
c. Add <RSWindowsNegotiate/> and <RSWindowsKerberos/>.
The default location for the configuration file is C:\Program Files\Microsoft SQL Server\
{reporting-services-instance}\Reporting
Services\ReportServer\rsreportserver.config.
11. In SQL Server Management Studio, grant the Application Pool user access to the VCM and VCM_Unix
databases, with membership in the VCM__SelectRole_General role in each database.
12. (Optional) If you did not configure the SQL Server Reporting Services service to run as the
IISApplication Pool account before installing VCM, start Internet Explorer as administrator and set the
report settings.
a. Click Start, select All Programs, right-click Internet Explorer and select Run as administrator.
b. Connect to http://localhost/Reports/Pages/Folder.aspx.
c. Click ECM Reports and click the ECM data source to display the properties menu.
d. To use integrated authentication, type the following text into the Connection string text box and
e. Click the back button to return to the ECM Reports view.
13. Select Folder Settings, select Security, select the new SSRS user or group, and click New RoleAssignment.
58
VMware, Inc.
Single-Tier Server Installation
14. Click Browser to allow the VCM SSRS user or group to view folders and reports and subscribe to
reports, and click OK.
15. In Server Manager, set the authentication mode.
a. In the navigation pane, select Roles > Web Server (IIS) and click Add Role Services in the Role
Services area.
b. In the Select Role Services wizard, locate the Security (Installed) section, click Windows
Authentication, and follow the prompts to install the service.
c. In the navigation pane, select Roles > Web Server (IIS).
d. Under server_name, select Sites\Default Web Site\VCM, double-click Authentication, and
verify that Windows Authentication is the only option enabled.
e. Under server_name\Sites\Default Web Site, double-click Authentication, click Windows
Authentication, verify that Windows Authentication is enabled, and click Advanced Settings.
f. Verify that Kernel Mode Authentication is disabled and click OK.
16. In Windows Explorer, update the configuration files.
a. Open the configuration file at
Windows\System32\inetsrv\config\applicationhost.config and locate the
<authentication> section.
b. Verify that Windows authentication is enabled, and if it is not enabled, enable it.
c. Save any changes and close the file.
17. Open a command prompt to set the property for the Active Directory service accounts for the service
principal names directory.
a. Click Start and select All Programs > Accessories.
b. Right-click Command Prompt and select Run as administrator.
c. Type Setspn -a http/web_server_name domain\Application Pool Account Name and press Enter.
d. Type Setspn -a http/web_server_fqdn domain\Application Pool Account Name and press Enter.
18. Open the properties for the SQLServer and Application Pool accounts, click the Delegation tab, and
select Trust this user for delegation to any service.
What to do next
Configure the VCMCollector Components before you install VCM. See "Configure the VCM Collector
Components" on page 59.
Configure the VCM Collector Components
The VCM Collector contains the VCM software application and VCM services. To prepare the VCM
Collector components for VCM installation, configure the required utilities.
In your single-tier installation configuration, configure the Web server and VCM Collector components on
the same machine.
VMware, Inc.
NOTE This procedure is required only if you did not install the complete set of Management Tools and
support components earlier.
n Perform the prerequisite tasks for your installation configuration. See "Single-Tier Server Installation"
on page 35.
n From the VCM Collector, verify that you can access the Microsoft Download Center, Microsoft SQL
Server Feature Pack to download SQLXML 4.0 SP1 in the following procedure. See the online Microsoft
Download Center.
n Verify that you can access the Microsoft Download Center, Microsoft SQL Server Feature Pack to
download and install the Native Client (sqlncli.msi) in the following procedure. See the online
Microsoft Download Center. The SQL Command Line Tools in the SQLServer Feature Pack are
required.
n Install .NET Framework 3.5.1 on the Windows Server 2008 R2, 2012, or 2012 R2 machines where
Package Studio will be installed.
Procedure
1. Download and install SQLXML 4.0 SP1, x64 Package.
2. Download and install SQL Server Command Line Utilities, which includes the SQLCMD utility, x64
Package (SqlCmdLnUtils.msi).
The SQL Command Line Tools in the SQLServer 2008 R2, 2012, or 2014 Feature Pack are required.
3. Download and install the SQL Server Native Client, x64 Package (sqlncli.msi).
The Native Client from the SQL Server Feature Pack is required.
4. Reboot the VCM Collector.
What to do next
Review the DCOMand port requirements, and install VCM. See "Installing VCM" on page125.
60
VMware, Inc.
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.
VCM 5.8 supports 64-bit environments that include 64-bit hardware, the 64-bit Windows Server 2008 R2,
Windows Server 2012, or Windows Server 2012 R2 operating system, and SQL Server 2008 R2, or 2012, or
2014.
CAUTION A two-tier installation configuration uses basic authentication with HTTPS by default. Be
aware of the risks to exposure of sensitive data if you use basic security without HTTPS. Optionally,
you can use Kerberos Authentication.
Figure 9–1. Two-Tier Split Installation
9
VMware, Inc.
You must install SQL Server Reporting Services (SSRS) on either the database server or the combined
VCMCollector and Web server.
The VMware Knowledge Base includes information about sizing your hardware environment for a twotier installation of VCM. See http://kb.vmware.com/kb/2033894.
Configuring a Two-Tier Split Installation Environment
In a two-tier installation environment, you configure the database server first, then configure the
combined VCM Collector and Web server before you install VCM. All machines are physical or virtual
Windows machines.
Your VCM database server and combined Web and VCM Collector server need the following
components.
Datab ase Server ComponentsCombin ed Web an d VCM Co llector Server Co mpon ents
VCM Database ComponentsVCM Web Console
VMware VCM Package Manager for WindowsVCM Collector Components
SSRS 2008 for VCM Reports (Optional if you install
it on the combined Web and VCM Collector)
(Optional) Other ToolsImport/Export Utility
(Optional) SSRS 2008 for VCM Reports
Foundation Checker
VMware VCM Package Manager for Windows
VMware VCM Package Studio
Prerequisites
n Perform the general system prerequisite steps. See "System Prerequisites to Install VCM" on page21.
n Connect the database server machine to the domain.
n Connect the combined VCM Collector and Web server machine to the domain.
n Obtain the installation media for the Enterprise, Standard, or Datacenter edition of SQL Server 2008 R2,
2012, or 2014, or verify access to a file share where the installer resides.
Procedure
1. "Verify that the Installing User is an Administrator" on the facing page
The user who installs Windows Server 2008 R2, 2012, or 2012 R2 operating system must be an
Administrator and a domain account.
2. "Install and Configure Windows Server Operating System" on the facing page
Install the Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2 operating
system on each Windows machine that serves as a tier in your configuration.
3. "Configuring the VCM Database Server" on page65
To ensure that the installation creates the VCM databases, you must configure the VCM database
server before you install VCM. In a two-tier split installation configuration, the VCM database server
resides on a separate machine. The databases include VCM, VCM_Coll, VCM_Raw, and VCM_UNIX.
4. "Configure the Combined VCM Collector and Web Server" on page74
In a two-tier split installation configuration, the VCM Collector and the Web server components reside
together on a dedicated Windows Server 2008 R2, 2012, or 2012 R2 machine, and the VCM database
server resides on a separate Windows Server 2008 R2, 2012, or 2012 R2 machine.
5. "Configure the Web Components" on page75
The combined VCM Collector and Web server contains Web applications such as IIS and SQL Server
Reporting Services (SSRS), other services, and VCM software components. Before you install VCM,
62
VMware, Inc.
6. "Configure the VCM Collector Components" on page88
The combined VCM Collector and Web server contains the VCM software application and VCM
services. To prepare the VCM Collector components of the combined VCM Collector and Web server
for VCM installation, configure the required utilities.
What to do next
Review the DCOMand port requirements, and use VCM Installation Manager to install the VCM
components. See "Installing VCM" on page 125.
Verify that the Installing User is an Administrator
The user who installs Windows Server 2008 R2, 2012, or 2012 R2 operating system must be an
Administrator and a domain account.
Procedure
1. Verify that the user is an Administrator.
a. Click Start and select All Programs > Administrative Tools > Computer Management.
b. Expand System Tools, expand Local Users and Groups, and click Users.
c. Right-click the user and click Properties.
Two-Tier Split Installation
d. Click the Member Of tab and verify that Administrators is listed.
e. If Administrators is not listed, add the user to the Administrators group.
f. Click Check Names and click OK.
2. Verify that the user is a domain account.
a. Click Groups.
b. Right-click Administrators and click Properties.
c. Verify that the Domain User is listed in the Members area.
What to do next
Prepare your Windows machine for VCM installation. See "Install and Configure Windows Server
Operating System" below.
Install and Configure Windows Server Operating System
Install the Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2 operating system
on each Windows machine that serves as a tier in your configuration.
Prerequisites
n Determine whether you require Windows Server 2008 R2, 2012, or 2012 R2 operating system. See
"Sizing Impact on Software Edition Requirements" on page 17.
VMware, Inc.
n The user who installs Windows Server 2008 R2, 2012, or 2012 R2 operating system must be an
Administrator and a domain account. See "Verify that the Installing User is an Administrator" on page
63.
n Decide on a valid DNS computer name with no underscores for use when the Windows installation
prompts for a machine name. If you attempt to change the machine name after a machine is identified
as a Collector, problems might occur with VCM, SQL Server, and SQL Server Reporting Services.
1. Install Microsoft Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2 on your
Windows machine.
2. During the installation, you can configure several options.
OptionDescription
Regional and
Language
Determines how numbers, dates, currencies, and time settings appear.
n Language: Setting for your language. The default is English.
Options
n Time and currency format: Determines how numbers, dates, currencies, and time
settings appear. The default is English (United States).
n Keyboard or input method: Allows text entry for multiple languages. The default
is US.
Disk
Configuration
Allows you to separate the machine disk drive into partitions to store data in
different partitions. You can create new disk partitions and delete existing partitions.
After you configure the disk, select a partition on which to install Windows Server
2008 R2, 2012, or 2012 R2 Edition.
Product KeyWhen the installation prompts, enter your product key.
Licensing
Modes
Administrator
Password
Windows Server 2008 R2, 2012, or 2012 R2 supports a single license that is included
with the product key.
The installation setup creates an account called administrator. To log in, you must
create a password that complies with the criteria. The password must have the
following attributes.
n Minimum of six characters
n Does not contain “administrator” or “admin”
n Contains uppercase letters
n Contains lower case letters
n Contains numbers
n Contains at least one non-alphanumeric character
3. Perform the initial configuration tasks to set the time zone and the computer name.
Disable the Remote Desktop Session Host
A Remote Desktop Session Host server hosts Windows-based programs for Remote Desktop Services
clients.
If the Remote Desktop Session Host role service is enabled, you must disable it to avoid changes to
settings for new connections, modifications of existing connections, or removal of connections.
64
VMware, Inc.
Two-Tier Split Installation
Procedure
1. Click Start and select All Programs > Administrative Tools > Server Manager.
2. In the navigation pane, expand Roles and click Remote Desktop Services.
3. In the Remote Desktop Services pane, scroll down to Role Services.
4. Click the Remote Desktop Session Host role service to highlight it.
5. Click Remove Role Services.
6. Deselect the Remote Desktop Session Host role service and follow the prompts to finish disabling the
Remote Desktop Session host role.
Enable DCOM
The Distributed Component Object Model (DCOM) protocol allows application components to interact
across Windows machines. DCOM must be enabled on the Windows machine to install and run VCM.
Although DCOMis enabled by default when Windows Server 2008 R2, 2012, or 2012 R2 is installed,
DCOMmight have been disabled by a custom installation or a lock-down script.
Procedure
1. Click Start and select All Programs > Administrative Tools > Component Services to open
Component Services.
2. In the Component Services navigation pane, expand Component Services and expand Computers.
3. Right-click the computer and click Properties.
4. Click the Default Properties tab.
5. Select Enable Distributed COM on this computer and click OK.
What to do next
Configure the database server. See "Configuring the VCM Database Server" below.
Configuring the VCM Database Server
To ensure that the installation creates the VCM databases, you must configure the VCM database server
before you install VCM. In a two-tier split installation configuration, the VCM database server resides on a
separate machine. The databases include VCM, VCM_Coll, VCM_Raw, and VCM_UNIX.
Use of a shared SQL Server is supported for VCM. However, VCM makes heavy use of SQL Server for
query and transaction processing. You must ensure that you have or can add enough capacity to a shared
SQL Server so that VCM and any other databases on the shared server do not experience poor
performance.
The SQL Server license includes SQL Server Reporting Services (SSRS). In your two-tier split installation
configuration, when you run SSRS and SQL Server on the same machine, the SQL Server database
machine can take on the role of the Report Server (SSRS).
VCM 5.8 supports running SSRS on the Web server or on the database server in a split installation.
Depending on the separation of services in your environment, you might want to install SSRS on the Web
server machine in a split installation, because SSRS has its own Web server.
VMware, Inc.
If you install SSRS on the Web server, it requires an additional SQL Server license, because you are
installing SSRS on a Windows Server 2008 R2, 2012, or 2012 R2 machine that is separate from the SQL
Server database services. If you run SQL Server Enterprise Edition, all SQL Server services running in
guests on a single virtual machine host are covered by the Enterprise Edition license.
VCM operates with a Standard, Enterprise, or Datacenter edition of SQL Server. You must install the 64-bit
SQL Server 2008 R2, or 2012, or 2014 version on your designated database server machine and verify that
the settings are configured correctly for a VCM installation.
If you plan to change the communication port that SQL Server uses from the default port of 1433 to a
nonstandard port number, make the changes during the installation of SQL Server and SQL Server
Reporting Services (SSRS). Changing the port after you install SSRS disables SSRS communication with
SQL Server, which causes an SSRS validation error during the VCM installation process. If you change the
port after installation, you must configure additional SSRS settings to repair the configuration.
Disable the Firewall or Add an Exception for SQL Server Port 1433
On the machine that is running SQL Server, to access SQLServer through a firewall, you must configure
the firewall or add an exception for port 1433. Port 1433 is the SQL Server default instance running over
TCP.
Procedure
1. To turn off the Windows domain firewall, follow these steps.
a. Click Start and select Control Panel.
b. Click System and Security.
c. Click Windows Firewall.
d. Click Turn Windows Firewall on or off.
e. Under Domain network location settings, click Turn off Windows Firewall.
2. To add an exception for SQL port 1433, follow these steps.
a. In Windows Firewall in the Control Panel, click Advanced Settings to open the Windows Firewall
with Advanced Security dialog box.
b. Click Inbound Rules and click New Rule.
c. Click Port and Next.
d. Click TCP, click Specific local ports, type 1433, and click Next.
e. Click Allow the connection and click Next.
f. Click Domain, uncheck Private, uncheck Public, and click Next.
g. Type a name for the rule and click Finish.
Install SQL Server on the Database Server
In a two-tier split installation configuration, the VCM database server resides on a separate machine. The
database server contains the VCM, VCM_Coll, VCM_Raw, and VCM_UNIX databases. You must
configure the VCM database server before you install VCM in a two-tier split installation configuration.
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.
Prerequisites
n Obtain the installation media for the Enterprise, Standard, or Datacenter edition of SQL Server 2008 R2,
2012, or 2014, or verify access to a file share where the installer resides.
66
VMware, Inc.
Procedure
1. Start the SQLServer installation.
2. Perform the following actions to install SQL Server.
For SQL Server 2008 R2
Wizard PageAction
Two-Tier Split Installation
SQL Server
Click New installation or add features to an existing installation.
Installation
Center
Setup Support
Rules
Setup Support
Click Install and verify that all of the rules pass. To view the detailed system
configuration check report, click the link.
Click Install to install the setup support files.
Files
Setup Support
Verify that all of the rules passed.
Rules – for
SQL Server
Setup support
files
Installation
Select New installation or add shared features.
Type
Product KeyVerify that the product key is entered.
License Terms Accept the license terms.
Setup RoleSelect SQL Server Feature Installation.
Feature
Selection
Select the following features.
Instance Features:
Installation
Rules
Instance
Configuration
Disk Space
Requirements
n Database Engine Services
Shared Features:
n Client Tools Connectivity
n SQL Server Books online
n Management Tools - Basic
and Management Tools - Complete
Verify that the rules passed. To view the detailed system configuration check
report, click the link.
Select Default Instance. If an instance of SQL Server is not installed, the installation
creates a default instance. If an instance of SQLServer is already installed, select
Install Setup FilesVerify that all rules are passed.
Setup RoleSelect SQL Server Feature Installation.
Feature SelectionSelect the following features.
Instance Features:
n Database Engine Services
Shared Features:
n Client Tools Connectivity
n Management Tools - Basic
and Management Tools - Complete
Instance
Configuration
Select Default Instance. If an instance of SQL Server is not installed, the
installation creates a default instance. If an instance of SQLServer is already
installed, select Named Instance and assign a name.
Server
Configuration
Browse the accounts for all SQL services and enter the NT
AUTHORITY\SYSTEM account.
It is possible to use a domain account for SQL Server services. A domain
account might be required for split installations, because the SQL Server
Agent might need access to the Collector for some activities. If you use a
domain account, you should use a local administrator on the SQL Server
machine to access DBServices. Otherwise, you must grant manual
permissions.
Database Engine
Configuration
Select Windows authentication and click Add Current User to add the
account to the SQL Server administrators.
Ready to InstallReview the summary of features and click Install to install SQL Server. When
the installation is finished, click the link to view the log file.
What to do next
n Reboot the database server machine.
Verify and Configure the SQL Server Properties
To ensure that SQLServer will operate with VCM, verify the SQLServer property settings and set the
server-wide SQL database settings in preparation to install VCM. For information about server-wide and
database-specific SQL Server database settings, see the VCM Administration Guide.
Procedure
1. Launch SQL Server Management Studio.
2. Right-click the SQL instance and select Properties.
3. Confirm the General page server property of Version as 10.50.1600.1 or some later build of version
10.50.
4. Select and confirm the Security page server properties.
70
VMware, Inc.
Two-Tier Split Installation
a. Select Windows Authentication mode, which is recommended.
b. Although SQL Server and Windows Authentication mode is acceptable for VCM, select Windows
Authentication mode, which is recommended.
5. Select and confirm the Database Settings page server properties.
a. For Default index fill factor, type or select a percentage value, which specifies the amount of free
space in each index page when the page is rebuilt.
Set the fill factor to 80% to keep 20% free space available in each index page.
b. For Recovery interval (minutes), type or select 5.
6. Click OK to save your changes.
What to do next
To ensure that SQLServer and VCMoperate correctly together, verify that the SQLServer name matches
the Windows machine name. See "Verify Matching SQL Server and Computer Names" below.
Verify Matching SQL Server and Computer Names
To ensure that SQLServer and VCM operate correctly together, you must verify that the SQLServer
name matches the Windows machine name. If you recently installed SQL Server, you do not need to
verify that the names match. If you obtained a machine that was renamed after the operating system and
SQL Server were installed, verify and reset the SQLServer server name.
Procedure
1. Launch SQL Server Management Studio.
2. Click Database Engine Query.
3. In the SQL Query pane, type SELECT @@Servername and click Execute.
4. Verify that the resulting SQL Server name matches the Windows machine name.
5. If the SQL Server name does not match the Windows machine name, reset the SQL Server name.
a. In the SQL Query pane, type the following command and replace NewServerName with the server
Verify the SQLServer Agent Service Account is a sysadmin
The SQL Server Agent service account that runs scheduled jobs in SQL Server must be a sysadmin.
Open SQLServer Management Studio and verify that the account you will use for the SQL Server Agent
service account has the sysadmin privilege.
Procedure
1. Launch SQL Server Management Studio.
2. Expand the server, expand Security, expand Server Roles.
3. Double-click sysadmin and view the members of the sysadmin role.
4. Verify that the account to use for the SQL Server Agent service is a member of the sysadmin fixed
role.
5. If the account is not a member of the sysadmin fixed role, add this role to the account.
What to do next
Verify that the SQL Server Agent service is configured to start automatically. See "Verify that the
SQLServer Agent Service Starts Automatically" below.
Verify that the SQLServer Agent Service Starts Automatically
VCM uses the SQL Server Agent service to run all scheduled jobs and SSRS reports, including dashboards.
Set the service to automatically start on the VCM server where SQL Server is installed.
Procedure
1. On the VCM database server, click Start and select Administrative Tools > Services.
2. Right-click SQL Server Agent, and select Properties.
3. From the Startup type menu, select Automatic.
4. Click OK, and close the Services window.
What to do next
Select the SQL Server Agent service account See "Select the SQLServer Agent Service Account" below.
Select the SQLServer Agent Service Account
SQL Server Agent is a service that runs scheduled jobs in SQLServer and runs as a specific user account.
Verify that the SQL Server Agent service account that you provided during the SQL Server installation is a
SQL Server sysadmin. The SQL Server Agent runs as a user account.
Prerequisites
n Verify that the account you provide for the SQL Server Agent service has permission to log in as a
service and the required additional permissions. See the online Microsoft Developer Network for more
information.
n Understand the supported service account types for non-clustered and clustered servers. VCM 5.8
supports Active/Active SQL clusters. See the online Microsoft Developer Network for more
information.
n Verify that the account you will use for the SQL Server Agent service account has the sysadmin
privilege. See "Verify the SQLServer Agent Service Account is a sysadmin" on page 72.
72
VMware, Inc.
Two-Tier Split Installation
Procedure
1. On the VCMdatabase server machine, click Start and select All Programs.
2. Click Microsoft SQL Server {version} > Configuration Tools > SQL Server ConfigurationManager.
3. Click SQL Server Services.
4. Right-click SQL Server Agent (MSSQLSERVER) and click Properties.
5. On the Log On tab, select a log in option and provide the account information.
OptionDescription
Built-in accountIn a single-tier installation, you can select the Local System account,
which has unrestricted access to all system resources. In a split
installation environment, do not select the built-in Local System
account. This account is a member of the Windows Administrators
group on the local machine.
This accountIn a split installation, the SQLServer Agent must be running as a user
account. Select a Windows domain account for the SQL Server Agent
service account.
This option provides increased security. Select this option for jobs that
require application resources across a network, to forward events to
other Windows application logs, or to notify administrators through
email or pagers.
6. Type or select an account name that has the sysadmin privilege.
7. Click OK.
What to do next
Establish SQLServer administration rights. See "Establish SQL Server Administration Rights" below.
Establish SQL Server Administration Rights
Members of the SQLServer sysadmin fixed server role can perform any activity in the server. The user
who installs VCM must have SQL Server sysadmin rights.
Procedure
1. Launch SQL Server Management Studio.
2. Expand the server instance, select Security and select Logins.
3. Right-click the login ID of the user who installs VCM and select Properties.
4. In the Select a page area, select Server Roles.
5. In the Server roles area, select the sysadmin check box.
6. Click OK to save the settings and close the window.
What to do next
Configure the combined VCM Collector and Web server. See "Configure the Combined VCM Collector
Configure the Combined VCM Collector and Web Server
In a two-tier split installation configuration, the VCM Collector and the Web server components reside
together on a dedicated Windows Server 2008 R2, 2012, or 2012 R2 machine, and the VCM database server
resides on a separate Windows Server 2008 R2, 2012, or 2012 R2 machine.
To configure the combined VCM Collector and Web server for a two-tier installation, verify the SQLXML
version, configure IIS, install and configure SSRS, then configure the VCM Collector components.
Install the .NET Framework
To support library and language interoperability, the VCMCollector must have the required versions of
the .NET Framework installed.
VCM 5.8 requires the .NET 3.5.1 Framework. If you use Package Studio, the VCM Collector must have
.NET 3.5.1 installed. If you use Package Manager, the VCM Collector must have .NET 3.5.1 or .NET 4.0
installed.
Determine the installed version of the .NET Framework. If one of the .NET Framework versions is
missing, install the version from the Microsoft download Web site.
Procedure
1. Click Start and select All Programs > Administrative Tools > Server Manager.
2. Click Features.
3. Verify that .NET Framework 3.5.1 appears in the feature summary.
4. If .NET Framework 3.5.1 does not appear, under Features select Add Features and select .NET 3.5.1.
Verify the ASP.NET Client System Web Version
To support client programming, verify the ASP.NET Client System Web version to confirm that the .NET
framework is installed correctly, and install it if the version is not correct.
1. Click Start and select All Programs > Administrative Tools > Internet Information Services (IIS)Manager.
2. Expand <server name> and click Sites.
3. Expand Default Web Site, expand aspnet_client, and expand system_web.
4. Verify that the version is 2_0_50727.
Verify the ASPRole Service
To support client programming, verify the status of the ASP Role Service to confirm that the .NET
framework is installed correctly.
Procedure
1. Click Start and select All Programs > Administrative Tools > Server Manager.
2. Expand Server Manager (<server name>) and expand Roles.
3. Click Web Server (IIS).
4. Scroll down to Role Services.
5. Locate ASP and verify whether the role service is installed.
6. If the role service is not installed, click Add Role Services and add the ASP role service.
74
VMware, Inc.
Two-Tier Split Installation
Verify ASP.NETRole Service
To support client programming, verify the status of the ASP.NET Role Service to confirm that the .NET
framework is installed correctly.
Procedure
1. Click Start and select All Programs > Administrative Tools > Server Manager.
2. Expand Server Manager (<server name>) and expand Roles.
3. Click Web Server (IIS).
4. Scroll down to Role Services.
5. Locate ASP.NET and verify that the role service is installed.
6. If the role service is not installed, click Add Role Services and add the ASP.NET role service.
What to do next
Configure the Web components for the combined VCM Collector and Web server. See "Configure the
Web Components" below.
Configure the Web Components
The combined VCM Collector and Web server contains Web applications such as IIS and SQL Server
Reporting Services (SSRS), other services, and VCM software components. Before you install VCM, you
must configure the combined VCM Collector and Web server.
The Windows machine that hosts the Web components must be running Internet Information Services
(IIS) 7.5. IIS is installed when you install Windows Server 2008 R2, 2012, or 2012 R2.
For a two-tier installation, the Web server components reside on the same machine as the VCM Collector.
The SQL Server license includes SQL Server Reporting Services (SSRS). In your two-tier split installation
configuration, when you run SSRS and SQL Server on the same machine, the SQL Server database
machine can take on the role of the Report Server (SSRS).
VCM 5.8 supports running SSRS on the Web server or on the database server in a split installation.
Depending on the separation of services in your environment, you might want to install SSRS on the Web
server machine in a split installation, because SSRS has its own Web server.
If you install SSRS on the Web server, it requires an additional SQL Server license, because you are
installing SSRS on a Windows Server 2008 R2, 2012, or 2012 R2 machine that is separate from the SQL
Server database services. If you run SQL Server Enterprise Edition, all SQL Server services running in
guests on a single virtual machine host are covered by the Enterprise Edition license.
Prerequisites
n Perform the prerequisite tasks for your two-tier split installation configuration. See "Two-Tier Split
Installation" on page 61.
n Place the Web server in the Internet Explorer Trusted Zone so that Internet Explorer can delegate the
VCM user's credentials to the Web service for use with SQL Server. See "Place the Web Server in the
Internet Explorer Trusted Zone" on page 107.
n If the domain firewall is turned on, verify that any required ports are open. If the database server is
blocked from communicating with the Collector, problems can occur when you submit jobs. VCM
displays an error about the SAS service, and the VCM Debug Event Log displays failures when calling
ecm_sp_collector_control.
n Verify that .NET Framework 3.5.1 is installed on Windows Server 2008 R2, 2012, or 2012 R2 machines
where Package Studio will be installed.
n Verify that you have an Internet connection to check for patch bulletin updates.
n On the Windows Server 2008 R2, 2012, or 2012 R2 Web server machine, verify that the following .NET
Framework components are installed.
n Windows Process Activation Service
n Process Model
n .NETEnvironment
n Configuration APIs
Procedure
1. Restart the Web server machine.
2. Click Start and select All Programs > Administrative Tools > Server Manager.
3. Click Roles and verify that the Web Server (IIS) role appears.
4. If the Web Server (IIS) role does not appear, in the Roles Summary area, click Add Roles and add the
Web Server (IIS) role.
5. On the Select Server Roles page, select Web Server (IIS) and select the Web Server components to
add.
OptionAction
Common HTTPFeaturesSelect these options:
n Static Content
n Default Document
n Directory Browsing
n HTTP Errors
Application DevelopmentSelect these options:
n ASP .NET
n .Net Extensibility
n ASP
n ISAPI Extensions
n ISAPI Filters
n Server Side Includes
Health and DiagnosticsSelect these options:
n HTTP Logging
n Request Monitor
SecuritySelect these options:
n Basic Authentication
n Request Filtering
76
VMware, Inc.
Two-Tier Split Installation
OptionAction
PerformanceSelect:
n Static Content Compression
Configuring IIS
To ensure that the Web components are correctly configured, verify that the correct role services are
enabled, the bindings are set correctly, and the default Web site is correct.
Verify the IIS 7.5 Role Services are Enabled
Verify that the correct IIS 7.5 Role Services are enabled on the combined VCM Collector and Web server .
Procedure
1. On the Collector, click Start and select All Programs > Administrative Tools > Server Manager.
2. Expand Roles and click Web Server (IIS).
3. If the Web Server (IIS) role does not appear in the list of Roles, scroll to Role Services, click Add Role
Services and add the Web Server (IIS) Role.
When you installed IIS, the ASP Role Service, ASP.NET Role Service, and IIS ServerSideIncludes Role
Service were installed.
4. In the Web Server (IIS) pane, scroll to Role Services and verify that the status is set to Installed for the
following Role Services.
5. If any of the Role Services are not installed, click Add Role Services, select the check boxes of the
services to install, and click Install.
Configure the IIS 7.5 Settings
IIS settings configure the information required for requests to communicate with a Web site. To support
VCMinteraction with IIS, configure the settings for the IIS 7.5 bindings on the combined VCMCollector
and Web server to ensure that the settings are correct.
Procedure
1. Click Start and select All Programs > Administrative Tools > Internet Information Services (IIS)
Manager.
Dynamic Content Compression
IIS Management Scripts and Tools
Management Service
2. Expand <server name>, expand Sites, and click Default Web Site.
3. In the Actions pane, under Edit Site, click Bindings.
4. Click Add to open the Site Bindings dialog box.
a. In the Type menu, select http.
b. In the IPaddress menu, select All Unassigned.
c. In the Port text box, type 80.
5. In the Site Bindings dialog box, click Close.
6. In the Actions pane, under Manage Web Site and Browse Web Site, click Advanced Settings.
7. Expand Connection Limits and set Connection Time-out (seconds) to 3600.
8. Click OK.
Verify the IIS 7.5 Default Web Site
IIS 7.5 provides a default Web site that defines the default authentication settings for applications and
virtual directories. Verify that the IIS 7.5 default Web site has the correct settings.
Procedure
1. Click Start and select All Programs > Administrative Tools > Internet Information Services (IIS)
Manager.
2. Expand <server name>, expand Sites, and click Default Web Site.
3. In the Default Web Site Home pane, locate the IIS options.
4. Double-click Authentication and set the authentication.
OptionAction
Anonymous Authentication Set to Disabled.
78
VMware, Inc.
Two-Tier Split Installation
OptionAction
ASP.NET ImpersonationSet to Disabled.
Basic AuthenticationSet to Enabled.
Forms AuthenticationSet to Disabled.
Verify the ISAPI Extensions
The ISAPI Extensions role provides support for dynamic Web content development. You must verify that
the role service is installed, and install it if needed.
Procedure
1. Click Start and select All Programs > Administrative Tools > Server Manager.
2. Expand Server Manager (<server name>) and expand Roles.
3. Click Web Server (IIS).
4. Scroll to Role Services.
5. Locate ISAPI Extensions and verify that the role service is installed.
6. If the role service is not installed, click Add Role Services and add the ISAPI Extensions role service.
What to do next
Prepare SQL Server Reporting Services (SSRS) to generate VCM reports. See "Installing and Configuring
SSRS on the Combined VCM Collector and Web Server" below.
Installing and Configuring SSRS on the Combined VCM Collector and Web
Server
SQL Server Reporting Services (SSRS) is a server-based report generation software system that is
administered using a web interface and used to deliver VCM reports.
Back Up Your SSRS Key
The rskeymgmt utility manages the symmetric keys used by a report server. This utility provides a way to
delete encrypted content that can no longer be used if you cannot recover or apply the key.
Use the Microsoft command-line utility to back up the symmetric key to an encrypted file.
Prerequisites
n See the online Microsoft Support center for details about how to use the rskeymgmt utility.
Procedure
1. On the Collector file system, locate the rskeymgmt.exe utility at c:\Program Files (x86)
\Microsoft SQLServer\100\Tools\Binn or the directory where you installed SQLServer.
2. To copy your SSRS key set to a removable media device and store it in a secure location, open a
command line prompt and run the rskeymgmt.exe utility with the appropriate options.
VMware, Inc.
Install SQL Server Reporting Services
In a two-tier installation configuration, for the Web server to generate VCM reports, install SQL Server
Reporting Services (SSRS).
Verify that the rules passed. To view the detailed system configuration check
report, click the link.
Select Default Instance. If an instance of SQL Server is not installed, the installation
creates a default instance. If an instance of SQLServer is already installed, select
Named Instance and assign a name.
Review the disk usage summary.
Browse the accounts for all SQL services and enter the NT AUTHORITY\SYSTEM
account.
It is possible to use a domain account for SQL Server services. A domain account
might be required for split installations, because the SQL Server Agent might need
access to the Collector for some activities. If you use a domain account, you should
use a local administrator on the SQL Server machine to access DBServices.
Otherwise, you must grant manual permissions.
Reporting
Specify the reporting services configuration mode.
Services
Configuration
Error
Review the summary information.
Reporting
Installation
Configuration
Verify that the rules passed. To view the detailed system configuration check
report, click the link.
Rules
Ready to
Install
Review the summary of features and click Install to install SQL Server. When the
installation is finished, click the link to view the log file.
For SSRS 2014
Wizard PageAction
SQL Server
Installation Center
Click New SQL Server stand-alone installation or add features to anexisting installation.
Product KeyVerify that the product key is entered.
License TermsAccept the license terms.
82
VMware, Inc.
Wizard PageAction
Microsoft UpdateUse this option to check for Microsoft updates.
Install Setup FilesVerify that all rules are passed.
Setup RoleSelect SQL Server Feature Installation.
Feature SelectionSelect the following features.
Instance Features:
n Reporting Services
Shared Features:
n Client Tools Connectivity
n Management Tools - Basic
and Management Tools - Complete
Two-Tier Split Installation
Instance
Configuration
Select Default Instance. If an instance of SQL Server is not installed, the
installation creates a default instance. If an instance of SQLServer is already
installed, select Named Instance and assign a name.
Server
Configuration
Browse the accounts for all SQL services and enter the NT
AUTHORITY\SYSTEM account.
It is possible to use a domain account for SQL Server services. A domain
account might be required for split installations, because the SQL Server
Agent might need access to the Collector for some activities. If you use a
domain account, you should use a local administrator on the SQL Server
machine to access DBServices. Otherwise, you must grant manual
permissions.
Reporting Services
Specify the reporting services configuration mode.
Configuration
Ready to InstallReview the summary of features and click Install to install SQL Server. When
the installation is finished, click the link to view the log file.
Configure SSRS
Configure SSRS manually in your installation configuration, because the SSRS command-line configuration
tool does not perform these steps.
SSRS might require HTTPS during installation. If HTTPSis required, you manually export a self-signed
certificate and import it to the VCMCollector machine’s root certificate store. If you do not manually
export the certificate, a manual import of a VCM report might fail. If the manual import fails, run the
import from the VCM Collector machine. For more information, see the Microsoft IIS Resource Kit Tools.
VMware, Inc.
Prerequisites
n Back up your SSRS key. See "Back Up Your SSRS Key" on page79.
1. On your combined VCMCollector and Web server, start SQLServer 2008 R2, 2012, or 2014 Reporting
Services Configuration Manager.
a. Click Start, select Run, and type rsconfigtool.exe.
b. In the Reporting Services Configuration Connection dialog box, click Connect to connect and log in
to SQL Server Reporting Services.
2. Update the SQL Server database.
a. In the navigation pane, click Database and click Change Database.
b. In the Report Server Database Configuration pane, verify that Action is selected.
c. On the Change Database page, select Create a new report server database and click Next.
d. Change the server name of your database server to the database machine and database instance
where SSRS will connect.
e. Verify that the authentication type is set to Current User – Integrated Security and click Test
Connection.
f. When the test message is successful, close the Test Connection dialog box and click Next.
g. On the Database pane, enter a name for the Database.
h. Set the Report Server Mode to Native Mode and click Next.
i. In the Credentials pane, change the Authentication Type to Windows Credentials, specify an
account, and click Next.
Specify an account that has permission to connect from the combined VCMCollector and Web
server to the database server, and specify the password for the account.
j. In the Summary pane, review the selections and click Next.
k. In the Progress and Finish pane, resolve any errors, and click Finish.
3. Update the encryption keys.
a. In the navigation pane, click Encryption Keys.
b. In the Delete Encrypted Content area, click Delete and accept the prompt to delete all encrypted
data.
c. In the Change area, click Change to replace the encryption key, and click OK.
4. Configure the Web Service URL.
a. In the navigation pane, click Web Service URL.
b. Verify or configure the settings and click Apply to activate the Report Server Web Service URL.
OptionAction
Virtual DirectorySet to ReportServer.
IP AddressSet to All Assigned (Recommended).
TCP PortSet to 80 if you are not using HTTPS.
SSLCertificateNot Selected
c. In the Results area, confirm that the virtual directory is created and that the URL is reserved.
84
VMware, Inc.
Two-Tier Split Installation
5. Confirm the Report Manager URL.
a. In the navigation pane, click Report Manager URL and click Apply to activate the Report Manager
URL.
b. Verify that the virtual directory was created and that the URL was reserved in the Results area.
c. Click the default URL and verify that it opens SQLServer Reporting Services.
6. Click Exit to close SQLServer 2008 R2, 2012, or 2014 Reporting Services Configuration Manager.
What to do next
To authenticate users and client applications against the report server, configure Basic Authentication on
the report server. See "Configure Basic Authentication on the Report Server for Multi-Tier Installations" on
page 85.
Configure Basic Authentication on the Report Server for Multi-Tier Installations
SQL Server Reporting Services (SSRS) provides several options to authenticate users and client applications
against the report server. When you install VCM in a two-tier split installation and use Basic
authentication, you must allow direct access to the Reports virtual directory.
Update the rsreportserver.config file so that VCM can authenticate users who use the VCM Web
console, and users can launch SSRS reports. To configure Basic authentication on the report server, edit the
XML elements and values in the RSReportServer.config file.
Procedure
1. On the Windows machine where you installed SSRS, stop the SSRS service.
2. Navigate to the rsreportserver.config file.
By default: C:\Program Files\Microsoft SQL Server\{reporting-services-instance}
To authenticate VCM reports with Kerberos, see "Configure Kerberos Authentication" below.
Configure Kerberos Authentication
The Kerberos network protocol uses secret-key cryptography to ensure security in your VCM
applications. To authenticate VCM Reports, you must use Basic Authentication with HTTPS or Kerberos
Authentication.
When you configure Kerberos Authentication in your two-tier split installation, configure it on the
database server and the combined VCMCollector and Web server.
Prerequisites
n Verify that your Windows Server 2008 R2, 2012, or 2012 R2 machine has Active Directory management
tools installed. If the tools are not installed, install them. See Microsoft TechNet online. This
configuration requires an Active Directory domain running at Windows Server 2003 or later domain
functional level.
n If SQL Server Reporting Services is running on a different Windows machine than the VCM Collector in
a two-tier installation, verify that the Application Pool account is a local administrator.
Procedure
1. Log in to your Windows Server 2008 R2, 2012, or 2012 R2 machine as a user who has domain
administrator privileges.
2. Start Active Directory Domain Services and select Active Directory Users and Computers.
3. Verify whether AD accounts exist in your domain for the SQLServer service and the VCM IIS
Application Pool.
4. If the accounts do not exist, create them.
a. Set the database account to be a local administrator on the database server.
b. Make the Application Pool account a local administrator on the VCM Collector in a two-tier
installation.
5. Select the Computers container and locate the Web system.
a. Open the properties for Web system.
b. Click the Delegation tab.
c. Select Trust this computer for delegation to any service.
6. Open IIS manager and set the identity of the CMAppPool application pool to the IISaccount.
7. In Reporting Services Configuration Manager, configure the SQL Server Reporting Services service to
run as the IISApplication Pool account.
8. Change SQL Server to run as the SQLServerDomain account.
a. In Reporting Services Configuration Manager, click Encryption Keys and click Delete to delete
encrypted content.
b. In the navigation pane, click Service Account and enter the app_pool_account account for the
database connection.
9. Open a command prompt to set the service principal names directory property for the Active
Directory service accounts.
86
VMware, Inc.
Two-Tier Split Installation
a. Click Start, select All Programs > Accessories, right-click Command Prompt, and select Run as
administrator.
b. Type: Setspn -a MSSQLSvc/db_server_name domain\sql_server_account_name and press Enter.
c. Type: Setspn -a MSSQLSvc/db_server_name:1433 domain\sql_server_account_name and press
Enter.
d. Type: Setspn -a MSSQLSvc/db_server_fqdn domain\sql_server_account_name and press Enter.
e. Type: Setspn -a MSSQLSvc/db_server_fqdn:1433 domain\sql_server_account_name and press
Enter.
10. Verify whether SSRSis running on the SQLServer and if it is not running, locate and update the
Report Server configuration file named rsreportserver.config.
a. Locate the AuthenticationTypes XML element.
b. Remove <RSWindowsNTLM/> and <RSWindowsBasic/>.
c. Add <RSWindowsNegotiate/> and <RSWindowsKerberos/>.
The default location for the configuration file is C:\Program Files\Microsoft SQL Server\
{reporting-services-instance}\Reporting
Services\ReportServer\rsreportserver.config.
11. In SQL Server Management Studio, grant the Application Pool user access to the VCM and VCM_Unix
databases, with membership in the VCM__SelectRole_General role in each database.
12. (Optional) If you did not configure the SQL Server Reporting Services service to run as the
IISApplication Pool account before installing VCM, start Internet Explorer as administrator and set the
report settings.
a. Click Start, select All Programs, right-click Internet Explorer and select Run as administrator.
b. Connect to http://localhost/Reports/Pages/Folder.aspx.
c. Click ECM Reports and click the ECM data source to display the properties menu.
d. To use integrated authentication, type the following text into the Connection string text box and
verify that Windows Authentication is the only option enabled.
e. Under server_name\Sites\Default Web Site, double-click Authentication, click Windows
Authentication, verify that Windows Authentication is enabled, and click Advanced Settings.
f. Verify that Kernel Mode Authentication is disabled and click OK.
16. In Windows Explorer, update the configuration files.
a. Open the configuration file at
Windows\System32\inetsrv\config\applicationhost.config and locate the
<authentication> section.
b. Verify that Windows authentication is enabled, and if it is not enabled, enable it.
c. Save any changes and close the file.
17. Open a command prompt to set the property for the Active Directory service accounts for the service
principal names directory.
a. Click Start and select All Programs > Accessories.
b. Right-click Command Prompt and select Run as administrator.
c. Type Setspn -a http/web_server_name domain\Application Pool Account Name and press Enter.
d. Type Setspn -a http/web_server_fqdn domain\Application Pool Account Name and press Enter.
18. Open the properties for the SQLServer and Application Pool accounts, click the Delegation tab, and
select Trust this user for delegation to any service.
What to do next
Configure the VCM Collector components of the combined VCM Collector and Web server before you
install VCM. See "Configure the VCM Collector Components" on page 88.
Configure the VCM Collector Components
The combined VCM Collector and Web server contains the VCM software application and VCM services.
To prepare the VCM Collector components of the combined VCM Collector and Web server for VCM
installation, configure the required utilities.
In your two-tier split installation configuration, configure the Web server and VCM Collector components
on the same machine.
NOTE This procedure is required only if you did not install the complete set of Management Tools and
support components earlier.
Prerequisites
n Perform the prerequisite tasks for your two-tier split installation configuration. See "Two-Tier Split
Installation" on page 61.
n From the VCM Collector, verify that you can access the Microsoft Download Center, Microsoft SQL
Server Feature Pack to download SQLXML 4.0 SP1 in the following procedure. See the online Microsoft
Download Center.
n Verify that you can access the Microsoft Download Center, Microsoft SQL Server Feature Pack to
download and install the Native Client (sqlncli.msi) in the following procedure. See the online
Microsoft Download Center. The SQL Command Line Tools in the SQLServer Feature Pack are
88
VMware, Inc.
Two-Tier Split Installation
required on the combined VCM Collector and Web server.
n Install .NET Framework 3.5.1 on the Windows Server 2008 R2, 2012, or 2012 R2 machines where
Package Studio will be installed.
Procedure
1. Download and install SQLXML 4.0 SP1, x64 Package.
2. Download and install SQL Server Command Line Utilities, which includes the SQLCMD utility, x64
Package (SqlCmdLnUtils.msi).
The SQL Command Line Tools in the SQLServer 2008 R2, 2012, or 2014 Feature Pack are required on
the combined VCM Collector and Web server.
3. Download and install the SQL Server Native Client, x64 Package (sqlncli.msi).
The Native Client from the SQL Server Feature Pack is required on the combined VCM Collector and
Web server.
4. Reboot the combined VCM Collector and Web server.
What to do next
Review the DCOMand port requirements, and use VCM Installation Manager to install the VCM
components. See "Installing VCM" on page 125.
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.
CAUTION A three-tier installation configuration uses basic authentication with HTTPS by default. Be
aware of the risks to exposure of sensitive data if you use basic security without HTTPS. Optionally,
you can use Kerberos Authentication.
VCM 5.8 supports 64-bit environments that include 64-bit hardware, the 64-bit Windows Server 2008 R2,
Windows Server 2012, or Windows Server 2012 R2 operating system, and SQL Server 2008 R2, or 2012, or
2014.
Figure 10–1. Three-Tier Split Installation
10
VMware, Inc.
VCM 5.8 supports running SSRS on the Web server or on the database server in a split installation.
Depending on the separation of services in your environment, you might want to install SSRS on the Web
server machine in a split installation, because SSRS has its own Web server.
The VMware Knowledge Base includes information about sizing your hardware environment for a threetier installation of VCM. See http://kb.vmware.com/kb/2033894.
Configuring a Three-Tier Split Installation Environment
In a three-tier installation environment, you configure the database server first, configure the Web server
next, then configure the VCM Collector. All machines are physical or virtual Windows machines.
Prerequisites
n Perform the general system prerequisite tasks. See "System Prerequisites to Install VCM" on page21.
n Connect the database server machine, Web server machine, and VCM Collector machine to the
domain.
n Obtain the installation media for the Enterprise, Standard, or Datacenter edition of SQL Server 2008 R2,
2012, or 2014, or verify access to a file share where the installer resides.
Procedure
1. "Verify that the Installing User is an Administrator" below
The user who installs Windows Server 2008 R2, 2012, or 2012 R2 operating system must be an
Administrator and a domain account.
2. "Install and Configure Windows Server Operating System" on the facing page
Install the Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2 operating
system on each Windows machine that serves as a tier in your configuration.
3. "Configure the VCM Database Server" on page95
To ensure that the installation creates the VCM databases, you must configure the VCM database
server before you install VCM. In a three-tier split installation configuration, the VCM database server
resides on a separate machine. The databases include VCM, VCM_Coll, VCM_Raw, and VCM_UNIX.
4. "Configure the Web Server" on page103
The Web server contains Web applications such as IIS and SQL Server Reporting Services (SSRS), other
services, and VCM software components. Before you install VCM, you must configure the Web
server.
5. "Configure the VCM Collector" on page119
The VCM Collector contains the VCM software application and VCM services. To prepare the VCM
Collector for VCM installation, configure the required utilities.
What to do next
Review the DCOMand port requirements, and use VCM Installation Manager to install the VCM
components. See "Installing VCM" on page 125.
Verify that the Installing User is an Administrator
The user who installs Windows Server 2008 R2, 2012, or 2012 R2 operating system must be an
Administrator and a domain account.
92
VMware, Inc.
Three-Tier Split Installation
Procedure
1. Verify that the user is an Administrator.
a. Click Start and select All Programs > Administrative Tools > Computer Management.
b. Expand System Tools, expand Local Users and Groups, and click Users.
c. Right-click the user and click Properties.
d. Click the Member Of tab and verify that Administrators is listed.
e. If Administrators is not listed, add the user to the Administrators group.
f. Click Check Names and click OK.
2. Verify that the user is a domain account.
a. Click Groups.
b. Right-click Administrators and click Properties.
c. Verify that the Domain User is listed in the Members area.
What to do next
Prepare your Windows machine for VCM installation. See "Install and Configure Windows Server
Operating System" below.
Install and Configure Windows Server Operating System
Install the Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2 operating system
on each Windows machine that serves as a tier in your configuration.
Prerequisites
n Determine whether you require Windows Server 2008 R2, 2012, or 2012 R2 operating system. See
"Sizing Impact on Software Edition Requirements" on page 17.
n The user who installs Windows Server 2008 R2, 2012, or 2012 R2 operating system must be an
Administrator and a domain account. See "Verify that the Installing User is an Administrator" on page
92.
n Decide on a valid DNS computer name with no underscores for use when the Windows installation
prompts for a machine name. If you attempt to change the machine name after a machine is identified
as a Collector, problems might occur with VCM, SQL Server, and SQL Server Reporting Services.
1. Install Microsoft Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2 on your
Windows machine.
2. During the installation, you can configure several options.
OptionDescription
Regional and
Language
Determines how numbers, dates, currencies, and time settings appear.
n Language: Setting for your language. The default is English.
Options
n Time and currency format: Determines how numbers, dates, currencies, and time
settings appear. The default is English (United States).
n Keyboard or input method: Allows text entry for multiple languages. The default
is US.
Disk
Configuration
Allows you to separate the machine disk drive into partitions to store data in
different partitions. You can create new disk partitions and delete existing partitions.
After you configure the disk, select a partition on which to install Windows Server
2008 R2, 2012, or 2012 R2 Edition.
Product KeyWhen the installation prompts, enter your product key.
Licensing
Modes
Administrator
Password
Windows Server 2008 R2, 2012, or 2012 R2 supports a single license that is included
with the product key.
The installation setup creates an account called administrator. To log in, you must
create a password that complies with the criteria. The password must have the
following attributes.
n Minimum of six characters
n Does not contain “administrator” or “admin”
n Contains uppercase letters
n Contains lower case letters
n Contains numbers
n Contains at least one non-alphanumeric character
3. Perform the initial configuration tasks to set the time zone and the computer name.
Disable the Remote Desktop Session Host
A Remote Desktop Session Host server hosts Windows-based programs for Remote Desktop Services
clients.
If the Remote Desktop Session Host role service is enabled, you must disable it to avoid changes to
settings for new connections, modifications of existing connections, or removal of connections.
94
VMware, Inc.
Three-Tier Split Installation
Procedure
1. Click Start and select All Programs > Administrative Tools > Server Manager.
2. In the navigation pane, expand Roles and click Remote Desktop Services.
3. In the Remote Desktop Services pane, scroll down to Role Services.
4. Click the Remote Desktop Session Host role service to highlight it.
5. Click Remove Role Services.
6. Deselect the Remote Desktop Session Host role service and follow the prompts to finish disabling the
Remote Desktop Session host role.
Enable DCOM
The Distributed Component Object Model (DCOM) protocol allows application components to interact
across Windows machines. DCOM must be enabled on the Windows machine to install and run VCM.
Although DCOMis enabled by default when Windows Server 2008 R2, 2012, or 2012 R2 is installed,
DCOMmight have been disabled by a custom installation or a lock-down script.
Procedure
1. Click Start and select All Programs > Administrative Tools > Component Services to open
Component Services.
2. In the Component Services navigation pane, expand Component Services and expand Computers.
3. Right-click the computer and click Properties.
4. Click the Default Properties tab.
5. Select Enable Distributed COM on this computer and click OK.
What to do next
Configure the database server. See "Configure the VCM Database Server" below.
Configure the VCM Database Server
To ensure that the installation creates the VCM databases, you must configure the VCM database server
before you install VCM. In a three-tier split installation configuration, the VCM database server resides on
a separate machine. The databases include VCM, VCM_Coll, VCM_Raw, and VCM_UNIX.
Use of a shared SQL Server is supported for VCM. However, VCM makes heavy use of SQL Server for
query and transaction processing. You must ensure that you have or can add enough capacity to a shared
SQL Server so that VCM and any other databases on the shared server do not experience poor
performance.
The SQL Server license includes SQL Server Reporting Services (SSRS). In your three-tier split installation
configuration, when you run SSRS and SQL Server on the same machine, the SQL Server database
machine can take on the role of the Report Server (SSRS).
VCM 5.8 supports running SSRS on the Web server or on the database server in a split installation.
Depending on the separation of services in your environment, you might want to install SSRS on the Web
server machine in a split installation, because SSRS has its own Web server.
VMware, Inc.
If you install SSRS on the Web server, it requires an additional SQL Server license, because you are
installing SSRS on a Windows Server 2008 R2, 2012, or 2012 R2 machine that is separate from the SQL
Server database services. If you run SQL Server Enterprise Edition, all SQL Server services running in
guests on a single virtual machine host are covered by the Enterprise Edition license.
VCM operates with a Standard, Enterprise, or Datacenter edition of SQL Server. You must install the 64-bit
SQL Server 2008 R2, or 2012, or 2014 version on your designated database server machine and verify that
the settings are configured correctly for a VCM installation.
If you plan to change the communication port that SQL Server uses from the default port of 1433 to a
nonstandard port number, make the changes during the installation of SQL Server and SQL Server
Reporting Services (SSRS). Changing the port after you install SSRS disables SSRS communication with
SQL Server, which causes an SSRS validation error during the VCM installation process. If you change the
port after installation, you must configure additional SSRS settings to repair the configuration.
Install SQL Server on the Database Server
In a three-tier split installation configuration, the VCM database server resides on a separate machine. The
database server contains the VCM, VCM_Coll, VCM_Raw, and VCM_UNIX databases. You must
configure the VCM database server before you install VCM in a three-tier split installation configuration.
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.
Prerequisites
n Obtain the installation media for the Enterprise, Standard, or Datacenter edition of SQL Server 2008 R2,
2012, or 2014, or verify access to a file share where the installer resides.
Procedure
1. Start the SQLServer installation.
2. Perform the following actions to install SQL Server.
For SQL Server 2008 R2
Wizard PageAction
SQL Server
Click New installation or add features to an existing installation.
Installation
Center
Setup Support
Rules
Setup Support
Click Install and verify that all of the rules pass. To view the detailed system
configuration check report, click the link.
Click Install to install the setup support files.
Files
Setup Support
Verify that all of the rules passed.
Rules – for
SQL Server
Setup support
files
Installation
Select New installation or add shared features.
Type
Product KeyVerify that the product key is entered.
License Terms Accept the license terms.
Setup RoleSelect SQL Server Feature Installation.
96
VMware, Inc.
Wizard PageAction
Three-Tier Split Installation
Feature
Selection
Installation
Rules
Instance
Configuration
Disk Space
Requirements
Server
Configuration
Select the following features.
Instance Features:
n Database Engine Services
Shared Features:
n Client Tools Connectivity
n SQL Server Books online
n Management Tools - Basic
and Management Tools - Complete
Verify that the rules passed. To view the detailed system configuration check
report, click the link.
Select Default Instance. If an instance of SQL Server is not installed, the installation
creates a default instance. If an instance of SQLServer is already installed, select
Named Instance and assign a name.
Review the disk usage summary.
Click Use the same account for all SQL Server services and enter the NT
AUTHORITY\SYSTEM account and password.
It is possible to use a domain account for SQL Server services. A domain account
might be required for split installations, because the SQL Server Agent might need
access to the Collector for some activities. If you use a domain account, you should
use a local administrator on the SQL Server machine to access DBServices.
Otherwise, you must grant manual permissions.
Database
Engine
Select Windows authentication and click Add Current User to add the account to
the SQL Server administrators.
Configuration
Error
Review the summary information.
Reporting
Installation
Configuration
Verify that the rules passed. To view the detailed system configuration check
report, click the link.
Rules
Ready to
Install
Review the summary of features and click Install to install SQL Server. When the
installation is finished, click the link to view the log file.
For SQL Server 2012
Wizard PageAction
SQL Server
Installation
Click New SQL Server stand-alone installation or add features to an existing
Click Install and verify that all of the rules pass. To view the detailed system
configuration check report, click the link.
Check for SQL Server updates.
Verify that all rules are passed.
Files
Setup Support
Verify that all of the rules passed.
Rules – for
SQL Server
Setup support
files
Product KeyVerify that the product key is entered.
License Terms Accept the license terms.
Setup RoleSelect SQL Server Feature Installation.
Feature
Selection
Select the following features.
Instance Features:
n Database Engine Services
Shared Features:
Installation
Rules
Instance
Configuration
Disk Space
Requirements
Server
Configuration
Database
Engine
Configuration
n Client Tools Connectivity
n Management Tools - Basic
and Management Tools - Complete
Verify that the rules passed. To view the detailed system configuration check
report, click the link.
Select Default Instance. If an instance of SQL Server is not installed, the installation
creates a default instance. If an instance of SQLServer is already installed, select
Named Instance and assign a name.
Review the disk usage summary.
Browse the accounts for all SQL services and enter the NT AUTHORITY\SYSTEM
account.
It is possible to use a domain account for SQL Server services. A domain account
might be required for split installations, because the SQL Server Agent might need
access to the Collector for some activities. If you use a domain account, you should
use a local administrator on the SQL Server machine to access DBServices.
Otherwise, you must grant manual permissions.
Select Windows authentication and click Add Current User to add the account to
the SQL Server administrators.
98
VMware, Inc.
Wizard PageAction
Three-Tier Split Installation
Error
Review the summary information.
Reporting
Installation
Configuration
Verify that the rules passed. To view the detailed system configuration check
report, click the link.
Rules
Ready to
Install
Review the summary of features and click Install to install SQL Server. When the
installation is finished, click the link to view the log file.
For SQL Server 2014
Wizard PageAction
SQL Server
Installation Center
Click New SQL Server stand-alone installation or add features to anexisting installation.
Product KeyVerify that the product key is entered.
License TermsAccept the license terms.
Microsoft UpdateUse this option to check for Microsoft updates.
Install Setup FilesVerify that all rules are passed.
Setup RoleSelect SQL Server Feature Installation.
Feature SelectionSelect the following features.
Instance Features:
n Database Engine Services
Shared Features:
n Client Tools Connectivity
n Management Tools - Basic
and Management Tools - Complete
Instance
Configuration
Select Default Instance. If an instance of SQL Server is not installed, the
installation creates a default instance. If an instance of SQLServer is already
installed, select Named Instance and assign a name.
Server
Configuration
Browse the accounts for all SQL services and enter the NT
AUTHORITY\SYSTEM account.
It is possible to use a domain account for SQL Server services. A domain
account might be required for split installations, because the SQL Server
Agent might need access to the Collector for some activities. If you use a
domain account, you should use a local administrator on the SQL Server
machine to access DBServices. Otherwise, you must grant manual
permissions.
Database Engine
Configuration
Select Windows authentication and click Add Current User to add the
account to the SQL Server administrators.
VMware, Inc.
Ready to InstallReview the summary of features and click Install to install SQL Server. When
the installation is finished, click the link to view the log file.
To ensure that SQLServer will operate with VCM, verify the SQLServer property settings and set the
server-wide SQL database settings in preparation to install VCM. For information about server-wide and
database-specific SQL Server database settings, see the VCM Administration Guide.
Procedure
1. Launch SQL Server Management Studio.
2. Right-click the SQL instance and select Properties.
3. Confirm the General page server property of Version as 10.50.1600.1 or some later build of version
10.50.
4. Select and confirm the Security page server properties.
a. Select Windows Authentication mode, which is recommended.
b. Although SQL Server and Windows Authentication mode is acceptable for VCM, select Windows
Authentication mode, which is recommended.
5. Select and confirm the Database Settings page server properties.
a. For Default index fill factor, type or select a percentage value, which specifies the amount of free
space in each index page when the page is rebuilt.
Set the fill factor to 80% to keep 20% free space available in each index page.
b. For Recovery interval (minutes), type or select 5.
6. Click OK to save your changes.
What to do next
n Restart the database machine.
n To ensure that SQLServer and VCMoperate correctly together, verify that the SQLServer name
matches the Windows machine name. See "Verify Matching SQL Server and Computer Names" below.
Verify Matching SQL Server and Computer Names
To ensure that SQLServer and VCM operate correctly together, you must verify that the SQLServer
name matches the Windows machine name. If you recently installed SQL Server, you do not need to
verify that the names match. If you obtained a machine that was renamed after the operating system and
SQL Server were installed, verify and reset the SQLServer server name.
Procedure
1. Launch SQL Server Management Studio.
100
2. Click Database Engine Query.
3. In the SQL Query pane, type SELECT @@Servername and click Execute.
4. Verify that the resulting SQL Server name matches the Windows machine name.
5. If the SQL Server name does not match the Windows machine name, reset the SQL Server name.
VMware, Inc.
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.