VMware vCenter Configuration Manager Installation Guide vCenter Configuration Manager 5.7 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs.
vCenter Configuration Manager Installation Guide You can find the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: docfeedback@vmware.com © 2006–2013 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents About This Book 5 Preparing to Install VCM 7 Typical or Advanced Installation VCM Installation Configurations Create VCM Domain Accounts VCM Account Configuration VCM Administrator Account VCM User Accounts Service Accounts Network Authority Account ECMSRSUser Account SQL Server Permissions and Constructs Gather Supporting Software Hardware and Software Requirements for VCM Servers Determine the Size of Your Environment Hardware and Disk Requirements By Number of Managed Machines Database Sizi
vCenter Configuration Manager Installation Guide Change the VCM Remote Virtual Directory Name Configure Additional Database Settings Select Separate Installation Folders Post-Installation On-Access Antivirus Settings SQL Server Database Settings Configure SQL Server Processor Settings Use SQLIO to Determine I/O Channel Throughput Hardware and Operating System Requirements for VCM Managed Machines VCM Agent Support on Non-English Windows Platforms VCM Managed Machine Requirements Linux, UNIX, and Mac OS A
About This Book The VCM Installation Guide describes how to install vCenter Configuration Manager (VCM) using the Typical Installation option. This document contains the following information: n Preliminary steps that prepare you and your domain for installation n Prerequisites for any server on which you run the Typical Installation option n Typical Installation steps n Post-installation steps n Requirements for VCM managed machines The VCM Installation Guide applies to VCM 5.
vCenter Configuration Manager Installation Guide Technical Support and Education Resources The following technical support resources are available to you. To access the current version of this book and other books, go to http://www.vmware.com/support/pubs. Online and Telephone To use online support to submit technical support requests, view your Support product and contract information, and register your products, go to http://www.vmware.com/support.
1 Preparing to Install VCM Before you work with the Windows machines on which you will install prerequisites and the VCM software, do the following evaluation and preparation tasks.
vCenter Configuration Manager Installation Guide n Using the classic Installation Manager to install VCM n Any three-tier split installation n Two-tier split installations that use Kerberos authentication n Upgrading to this version of VCM n Migrating VCM to another server or servers n Maintaining VCM after installation n Hardware and software requirements for the operating system provisioning server n Installing, configuring, and upgrading the operating system provisioning server and compon
Preparing to Install VCM Create VCM Domain Accounts VCM requires that you create domain accounts with certain permissions. In the VCM Typical Installation, you have the option to use the built-in Local System account in place of some of the accounts. Before installing VCM, create or identify the domain accounts to use for each of the VCM functions. Keep the credentials on hand for when the installation prompts for an account username and password.
vCenter Configuration Manager Installation Guide Account Permissions VCM Default Network Authority Local admin on Windows machines that VCM collects from using the DCOM Agent Depending on enterprise size and for convenience, possibly a separate, domain administrator account with rights on the Windows machines Not an interactive user account VCM Account Configuration You create accounts for VCM to use as described in "Create VCM Domain Accounts" on the previous page.
Preparing to Install VCM IMPORTANT Never use the service accounts for logging in to the VCM Console or for any other purpose. Logging in to VCM using a service account can lead to unexpected or inconsistent behavior. Services that use the same account as a logged in user might modify the logged in user's current role or the machine group, or log the user out of the system.
vCenter Configuration Manager Installation Guide Network Authority Account The Network Authority account is for data collection from DCOM Windows machines, data collection from Active Directory, and for Active Directory and NT domain discovery. VCM supports multiple Network Authority accounts but must have at least a default Network Authority account configured. Configure Network Authority accounts in VCM under the Administration slider.
Preparing to Install VCM Gather Supporting Software To install VCM, you need the VCM software plus your operating system and database software. Supporting products might be bundled or standalone, depending on edition type such as Standard or Enterprise. In addition, some software might be needed only for split installations. Before installing, gather copies of the following software from downloads or media so that you have it on hand when the VCM Installer prompts for it.
vCenter Configuration Manager Installation Guide 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.
Preparing to Install VCM Table 1–3. Blank Sizing Worksheet Product Description VCM Windows Servers Anticipated Number of Managed Machines in the Next 12–24 Months 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.
vCenter Configuration Manager Installation Guide Separate Disk Channels Single Tier 2-Tier Database 2-Tier Web/Collector 2 2 1 Table 1–5. Minimum Hardware Requirements to Support 1001–2000 Managed Machines Single Tier 2-Tier Database 2-Tier Web/Collector Processor Quad Xeon or two Dual Core 2GHz Quad Xeon or two Dual Core 2GHz Dual Xeon or single Dual Core 2GHz RAM 12GB 12GB 4GB Separate Disk Channels 3 3 2 Table 1–6.
Preparing to Install VCM Number of VCM Managed Machines RAID Channel and RAID Level Partitions Usable Space 501–1000 Channel 0 – RAID 1 OS 36GB Collector Data Files 36GB TempDB 56GB SQL Log Files 56GB Channel 2 – RAID 0+1 (recommended) or RAID 10 SQL Data Files 113GB Channel 0 – RAID 1 OS 36GB Collector Data Files 54GB Channel 1 – RAID 1 TempDB 113GB Channel 2 – RAID 1 SQL Log Files 113GB Channel 3 – RAID 0+1 (recommended) or RAID 10 SQL Data Files 227GB Channel 0 – RAID 1 O
vCenter Configuration Manager Installation Guide The best practice in production environments is to have the Managing Agent process the 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.
Preparing to Install VCM Prerequisites n Address the non-virtual hardware and software requirements. See "Hardware and Software Requirements for VCM Servers" on page 13. n Follow best practices whenever you install SQL Server on a virtual machine. See the Microsoft SQL Server on VMware Best Practices Guide available on the VMware Web site at http://www.vmware.com. Procedure 1. "Configure the Disk to Install VCM on a Virtual Machine" below Configure the disk for the virtual machine.
vCenter Configuration Manager Installation Guide What to do next Configure the CPU for the virtual machine. See "Configure the CPU to Install VCM on a Virtual Machine" below. Configure the CPU to Install VCM on a Virtual Machine Configure the CPU for the virtual machine. For large scale environments, you might need to alter the requirements.
Preparing to Install VCM Procedure 1. Start vCenter Server. 2. Select your virtual machine. 3. Click the Resource Allocation tab. 4. In the Memory pane, click Edit. 5. In the Virtual Machine Properties dialog box, click the Resources tab. 6. In the Resource Allocation pane, click Memory and change the memory resource allocation. 7. Click OK. VMware, Inc.
vCenter Configuration Manager Installation Guide 22 VMware, Inc.
2 Common Prerequisites for All VCM Servers All Windows machines that become VCM servers require the following prerequisites.
vCenter Configuration Manager Installation Guide Procedure 1. Install Microsoft Windows Server 2008 R2 on your Windows machine. 2. During the installation, you can configure several options. Option Description Regional and Language Options Determines how numbers, dates, currencies, and time settings appear. n Language: Setting for your language. The default is English. n Time and currency format: Determines how numbers, dates, currencies, and time settings appear.
Common Prerequisites for All VCM Servers 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.
vCenter Configuration Manager Installation Guide Procedure 1. Log in with a local administrator account. 2. Select Start > Administrative Tools > Computer Management. 3. On the left, navigate to Computer Management (Local) > System Tools > Local Users and Groups > Groups. 4. On the right, double-click Administrators. 5. Click Add. 6. For the object name, type the domain and account name, separated by a backslash. For example: mydomain\vcmadmin 7. Click OK. 8.
3 VCM Installation The following sections describe a typical VCM installation. To perform an advanced installation, see the VCM Advanced Installation Guide. This chapter includes the following topics: Start the VCM Installer 27 Prerequisites 28 Basic Information 35 Additional Information 37 Start the VCM Installer To begin installing VCM, start the VCM Installer. Prerequisites n Log in using the VCM administrator domain account. See "Log in as VCM Administrator" on page 26. Procedure 1.
vCenter Configuration Manager Installation Guide What to do next Address any missing prerequisites. If the VCM Installer found that all prerequisites were met, the basic information page appears, where you enter settings for VCM installation. What the Installer Checks For The VCMTypical Installation checks to make sure that prerequisites are enabled and installed. n .NET Framework 3.
VCM Installation Windows machine, the VCM Installer configures it when you start the VCM installation. 7. "Remove the VCM Agent" on page 34. VCM does not operate correctly when a previous VCM Agent is already installed on the Windows machine. If an existing VCM Agent is detected, the VCM Installer removes it when you start the VCM installation. What to do next Enter basic and (optional) additional information.
vCenter Configuration Manager Installation Guide 5. If you do not have a SQL Server instance , click Install a New Instance to install an instance on the current machine, which creates a single-tier configuration. a. Browse to a copy of SQL Server 2008 R2 or 2012, Standard or Enterprise, and enter the product license if your edition requires one. b. If you do not have a copy of SQL Server, make sure that the server is connected to the Internet, and click Download Evaluation Version.
VCM Installation Procedure 1. On the left, click Prerequisites. 2. In SQL Server Reporting Services Web Service URL, type the address for the SSRS server. The default is: http://{server-name}:80/ReportServer 3. Click Validate. 4. Click OK. If you do not have an SSRS server, install one by running the SQL Server 2008 R2 or 2012, Standard or Enterprise installer. Follow the prompts to add SSRS. Alternatively, run the SQL Server evaluation installer to add an evaluation version of SSRS.
vCenter Configuration Manager Installation Guide ... 5. Replace any existing parameters with one parameter. ... 6. Save and close rsreportserver.config. 7. Start the SSRS service.
VCM Installation Prerequisites n Log in using the VCM administrator domain account. n Start the VCM Installer, select Typical Installation, and allow the VCM Installer to check for prerequisites. n For SQL Server native client and SQL Server command-line tools downloads, the server must be able to connect to the Internet. Procedure 1. On the left, click Prerequisites. 2. Under SQL Server Support Components, click Install SQL Server Utilities. 3. Browse to copies of the utilities, and install them. 4.
vCenter Configuration Manager Installation Guide Procedure 1. On the left, click Prerequisites. 2. Under Internet Information Services, note whether IIS will be configured. When you start the installation, the VCM Installer configures IIS in encrypted or unencrypted mode and creates the VCM Web server. What to do next VCM requires Microsoft .NET Framework 3.5. If the .NET Framework is not configured on the Windows machine, the VCM Installer configures it when you start the VCM installation.
VCM Installation What to do next Click Next, and enter the basic settings needed for installation. See "Basic Information" below. Basic Information Before you start the installation, you must add license keys, select service accounts, and select an installation folder. Prerequisites Click Prerequisites, and correct any missing installation requirements. See "Prerequisites" on page 28. Procedure 1. "Add VCM License Keys" below.
vCenter Configuration Manager Installation Guide Add the Services and Login Accounts Select the accounts under which VCM services and logins run. Prerequisites n Click Prerequisites, and correct any missing installation requirements. See "Prerequisites" on page 28. Procedure 1. On the left, click Basic Information. 2. Under VCM Accounts, select one of the following options. n Use Built-in Accounts. Run VCM logins and services under built-in Windows operating system accounts.
VCM Installation Procedure 1. On the left, click Basic Information. 2. Under Install Path, type the folder path you want, or click the ellipsis button to browse to a folder. The default folder is: {drive}:\Program Files (x86)\VMware\VCM The default drive letter is the drive that has the most free space. What to do next Select whether to access the VCM Console over encrypted HTTPS. See "Enable HTTPS" below. Enable HTTPS Select whether to access the VCM Console over encrypted HTTPS.
vCenter Configuration Manager Installation Guide Procedure 1. "Select Separate Services and Login Accounts" below. (Optional) Select separate accounts under which VCM services and logins run. 2. "Change the VCM Console Virtual Directory Name" below. (Optional) Change the VCM Console virtual directory name to a name other than the default. 3. "Change the VCM Remote Virtual Directory Name" on the facing page. (Optional) Change the VCM Remote virtual directory name to a name other than the default. 4.
VCM Installation Prerequisites n Click Prerequisites and correct any missing installation requirements. See "Prerequisites" on page 28. n Click Basic Information and enter the basic installation settings. See "Basic Information" on page 35. Procedure 1. On the left, click Additional Information. 2. Under User Credentials, click the VCM Remote tab. 3. In the Console Virtual Directory Name text box, type the name you want. The default is VCM.
vCenter Configuration Manager Installation Guide Procedure 1. On the left, click Additional Information. 2. In Additional Information, click the Database tab. 3. Edit the following settings: Option Description Database Name Name of the VCM database. The default is VCM.
VCM Installation The Collector data folder holds managed machine data until that data is written to the VCM database. The folder content is dynamic and changes as collections occur, and it can be placed on slower performing storage. The database, Web console, and Tomcat folders hold binaries that support those respective functions and are installed into separate folders if you want better fault isolation and troubleshooting capability.
vCenter Configuration Manager Installation Guide 42 VMware, Inc.
4 Post-Installation After installing VCM, do the following post-installation tasks to complete the installation and configuration of your VCM environment.
vCenter Configuration Manager Installation Guide Procedure 1. Click Start. 2. Select All Programs > Microsoft SQL Server {version} > SQL Server Management Studio. 3. Right-click the SQL instance that you installed and select Properties. 4. In the Select a page area, select Database Settings. 5. Configure the following settings. n Default index fill factor. Sets a percentage value for the amount of free space in each index page when the page is rebuilt.
Post-Installation n To remove a processor from SQL Server and reserve it for the OS, uncheck the check box next to the processor. Remove the processor that the network card will use so that network communication does not affect SQL Server. Most network cards use the first processor, but some Intel network cards use the last processor.
vCenter Configuration Manager Installation Guide 46 VMware, Inc.
Hardware and Operating System Requirements for VCM Managed Machines 5 VCM collects data from Windows and UNIX machines that VCM manages. The VCM Agent is supported on many different machine and operating system types. This chapter includes the following topics: VCM Agent Support on Non-English Windows Platforms 47 VCM Managed Machine Requirements 47 Linux, UNIX, and Mac OS Agent Files 50 Windows Custom Information Supports PowerShell 2.
vCenter Configuration Manager Installation Guide Machines that are noted with a specific Agent version are supported with the Agent version listed. For machines that are noted with support up to the a certain Agent version, you could install an earlier version of the Agent on these platforms, but you cannot install a newer Agent, which means that you cannot use the latest features on those machines. Contact VMware Technical Support for previously supported Agents. The following x64 platforms are tested.
Hardware and Operating System Requirements for VCM Managed Machines Agent Supported Operating System Supported Hardware Platform Platforms To Be Upgraded ESX 4.1, 4.1 Update 1 ESXi 4.1, 4.1 Update 1, Update 2, Update 3 ESXi 5.0, 5.0 Update 1 ESXi 5.1 HP-UX 11i v1.0 (11.11) (up to 5.4 Agent only) (If you install the Agent on HPUX 11.11, patch PHSS_30966 is required.) Supported in trusted mode in the default configuration. PA-RISC HP-UX 11i v2.0 (11.23) (up to 5.4 Agent only) Itanium HP-UX 11i v2.
vCenter Configuration Manager Installation Guide Linux, UNIX, and Mac OS Agent Files VCM Linux, UNIX, and Mac OS Agent files are architecture specific. When you install the Agent using VCM, the target operating systems are evaluated and the corresponding Agent is installed. If you are manually installing the Agent on the target machine, you must ensure that you use to correct Agent binary packages. The Agent packages are located on the Collector in \Program Files (x86) \VMware\VCM\Installer\Packages by def
Hardware and Operating System Requirements for VCM Managed Machines Table 5–3. Supported Operating Systems Operating System Versions Red Hat Enterprise Linux (RHEL) (Server only) 5.0, 5.2, 5.4, 5.5, 5.6, 5.8, 6.0, 6.2, 6.3, 32-bit and 64-bit SUSE Linux Enterprise Server (SLES) 10.3, 32-bit and 64-bit 11.1, 32-bit and 64-bit 11.2, 32-bit and 64-bit (Custom import as 11.
vCenter Configuration Manager Installation Guide Software Provisioning Component Description Requirements Software Repositories File system used to store the shared software packages. .NET 3.5.1 and IIS 6, 7, or 7.5 Package Manager Application on each managed machine that downloads packages from repositories, and installs and removes the software contained in the packages. .NET 3.5.
Hardware and Operating System Requirements for VCM Managed Machines Support for VMware Cloud Infrastructure Use VCM to collect data from vCenter Server, vCloud Director, and vShield Manager. The collection runs on the supported platforms using the VMware API/SDK through a Managing Agent. To collect ESX Linux Data Types from the ESX Service Console OS, including ESX Logs, you use an Agent Proxy.
vCenter Configuration Manager Installation Guide Physical Requirements for Virtualization Agent Proxy n Processor. Single Xeon or single-core 2GHz minimum n RAM. 4GB minimum n Disk Space. Each Agent Proxy requires an additional 93MB of disk space, above the 200MB required for the standard Agent. You will also need: n 4MB per ESX server for data model storage n 150MB per ESX server for Agent master files Virtual Requirements for Virtualization Agent Proxy n CPU.
Hardware and Operating System Requirements for VCM Managed Machines Operating System Version Hardware Platform FIPS Module Certificate Windows Vista 1 x86 and 64-bit 892 Windows 2003 SP2 x86 and 64-bit 875 Windows 2003 SP1 x86 and 64-bit 382 Windows 2003 SP1 x86 and 64-bit 381 Windows 2003 Gold x86 and 64-bit 382 Windows 2003 Gold x86 and 64-bit 381 Windows XP SP2 x86 240 Windows XP SP2 x86 238 Windows XP SP1 x86 240 Windows XP Gold x86 240 Windows XP Gold x86
vCenter Configuration Manager Installation Guide RSAENH Validated Operating Systems Validated Versions (Links to Security Policy) FIPS Certificate # FIPS Version Validated Vista Ultimate Edition SP1 6.0.6001.22202 #1002 140–2 Windows Server 2008 6.0.6001.22202 #1010 140–2 Cryptographic DSS Enhanced Validated Modules The Microsoft Cryptography API (CAPI) supports the following validated versions of DSS enhanced modules, and the operating systems for which the testing is valid. Table 5–10.
Hardware and Operating System Requirements for VCM Managed Machines Table 5–11. Windows Agents and Component File Sizes Agent Type Installed File Size Data File Size Projected Data File Size VCM Agent used as Managing Agent 130–135MB 200MB–1GB The projected data file sizing information can vary depending on the size of your vCenter Server instances and the number of hosts and guests.
vCenter Configuration Manager Installation Guide Agent Type Installed File Size Data File Size Package Manager (installed with VCM Agent Extension for Provisioning), which includes the database and cratecache. Package n/a Manager 4MB Database 140KB Projected Data File Size Package Manager. The application that installs and removes packages. Size remains fixed. Database. Metadata about packages. Increased size based on number of installed packages.
Hardware and Operating System Requirements for VCM Managed Machines Agent Type Installed File Size Data File Size CMAgent.5.7.0.SunOS 80–90MB 25MB CMAgent.5.7.0.SunOS.x86.5.10 80–90MB 35MB Mac OS X Machines The projected data file sizing information for Mac OS X machines can vary depending on your collection filter set and is determined by collected data types and actions. The size can vary from 10–20MB to more than 100MB.
vCenter Configuration Manager Installation Guide 60 VMware, Inc.
Index A account built-in 36 Collector service 11 default network authority 12 domain 25 network authority 12 services 36, 38 Tomcat service 11 VCM administrator 10, 26 VCM Remote service 11 vSphere Client VCM plug-in 11 advanced installation 7 Agent disk size 56 hardware 47 non-English Windows platforms 47 patch assessment 52 removal prerequisite 34 software provisioning 51 Agent machines for new content architecture 52 Agent Proxy FIPS 56 hardware requirements 53 OS requirements 53 virtualization 53 antiv
vCenter Configuration Manager Installation Guide installing VCM on a virtual machine 18 K Kerberos authentication 7 L language packs for Windows machines 47 large scale environment 43 LDF file 39 license keys 35 Linux/UNIX Agent file size 58 machine patch assessment 52 M Mac OS X Agent file size 59 machine preparation 7 maintaining VCM 7 managed machines 14, 47 requirements 47 Managing Agent 53 requirements 53 MDF file 39 memory virtual machine 20 Microsoft CryptoAPI 54 migrating VCM 7 minimum requireme
Index VCM Console virtual directory 38 VCM database name 39 VCM database server 29, 39 VCM Remote service account 11 VCM Remote virtual directory 39 virtual directory VCM Console 38 VCM Remote 39 virtual environment data collection 53 virtual machine CPU 20 disk space 19 installing VCM on 18 memory 20 minimum requirements 18 virtualization Agent Proxy 53 VMware Cloud Infrastructure 53 vShield Manager 53 vSphere Client VCM plug-in account 11 W WCI PowerShell 50 Windows FIPS 54 version 13 Windows Agent file
vCenter Configuration Manager Installation Guide 64 VMware, Inc.
