VMware vCenter Configuration Manager Advanced Installation Guide vCenter Configuration Manager 5.6 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 Advanced Installation Guide You can find the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: docfeedback@vmware.com © 2006–2012 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents About This Book Achieving a Successful VCM Installation VCM Collector and Agent OS Platform Support Hardware Requirements for Collector Machines Determine the Size of Your Environment Identify Your Specific Hardware Requirements Database Sizing for Managed vCenter Server Instances Hardware and Disk Requirements By Number of Managed Machines Software and Operating System Requirements for Collector Machines Sizing Impacts on Software Requirements Software Installation and Configuration Overview VC
vCenter Configuration Manager Advanced Installation Guide Verify the ASP Role Service Verify the ASP.
Contents Configuring IIS Verify the ISAPI Extensions Place the Web Server in the Internet Explorer Trusted Zone Access to Patch Download Folder for Windows Patch Deployment Installing and Configuring SSRS on the Web Server Configure Kerberos Authentication Modify the SQLCMD Path Variable Configure the VCM Collector Install the .
vCenter Configuration Manager Advanced Installation Guide VCM Agent Support on Non-English Windows Platforms VCM Managed Machine Requirements Windows Custom Information Supports PowerShell 2.
About This Book The VCM Advanced Installation Guide describes the steps to install VCM in all supported installation configurations. This document includes detailed information that does not appear in the VCM Installation Guide.
vCenter Configuration Manager Advanced Installation Guide VMware VCM Documentation The vCenter Configuration Manager (VCM) documentation consists of the VCM Installation Guide, VCM Administration Guide, VCM Advanced Installation Guide, VCM online help, and other associated documentation. 8 VMware, Inc.
vCenter Configuration Manager Advanced Installation Guide Technical Support and Education Resources The following technical support resources are available to you. To access the current version of this book and other books, go to http://www.vmware.com/support/pubs. Online and Telephone 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.
Achieving a Successful VCM Installation 1 Perform the requirements to successfully install VMware vCenter 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 vCenter Configuration Manager (VCM). Perform the preparatory steps to install and configure your physical and virtual machines for a successful VCM installation.
vCenter Configuration Manager Advanced Installation Guide For details about VCM Collector machines, see Hardware Requirements for Collector Machines and Software and Operating System Requirements for Collector Machines in the VCM Installation Guide. For details about VCM managed machines, see Hardware and Operating System Requirements for Managed Machines in the VCM Installation Guide. 11 VMware, Inc.
Hardware Requirements for Collector Machines 2 Your VCM Collector hardware requirements depend on the number of physical and virtual managed machines in your environment. Use this information to determine how many machines you plan to manage. You can determine the individual hardware requirements to ensure a successful VCM installation. Disk space requirements vary based on the following factors.
vCenter Configuration Manager Advanced Installation Guide Table 2–1. Sizing Worksheet Product Description VCM Anticipated Number of Managed Machines in the Next 12-24 Months Windows Servers ESXi Servers Guest Virtual Machines Linux or UNIX Mac Windows Workstations VCM for AD Divide total number of AD objects by 100 to determine the approximate "machine count" for your AD environment.
Hardware Requirements for Collector Machines Table 2–3. VCM Database Sizing per vCenter Server Instance Hosts Guests Est. Daily Change Data Retention in Days Data Size 25 250 10% 15 3GB 50 500 10% 15 6GB 250 2500 10% 15 30GB The best practice in production environments is to have the Managing Agent process requests for a single vCenter Server. Dedicate one Managing Agent machine for each vCenter Server.
vCenter Configuration Manager Advanced Installation Guide Table 2–4.
3 Software and Operating System Requirements for Collector Machines Your VCM environment software configuration must meet the requirements to install VCM 5.6. 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.
vCenter Configuration Manager Advanced Installation Guide VCM supports several installation configurations including single-tier, two-tier, and three-tier. You use Installation Manager to install VCM in these configurations. See "Preparing for Installation" on page 18. To understand the requirements to upgrade or migrate your environment to the latest version of VCM, see "VCM Upgrades and Migrations" on page 17.
Preparing for Installation 4 Prepare your environment for a VCM installation by performing the prerequisites to include hardware, software, and physical and virtual machines before you install VCM components and tools. VCM Installation Configurations VCM supports several installation configurations including single-tier, two-tier, and three-tier. Use Installation Manager to install VCM in these configurations.
vCenter Configuration Manager Advanced Installation Guide 19 VMware, Inc.
System Prerequisites to Install VCM 5 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.
vCenter Configuration Manager Advanced Installation Guide Verify that the VMware Application Services Account is a domain user. n "Verify the VCM Agent is Not Installed" on page 24 The target Windows machine must not have a VCM Agent installed before you install VCM. If an Agent is installed, you must uninstall the Agent for VCM to install. n "Verify the SQLXML Version" on page 25 SQLXML provides client-side XML functionality and enhancements to existing SQL features. SQLXML 4.
System Prerequisites to Install VCM 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 in compatibility mode. n Mozilla Firefox version 6.0 or later with the Internet Explorer IE Tab add-on. This add-on requires Internet Explorer 6.
vCenter Configuration Manager Advanced Installation Guide CAUTION Do not use Network Service for the SQL Server service account. If you use the Network Service account for your SQL Server instance, VCM installation could fail. Foundation Checker does not check for this account during VCM installation. The LocalSystem account, NT AUTHORITY\System, has unrestricted access to all local system resources. This account is a member of the Windows Administrators group on the local machine. If the NT AUTHORITY\Syst
System Prerequisites to Install VCM 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 application services 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. Ensure that the user has Windows administrator rights issued by the network administrator.
vCenter Configuration Manager Advanced Installation Guide 4. Uninstall the VCM Agent. a. If the Agent was installed using the MSI installer, to uninstall the Agent click Start and click Run to execute the command line using the UninstallString registry value. An example value is as follows. MsiExec.exe /X{7C51E2CA-C932-44EF-8B77-3C03356A24CC}. b. If the Agent was installed using the manual installer, run the following command to uninstall the Agent. %windir%\CMAgent\Uninstall\Packages\CMAgentInstall\UnCMAg
Configure Resources to Install VCM on a Virtual Machine 6 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.
vCenter Configuration Manager Advanced Installation Guide Configure the Disk to Install VCM on a Virtual Machine Configure the disk for the virtual machine. For large scale environments, you might need to alter the requirements. Prerequisites n Prepare the virtual machine to be used as a VCM Collector. See "Configure Resources to Install VCM on a Virtual Machine" on page 26.
Configure Resources to Install VCM on a Virtual Machine Procedure 1. Start vCenter Server. 2. Select your virtual machine. 3. Click the Resource Allocation tab. 4. In the CPU pane, click Edit. 5. In the Virtual Machine Properties dialog box, click the Resources tab. 6. In the Resource Allocation pane, click CPU and change the CPU resource allocation. 7. Click OK. What to do next Configure the memory for the virtual machine. See "Configure the Memory to Install VCM on a Virtual Machine" on page 28.
vCenter Configuration Manager Advanced Installation Guide 29 VMware, Inc.
Secure Communications Certificates 7 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.
vCenter Configuration Manager Advanced Installation Guide 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.
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.
vCenter Configuration Manager Advanced Installation Guide 33 VMware, Inc.
Single-Tier Server Installation 8 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 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.
vCenter Configuration Manager Advanced Installation Guide Figure 8–2. Typical VCM Enterprise-Wide, Single-Server Installation 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.
Single-Tier Server Installation Figure 8–3. VCM Collector with OS Provisioning Server For advanced information to install VCM in a single-tier environment, see the VCM Advanced Installation Guide. Configure a Single-Tier Installation Environment In a single-tier installation configuration, you configure the single Windows Server 2008 R2 machine for the Database, Web, and VCM Collector components, then install VCM. The machine can be a physical or virtual Windows machine.
vCenter Configuration Manager Advanced Installation Guide Procedure 1. "Verify that the Installing User is an Administrator" on page 37 The user who installs the Windows Server 2008 R2 operating system must be an Administrator and a domain account. 2.
Single-Tier Server 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.
vCenter Configuration Manager Advanced 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.
Single-Tier Server Installation 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. Procedure 1. Click Start and select All Programs > Administrative Tools > Server Manager. 2.
vCenter Configuration Manager Advanced Installation Guide 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 .
Single-Tier Server Installation 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. VCM operates with a Standard or Enterprise edition of SQL Server.
vCenter Configuration Manager Advanced Installation Guide Wizard Page Action Setup Support Verify that all of the rules passed. Rules – for SQL Server Setup support files Installation Type Select New installation or add shared features. Product Key Verify that the product key is entered. License Terms Accept the license terms. Setup Role Select SQL Server Feature Installation. Feature Selection Select the following features.
Single-Tier Server Installation Wizard Page Action Installation Verify that the rules passed. To view the detailed system configuration check Configuration report, click the link. Rules Ready to Install Review the summary of features and click Install to install SQL Server 2008 R2. 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 SQL Server properties.
vCenter Configuration Manager Advanced Installation Guide Verify Matching SQL Server and Computer Names To ensure that SQL Server and VCM operate correctly together, you must verify that the SQL Server name matches the Windows machine name. If you recently installed SQL Server 2008 R2, 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 2008 R2 were installed, verify and reset the SQL Server server name. Procedure 1.
Single-Tier Server Installation Select the SQL Server Agent Service Account SQL Server Agent is a service that runs scheduled jobs in SQL Server 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 on as a service and the required additional permissions.
vCenter Configuration Manager Advanced Installation Guide Procedure 1. Click Start and select All Programs > Microsoft SQL Server 2008 R2 > 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.
Single-Tier Server Installation components are installed. n Windows Process Activation Service n Process Model n .NET Environment 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.
vCenter Configuration Manager Advanced Installation Guide 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 VCM Collector. Procedure 1. On the Collector, click Start and select All Programs > Administrative Tools > Server Manager. 2.
Single-Tier Server Installation Role Service Category Role Service Management Tools IIS Management 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. Configure the IIS 7.5 Settings IIS settings configure the information required for requests to communicate with a Web site. To support VCM interaction with IIS, configure the settings for the IIS 7.
vCenter Configuration Manager Advanced Installation Guide Procedure 1. Click Start and select All Programs > Administrative Tools > Server Manager. 2. Expand Server Manager () 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.
Single-Tier Server Installation 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.
vCenter Configuration Manager Advanced Installation Guide 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.
Single-Tier Server Installation 4. In the file, locate the block. The block resembles the following example. ... 5. Remove any existing parameters and add the parameter to the XML element. The modified block resembles the following block. ...
vCenter Configuration Manager Advanced Installation Guide Procedure 1. Log in to your Windows Server 2008 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 SQL Server 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.
Single-Tier Server Installation 10. Verify whether SSRS is running on the SQL Server 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 and . c. Add and . The default location for the configuration file is C:\Program Files\Microsoft SQL ServerReportingServicesInstance\Reporting Services\ReportServer\rsreportserver.
vCenter Configuration Manager Advanced Installation Guide 16. In Windows Explorer, update the configuration files. a. Open the configuration file at Windows\System32\inetsrv\config\applicationhost.config and locate the 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.
Single-Tier Server Installation Procedure 1. Download and install SQL XML 4.0 and SP1, X64 Package. 2. Download and install SQL Server 2008 R2 Command Line Utilities, which includes the SQLCMD utility, X64 Package (SqlCmdLnUtils.msi). The SQL Command Line Tools in the SQL Server 2008 R2 Feature Pack are required. 3. Download and install the SQL Server 2008 R2 Native Client, X64 Package (sqlncli.msi). The Native Client from the SQL Server 2008 R2 Feature Pack is required. 4. Reboot the VCM Collector.
vCenter Configuration Manager Advanced Installation Guide 59 VMware, Inc.
Two-Tier Split Installation 9 In a two-tier split installation, the VCM database resides on the Windows Server 2008 R2 database server machine, and the VCM Collector and Web components reside on the second Windows Server 2008 R2 machine. VCM 5.6 supports 64-bit environments that include 64-bit hardware, the 64-bit Windows Server 2008 R2 operating system, and SQL Server 2008 R2. CAUTION A two-tier installation configuration uses basic authentication with HTTPS by default.
vCenter Configuration Manager Advanced Installation Guide 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.
Two-Tier Split Installation 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. 6. "Configure the VCM Collector Components" on page 84 The combined VCM Collector and Web server contains the VCM software application, VCM services, and the OS Provisioning Server.
vCenter Configuration Manager Advanced Installation Guide Prerequisites n Determine whether you require the Windows Server 2008 R2 Enterprise Edition or Standard Edition. See the VCM Installation Guide. n The user who installs the Windows Server 2008 R2 operating system must be an Administrator and a domain account. See "Verify that the Installing User is an Administrator" on page 62. n Verify that the computer name settings for your Windows machine is a valid DNS machine name with no underscores.
Two-Tier Split Installation Configure the Operating System Locale Settings To set the language for VCM installation, verify that your Windows Server Locale Setting is configured correctly. Procedure 1. In Windows Explorer, click Start and select Control Panel > Clock, Language, and Region. 2. Click Region and Language. 3. Click the Administrative tab and set the language to English (United States).
vCenter Configuration Manager Advanced Installation Guide 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 dedicated machine. The databases include VCM, VCM_Coll, VCM_Raw, and VCM_UNIX. The SQL Server license includes SQL Server Reporting Services (SSRS).
Two-Tier Split Installation 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.
vCenter Configuration Manager Advanced Installation Guide Wizard Page Action License Terms Accept the license terms. Setup Role Select SQL Server Feature Installation. Feature Selection Select the following features. Instance Features: n Database Engine Services Shared Features: Installation Rules n Client Tools Connectivity n SQL Server Books online n Management Tools - Basic and Management Tools - Complete Verify that the rules passed.
Two-Tier Split Installation Verify and Configure the SQL Server Properties To ensure that SQL Server will operate with VCM, verify the SQL Server 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. Click Start and select All Programs > Microsoft SQL Server 2008 R2 > SQL Server Management Studio. 2.
vCenter Configuration Manager Advanced Installation Guide 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 name. exec sp_dropserver @@SERVERNAME exec sp_addserver 'NewServerName', 'local' b. Click Execute. c.
Two-Tier Split Installation Prerequisites n Verify that the account you provide for the SQL Server Agent service has permission to log on 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.6 supports Active/Active SQL clusters. See the online Microsoft Developer Network for more information.
vCenter Configuration Manager Advanced Installation Guide Procedure 1. Click Start and select All Programs > Microsoft SQL Server 2008 R2 > 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.
Two-Tier Split Installation Verify the ASP Role 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 () 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.
vCenter Configuration Manager Advanced Installation Guide 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 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.
Two-Tier Split Installation Option Action Application Development Select these options: Health and Diagnostics Security Performance n ASP .NET n .
vCenter Configuration Manager Advanced Installation Guide 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 Category Role Service Common HTTP Features Static Content Default Document Directory Browsing HTTP Errors HTTP Redirection Application Development ASP.NET .
Two-Tier Split Installation a. In the Type menu, select http. b. In the IP address 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.
vCenter Configuration Manager Advanced Installation Guide 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.
Two-Tier Split Installation Wizard Page Action Installation Type Select New installation or add shared features. Product Key Verify that the product key is entered. License Terms Accept the license terms. Setup Role Select SQL Server Feature Installation. Feature Selection Select the following options.
vCenter Configuration Manager Advanced Installation Guide 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 HTTPS is 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.
Two-Tier Split Installation 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. Option Action Virtual Directory Set to ReportServer. IP Address Set to All Assigned (Recommended). TCP Port Set to 80 if you are not using HTTPS. SSL Certificate Not 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.
vCenter Configuration Manager Advanced Installation Guide 4. In the file, locate the block. The block resembles the following example. ... 5. Remove any existing parameters and add the parameter to the XML element. The modified block resembles the following block.
Two-Tier Split Installation Procedure 1. Log in to your Windows Server 2008 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 SQL Server 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.
vCenter Configuration Manager Advanced Installation Guide 10. Verify whether SSRS is running on the SQL Server 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 and . c. Add and . The default location for the configuration file is C:\Program Files\Microsoft SQL ServerReportingServicesInstance\Reporting Services\Repor
Two-Tier Split Installation 16. In Windows Explorer, update the configuration files. a. Open the configuration file at Windows\System32\inetsrv\config\applicationhost.config and locate the 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.
vCenter Configuration Manager Advanced Installation Guide Procedure 1. Download and install SQL XML 4.0 and SP1, X64 Package. 2. Download and install SQL Server 2008 R2 Command Line Utilities, which includes the SQLCMD utility, X64 Package (SqlCmdLnUtils.msi). The SQL Command Line Tools in the SQL Server 2008 R2 Feature Pack are required on the combined VCM Collector and Web server. 3. Download and install the SQL Server 2008 R2 Native Client, X64 Package (sqlncli.msi).
Three-Tier Split Installation 10 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 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.
vCenter Configuration Manager Advanced Installation Guide 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 page 20.
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.
vCenter Configuration Manager Advanced 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.
Three-Tier Split Installation 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. Procedure 1. Click Start and select All Programs > Administrative Tools > Server Manager. 2.
vCenter Configuration Manager Advanced Installation Guide 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 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 or Enterprise edition of SQL Server.
Three-Tier Split Installation Wizard Page Action Installation Type Select New installation or add shared features. Product Key Verify that the product key is entered. License Terms Accept the license terms. Setup Role Select SQL Server Feature Installation. Feature Selection Select the following features.
vCenter Configuration Manager Advanced Installation Guide What to do next n Reboot the database server machine. Verify and Configure the SQL Server Properties To ensure that SQL Server will operate with VCM, verify the SQL Server 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.
Three-Tier Split Installation Procedure 1. Click Start and select All Programs > Microsoft SQL Server 2008 R2 > 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.
vCenter Configuration Manager Advanced Installation Guide Select the SQL Server Agent Service Account SQL Server Agent is a service that runs scheduled jobs in SQL Server 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.
Three-Tier Split Installation Procedure 1. Click Start and select All Programs > Microsoft SQL Server 2008 R2 > 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 dedicated Web server.
vCenter Configuration Manager Advanced Installation Guide components are installed. n Windows Process Activation Service n Process Model n .NET Environment 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.
Three-Tier Split Installation 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 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.
vCenter Configuration Manager Advanced Installation Guide Role Service Category Role Service Management Tools IIS Management 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. Configure the IIS 7.5 Settings IIS settings configure the information required for requests to communicate with a Web site.
Three-Tier Split Installation Option Action Forms Authentication Set 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 () and expand Roles. 3. Click Web Server (IIS). 4. Scroll to Role Services. 5.
vCenter Configuration Manager Advanced Installation Guide Access to Patch Download Folder for Windows Patch Deployment Grant the Collector service access to the patch download folder to download patches during Windows patch deployment. During Windows patch deployment in a three-tier split installation, you must download the Windows patches immediately. If you download the patches during the patch deployment, the patches are not downloaded to the Web server.
Three-Tier Split Installation What to do next Prepare SQL Server Reporting Services (SSRS) to generate VCM reports. See "Installing and Configuring SSRS on the Web Server" on page 102. Installing and Configuring SSRS on the 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.
vCenter Configuration Manager Advanced Installation Guide Install SQL Server Reporting Services In a three-tier installation configuration, for the Web server to generate VCM reports, install SQL Server Reporting Services (SSRS). Prerequisites n Back up your SSRS key. See "Back Up Your SSRS Key" on page 102. n Disable the Internet Explorer Protected Mode. See "Disable IE Protected Mode for SSRS" on page 102.
Three-Tier Split Installation Wizard Page Action Instance Select Default Instance. If an instance of SQL Server is not installed, the installation Configuration creates a default instance. If an instance of SQL Server is installed, select Named Instance and assign a name. Disk Space Review the disk usage summary. Requirements Server Click Use the same account for all SQL Server services.
vCenter Configuration Manager Advanced Installation Guide Procedure 1. On your Web server, start SQL Server 2008 R2 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 2008 R2 Reporting Services. 2. Update the SQL Server database. a. In the navigation pane, click Database and click Change Database. b.
Three-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 SQL Server Reporting Services. 6. Click Exit to close SQL Server 2008 R2 Reporting Services Configuration Manager. 7. Reboot the Web server.
vCenter Configuration Manager Advanced Installation Guide ... 6. Save the configuration file. 7. Start the SSRS service. What to do next To authenticate VCM reports with Kerberos, see "Configure Kerberos Authentication" on page 107. Configure Kerberos Authentication The Kerberos network protocol uses secret-key cryptography to ensure security in your VCM applications.
Three-Tier Split Installation 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.
vCenter Configuration Manager Advanced Installation Guide 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
Three-Tier Split Installation Procedure 1. On the Web server, in the Control Panel click System and Security. 2. Click System. 3. Click Change settings. 4. Select the Advanced tab. 5. Click Environment Variables. 6. In the User variables area, click New. 7. Type a name for the environment variable and enter the following value: C:\Program Files\Microsoft SQL Server\100\Tools\Binn 8. Click OK to close the New User Variable dialog box. 9.
vCenter Configuration Manager Advanced Installation Guide 3. Download and install the SQL Server 2008 R2 Native Client, X64 Package (sqlncli.msi). The Native Client from the SQL Server 2008 R2 Feature Pack is required on the Web server and the VCM Collector. 4. Reboot the VCM Collector. Install the .NET Framework To support library and language interoperability, the VCM Collector must have the required versions of the .NET Framework installed. VCM 5.6 requires the .NET 3.5.1 Framework.
Three-Tier Split Installation Verify the ASP.NET Role 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 () 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.
vCenter Configuration Manager Advanced Installation Guide Procedure 1. On the VCM Collector, click Start > Run, type mmc, and click OK to open the Microsoft Management Console. a. Select File > Add/Remove Snap-In. b. Select Certificates and click Add. c. Select Computer Account and click Next. d. In the Select Computer dialog box, select Local Computer and click Finish. e. Click OK to add the snap-in to Microsoft Management Console. 2. In the navigation pane, click Certificates > Personal > Certificates.
Three-Tier Split Installation a. Select File > Add/Remove Snap-In. b. Select Certificates and click Add. c. Select Computer Account and click Next. d. In the Select Computer dialog box, select Local Computer and click Finish. e. Click OK to add the snap-in to Microsoft Management Console and close the Add or Remove Snap-ins dialog box. 4. In the navigation pane, click Certificates > Personal > Certificates. 5. In the center pane, right-click the VCM certificate and select All Tasks > Import. a. Click Next.
vCenter Configuration Manager Advanced Installation Guide 115 VMware, Inc.
11 Installing VCM After you perform the system prerequisite tasks and configure your installation configuration, understand the components to select during VCM installation, enable DCOM and the required ports, then use the installation image to start Installation Manager and install the appropriate VCM components on the physical and virtual machines in your installation configuration. For a single-tier installation configuration, install all of the available components.
vCenter Configuration Manager Advanced Installation Guide DCOM and Port Requirements for VCM SQL Server must communicate with the VCM Collector in split installations to submit jobs and control the Collector service. Before you install VCM, you must enable DCOM and the required port. n On the VCM Collector, enable DCOM. Use the built-in DCOM rule named COM+ Network Access (DCOM-In). n On the database server, enable port 1433. For more information, see Microsoft TechNet online.
Installing VCM Prerequisites n Review the list of supported platforms. See the VCM Installation Guide. n If you are migrating a version of VCM to VCM 5.6, a SQL Server version to 2008 R2, or a 32-bit environment to a 64-bit environment, see the VCM Installation Guide. n Obtain the installation package from the Download VMware vCenter Configuration Manager Web site or use the VCM 5.6 CD CAUTION When the installation requires the domain name for the database server, use the NetBIOS short form name.
vCenter Configuration Manager Advanced Installation Guide n Remote_Command_Files: Provides access to the Windows remote command files that are required to run remote commands in VCM. n Reports: Provides access to VCM reports, which include AD, UNIX, Licensing, Provisioning, VCM Patching, Virtualization, and so on. n SCAP: Provides access to the SCAP import and export files used to assess your managed machines against SCAP benchmarks.
Installing VCM Procedure 1. Browse to C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys. This path is the default location for your private keys. This path might differ depending on your organizational policies. 2. Expand the MachineKeys folder. The key that matches the date and time when you generated the certificate during installation is most likely the correct key. Because another reliable method does not exist to identify the key, use the date and time. 3. Right-click the key file and click Properties.
vCenter Configuration Manager Advanced Installation Guide Procedure 1. Click Start and select Administrative Tools > Internet Information Services (IIS) Manager. 2. Expand the server node and the Sites node. 3. Right-click Default Web Site and select Edit Permissions. 4. Click Security and verify that the user is listed with full rights or is a member of the Administrators group. What to do next Configure SQL Server database file growth and database recovery settings to tune your VCM database.
Configuring SQL Server for VCM 12 VCM relies heavily on its SQL databases for operation. You must update the default settings to optimize SQL Server performance. These settings include the SQL Server database settings, processor settings, and the Input/Output (I/O) configuration. To ensure that VCM runs at peak performance and requires little operator intervention during its lifecycle, set up a routine maintenance plan. See the VCM Administration Guide.
vCenter Configuration Manager Advanced Installation Guide SQL Server Processor Settings In multiprocessor environments, you must configure the SQL Server use of the processors. To do this, you reserve a processor by removing it from SQL Server, to be used for other functions such as the VCM Collector service and Internet Information Services (IIS). Because IIS cannot make use of processor affinity in multiprocessor machines, it uses them all equally.
Configuring SQL Server for VCM Because SQL Server is extremely disk-write intensive, performance suffers when SQL is configured with RAID 5. Understanding the RAID levels can help SQL database administrators configure the disk IO subsystem in the most efficient manner. n RAID 0. Striping Without Parity. In this configuration, each block of data is written to each disk in the array in a circular order, which means each disk in the array holds only a portion of the total data written.
vCenter Configuration Manager Advanced Installation Guide Disk Interface and Disk Drive Performance In addition to selecting the appropriate RAID configuration, consider the disk interface and disk drive performance. VCM data storage needs are usually low enough relative to commonly available drives that the smallest drives are sufficient.
Configuring SQL Server for VCM more than twice the number of processors in the system for more than very short periods of time. When viewing this counter, a logical drive that is also used by the page file might show high queuing due to insufficient RAM, but the counter can be useful to determine whether disk subsystem resources are appropriate and whether the resources are optimally arranged, such as disks per channel, RAID type, and so on.
vCenter Configuration Manager Advanced Installation Guide 127 VMware, Inc.
Upgrading or Migrating VCM 13 Upgrade or migrate your existing VCM environment to VCM 5.6, which supports 64-bit environments that include 64-bit hardware, 64-bit Windows Server 2008 R2 and SP1, and SQL Server 2008 R2 and SP1. Determine whether your VCM environment requires an upgrade or a migration. The prerequisites and steps differ depending on whether you perform an upgrade or a migration of VCM. CAUTION VCM 5.6 does not include the Patch Administrator role.
vCenter Configuration Manager Advanced Installation Guide Procedure n "Upgrade VCM" on page 129 An upgrade to VCM 5.6 uses an existing VCM Collector installation. You can upgrade a 64-bit environment that is running VCM 5.3 or earlier to VCM 5.6. n "Upgrade Existing Windows Agents" on page 130 Use the Upgrade Agent wizard to upgrade the Agent files on one or more Windows machines. If you are upgrading VCM from 5.4, an upgrade to your Windows Agents is not required.
Upgrading or Migrating VCM Upgrade Existing Windows Agents Use the Upgrade Agent wizard to upgrade the Agent files on one or more Windows machines. If you are upgrading VCM from 5.4, an upgrade to your Windows Agents is not required. The upgrade process uses the current settings of the Agent installed on the Windows machine. For example, if the Agent uses DCOM, or HTTP on port 26542, the upgrade process retains that setting. This process will not upgrade components that do not require an upgrade.
vCenter Configuration Manager Advanced Installation Guide Procedure 1. Click Administration. 2. Select Settings > General Settings > VCM Remote. 3. Select the Will Remote automatically upgrade old Remote clients? setting. 4. Click Edit Setting and select Yes. When this setting is enabled, the next contact between the client and server automatically downloads and installs the upgrade files and upgrades the VCM Remote client software on the client machine.
Upgrading or Migrating VCM The Agent Upgrade - Local Package UNIX remote command upgrades existing UNIX Agents when the Agent package exists locally or in a remote location that is accessible by the target machine, such as on a file share. Prerequisites n Install the VCM UNIX Agent on the managed machines to upgrade. n Determine which Agent version is installed on a UNIX machine. Click Administration and select Machines Manager > Licensed Machines > Licensed UNIX Machines. Procedure 1.
vCenter Configuration Manager Advanced Installation Guide What to do next Upgrade your UNIX Agents using a remote package. See "Upgrade UNIX Agents Using a Remote Package" on page 133. Upgrade UNIX Agents Using a Remote Package Use VCM remote commands and a remote Agent package to upgrade the VCM UNIX Agent on the UNIX platforms in your environment. The UNIX Agents use Transport Layer Security (TLS) and the Enterprise Certificate is embedded in the Agent package.
Upgrading or Migrating VCM Upgrading Virtual Environments Collections VCM 5.5 and later collect data directly from instances of vCenter Server, vCloud Director, and vShield Manager using a Managing Agent. See the VCM Administration Guide. To upgrade your virtual environment,you might upgrade the Windows Managing Agent, the vSphere Client VCM Plug-In, or the Agent Proxy. Upgrade the Managing Agent A Managing Agent is a Windows machine on which the VCM 5.
vCenter Configuration Manager Advanced Installation Guide What to do next Register the new vSphere Client VCM Plug-In. See the VCM Administration Guide. Upgrading Agent Proxy Machines When you upgrade a Collector to VCM 5.6, the Agent Proxy on the Collector is automatically upgraded and the Agent Proxy protected storage and user account configuration settings are preserved.
Upgrading or Migrating VCM Procedure 1. On your VCM Collector, click Administration. 2. Select Machines Manager > Additional Components > Agent Proxies. 3. In the Agent Proxies data grid, select the machines on which to upgrade the Agent Proxy. 4. Click Upgrade. 5. On the Upgrade Agent Proxies Machines page, select an action and click Next. Option Description All Machines Runs the process on all eligible machines. Selected Machines Only Runs the process on all machines listed in the lower pane.
vCenter Configuration Manager Advanced Installation Guide installed, you must run ProvisioningProductInstall.exe from the VCM Collector. n If you previously used this Agent Proxy to collect data from your upgraded Collector, the first collection might fail because of password encryption. If the collection fails, reset the VM Host password. You can set the password for multiple hosts at the same time. Click Administration and select Machines Manager > Licensed Machines > Licensed ESX/ESXi Hosts.
Upgrading or Migrating VCM For a migration, you must update your hardware to 64-bit, update the operating system to the 64-bit Windows Server 2008 R2 operating system, update to SQL Server 2008 R2, and update SQL Server Reporting Services. Then you can migrate your existing VCM, SCM, or ECM installation to your new VCM 5.6 environment. Prerequisites Before you migrate any part of your existing VCM environment to VCM 5.6, you must perform the prerequisites. See "Prerequisites to Migrate VCM" on page 138.
vCenter Configuration Manager Advanced Installation Guide n Back up your databases. See "Back Up Your Databases" on page 139. n Back up the CMFILES$ share. See "Back up Your Files" on page 139. n Back up any files that you used to customize your Collector. n Back up any reports that you exported to a non-default location. n Back up your certificates. See "Export and Back up Your Certificates" on page 140. n Verify that all jobs have finished running.
Upgrading or Migrating VCM differs. 2. Back up any files used to customize your Collector. 3. Back up any reports that exist in a location other than the default location. Export and Back up Your Certificates Export and back up your VCM Collector and Enterprise certificates. Procedure 1. On your VCM Collector, click Start and click Run. Type mmc.exe. 2. In the Console window, click File and select Add/Remote Snap-in. 3. In the Add/Remote Snap-in dialog box, click the Standalone tab and click Add. 4.
vCenter Configuration Manager Advanced Installation Guide Procedure 1. Move the VCM database to a prepared machine that has 64-bit SQL Server 2008 R2 installed. 2. On the prepared machine, start SQL Server Management Studio. 3. Attach the database to SQL Server 2008 R2. 4. Confirm that the sa account or the VCM service account is the owner of the newly attached database. What to do next Install VCM 5.6. See "Use Installation Manager to Install VCM" on page 117.
Upgrading or Migrating VCM Migrate a 32-bit Environment Running VCM 5.3 or Earlier to VCM 5.6 Migrate an existing 32-bit Collector to VCM 5.6. A migration to VCM 5.6 requires you to prepare new hardware and software for your environment and install the required software components.
vCenter Configuration Manager Advanced Installation Guide CAUTION When you begin the VCM installation, do not select the Repair option unless you are directed by VMware Technical Support. The repair process requires access to your original installation media to check for and replace missing files and settings. When the installation begins, VCM Foundation Checker gathers information about the Collector machine. If errors occur, you must resolve them before you can proceed. 8.
Upgrading or Migrating VCM Prerequisites n Understand the scenarios to migrate your VCM environment to VCM 5.6. See "Upgrading or Migrating VCM" on page 128. n Perform the prerequisite steps to migrate your VCM environment to VCM 5.6. See "Prerequisites to Migrate VCM" on page 138. n Understand how to detach and attach a SQL server database in SQL Server Management Studio. See the online Microsoft MSDN Library. n Understand how to use the sp_changedbowner stored procedure.
vCenter Configuration Manager Advanced Installation Guide new Remote virtual directory as used in your previous installation. If you change the Remote virtual directory name, you must update all corresponding Agents to use the new virtual directory. 10. Select your existing databases to migrate them to VCM 5.6. If Installation Manager requests that you create a new database, select the previous wizard page and verify that your existing database, which you attached, is selected. 11.
Upgrading or Migrating VCM CAUTION Before you begin the migration, to avoid any potential loss of data you must perform the prerequisite steps to back up your files, including the VCM databases, the CMFILES$ share, any files used to customize the VCM Collector, reports that are exported to a non-default location, and your certificates. Prerequisites n Understand the scenarios to migrate your VCM environment to VCM 5.6. See "Upgrading or Migrating VCM" on page 128.
vCenter Configuration Manager Advanced Installation Guide When the installation begins, VCM Foundation Checker gathers information about the Collector machine. If errors occur, you must resolve them before you can proceed. 8. Make sure that you select all of the components for installation. If a component cannot be upgraded due to an invalid upgrade or an incomplete copy of the install image, Installation Manager clears the check box and displays a message. 9.
Upgrading or Migrating VCM Procedure 1. On your VCM Collector, reinstall the software that was installed before you started the migration. Install the software in the order listed. a. SQL Server 2005 b. SQL Server Reporting Services, 32-bit version c. SQL Server 2005 SP3 d. VMware VCM 5.3, EMC Ionix SCM 5.0 or later, or Configuresoft ECM 4.11.1 or later 2. Use SQL Server Management Studio Object Explorer to connect the databases from your backed up copies. 3. Recopy the files to the CMFILES$ share.
vCenter Configuration Manager Advanced Installation Guide 149 VMware, Inc.
Maintaining VCM After Installation 14 Perform routine maintenance on your VCM configuration management database to keep VCM running smoothly and performing efficiently. Maintenance includes configuring settings specific to your environment, configuring the database file growth and recovery settings, creating a maintenance plan, and incorporating the database into your backup and disaster recovery plans. Prerequisites n Install VCM. See "Use Installation Manager to Install VCM" on page 117.
vCenter Configuration Manager Advanced Installation Guide Procedure 1. In VCM, select Administration. 2. Click Settings and review the available general and product-specific configuration settings to customize for your environment. 3. Click Windows and configure the settings to communicate with the VCM Windows Agent for your collection types. Option Description Agent - General Configures the general characteristics of the Windows Agent operation.
Maintaining VCM After Installation Option Description Network Authority Configures and manages the available domains, available accounts, and assigned accounts by domain or machine group, and the proxy servers used during the HTTP Agent installation. What to do next n See the online help for each product component for more information about the specific settings. n Configure the database file growth. See "Configure Database File Growth" on page 152.
vCenter Configuration Manager Advanced Installation Guide n Simple Recovery: The VCM database settings are set to Simple by default. The transaction log retains enough information to recover the database to a known good state when the server restarts. Transaction log backups are not allowed and point-in-time recovery is not available. Simple recovery causes the transaction log file to grow.
Maintaining VCM After Installation Procedure 1. Click Start. 2. Select All Programs > Microsoft SQL Server 2008 R2 > SQL Server Management Studio. 3. Expand the SQL instance. 4. Expand Databases. 5. Right-click VCM and select Properties. 6. Click Options. 7. In the Recovery model drop-down, select the recovery model and click OK. What to do next Create a maintenance plan for SQL Server 2008 R2. See "Create a Maintenance Plan for SQL Server 2008 R2" on page 154.
vCenter Configuration Manager Advanced Installation Guide a. Click the Databases drop-down menu. b. Select the following databases and click OK. n VCM n VCM_Coll n VCM_Raw n VCM_UNIX You must select the VCM_Raw database, because it contains transient data that the other databases consume. c. Select Include indexes and click Next. 11. On the Define Rebuild Index Task page, define how the maintenance plan will rebuild the Index. a. Click the Databases drop-down menu. b.
Maintaining VCM After Installation n You have established a routine maintenance plan to ensure that SQL Server 2008 R2 continues to operate efficiently. To view, save, copy, or send the report, click Report and select an option. n Use VCM normally. Incorporate the VCM Database into Your Backup and Disaster Recovery Plans Consider your VCM database as any other SQL database in your environment and incorporate the database into your corporate strategy for backup and disaster recovery. VMware, Inc.
vCenter Configuration Manager Advanced Installation Guide 157 VMware, Inc.
Hardware and Operating System Requirements for Managed Machines 15 VCM collects data from Windows and UNIX machines that VCM manages. The VCM Agent is supported on many different machine and operating system types. VCM Agent Support on Non-English Windows Platforms If you install the VCM Agent on non-English (non-ENU) Windows machines, and collect data from these machines, review the following dependencies and limitations.
vCenter Configuration Manager Advanced Installation Guide Table 15–1.
Hardware and Operating System Requirements for VCM Managed Machines Agent Supported Operating System Supported Hardware Platform SUSE Linux Enterprise Server (SLES) 10.3–10.4, 11.0–11.2 x86 and x64 Platforms To Be Upgraded SUSE Linux Enterprise Server (SLES) 10.0–10.2 (up to 5.5.0 Agent only) Mac OS X (Servers and Workstations) Mac OS X 10.6 (up to 5.5.0 Agent only) Intel-based Apple platforms only Mac OS X 10.
vCenter Configuration Manager Advanced Installation Guide Supported OS Provisioning Target Systems Use OS provisioning to install the following operating system on machines with at least 1GB RAM. Table 15–2. 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.
Hardware and Operating System Requirements for VCM Managed Machines Table 15–4. Software Provisioning Component Requirements Software Provisioning Component Description Requirements VMware vCenter Application used to the create the software packages. Configuration Manager Package Studio .NET 3.5.1 or higher Software Repositories File system used to store the shared software packages. .NET 3.5.1 and IIS 6, 7, or 7.
vCenter Configuration Manager Advanced Installation Guide n Red Hat RHEL 5 and 6 n SUSE SLES 10.0–10.4 and 11.0–11.2 For information about the new content format, see the VCM Administration Guide or the VCM online help. 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.
Hardware and Operating System Requirements for VCM Managed Machines When collecting data from ESX Servers, you must configure at least one VCM Agent Proxy machine. You can configure the Collector as the Agent Proxy or configure standalone Agent Proxy machines. The Collector communicates with the Agent Proxy and the Agent Proxy then directly communicates with the ESX Servers using SSH and/or Web Services for necessary data collection actions.
vCenter Configuration Manager Advanced Installation Guide vCenter Operations Manager Integration Features You can configure the following versions vCenter Operations Manager with VCM 5.6. Different integrated versions of vCenter Operations Manager support different features. vCenter Operations Manager Version VCM Features in vCenter Operations Manager 5.0.x VCM change events 5.
Hardware and Operating System Requirements for VCM Managed Machines Operating System Version Hardware Platform FIPS Module Certificate Windows Server 2008 R2 RTM Windows All 2000 x86 76 Cryptographic RSA Enhanced Validated Modules The Microsoft Cryptography API (CAPI) supports the following validated versions of RSA enhanced modules, and the operating systems for which the testing is valid. Table 15–8.
vCenter Configuration Manager Advanced Installation Guide FIPS for VCM Agent Proxies The VCM Agent Proxy uses the OpenSSL FIPS v1.1.2, which is validated to the 918 certificate. Agent Sizing Information The disk space requirements are fairly constant for a Windows, UNIX, Linux, Mac OS X, or AD managed machine that runs a VCM Agent. Each machine requires no more than 200MB to run an Agent. However, the recommended memory to run the HP-UX Agent is 1GB.
Hardware and Operating System Requirements for VCM Managed Machines Agent Type Installed File Size Data File Size Projected Data File Size Active Directory Agent VCM Agent +30MB See VCM Agent data file sizes The projected data file size is determined the same as the default Agent. VCM Remote Client VCM Agent +2MB (installs or upgrades Agent) See VCM Agent data file sizes The projected data file size is determined the same as the default Agent.
vCenter Configuration Manager Advanced Installation Guide UNIX and Linux Machines The projected data file sizing information for UNIX and Linux machines information can vary depending on your collection filter set and is determined by collected data types and actions. The size can vary from 10–20 MB to more than 100MB. The most likely data types to cause large data growth are File System-File Structure and System Logs.
Hardware and Software Requirements for the Operating System Provisioning Server 16 VCM operating system provisioning supports one instance of VCM with one or more instances of Operating System Provisioning Server (OS Provisioning Server). Configure the server to meet the requirements. Supported OS Provisioning Server Platform The OS Provisioning Server can be installed on Red Hat Enterprise Linux version 5.2, 5.4, or 5.5, 32-bit or 64-bit.
vCenter Configuration Manager Advanced Installation Guide OS Provisioning Server Software Requirements For OS provisioning to function correctly, the machine on which you are installing the OS Provisioning Server requires the presence of some packages, while others conflict and are not allowed. Verify the required and disallowed packages, making certain that the required packages are present and that any disallowed packages are removed.
Hardware and Software Requirements for the Operating System Provisioning Server n IP Address: 10.11.12.1 n Netmask: 255.255.255.0 OS Provisioning Network Port Usage During the installation of OS distributions, internal application and services must communicate between the OS Provisioning Server and the target machines. If there are firewalls or routers between the OS Provisioning Server and the target machines, they must be configured to allow the following ports. Table 16–1.
vCenter Configuration Manager Advanced Installation Guide Prerequisites n Identify the ports for which you must configure the firewall. See "OS Provisioning Server Network Requirements" on page 171. n Ensure that you do not accidentally lose your iptables changes. In the iptables-config file, determine whether IPTABLES_SAVE_ON_STOP or IPTABLES_SAVE_ON_RESTART are set to yes. Procedure 1. On the OS Provisioning Server, log in as root. 2. Change directory to /etc/sysconfig. 3.
Installing, Configuring, and Upgrading the OS Provisioning Server and Components 17 The Operating System (OS) Provisioning Server is a repository of imported OS distributions. It manages the installation of the distributions on target machines. The installation of the distributions is part of the OS provisioning function in VCM, which identifies machines that can be provisioned and initiates the OS provisioning on the target machines.
vCenter Configuration Manager Advanced Installation Guide Procedure 1. "Install the Operating System Provisioning Server" on page 175 Using the supplied media or media images, install the OS Provisioning Server and run the command to create the distribution repository. 2.
Installing, Configuring, and Upgrading the OS Provisioning Server and Components 7. Click Close when the installation finishes. 8. In the Nixstaller window, click Finish. 9. Run the service FastScale status command to verify that the installation finished. A successful installation displays the following results. PID values vary. rsyslogd (pid 3335) is running... fsmesgd (pid 3517) is running... fsrepod (pid 3683) is running... fsadmin (pid 12618) is running...
vCenter Configuration Manager Advanced Installation Guide CAUTION The uninstall process removes the application and deletes all the data in the database. Procedure 1. On the OS Provisioning Server, log in as root. 2. Mount the OS Provisioning Server ISO by attaching or mounting the image. 3. Type cd / to change the directory to the location of the image. 4. Run the ./UNINSTALL-ME command to uninstall the application. 5. Type yes.
Installing, Configuring, and Upgrading the OS Provisioning Server and Components Procedure 1. Open /opt/FastScale/etc/dhcpd.conf. 2. Configure the settings for your environment. Option Description subnet The IP address subnet of the private network interface. Default value is 10.11.12.0. netmask The netmask of the subnet. Default value is 255.255.255.0. range The range of allocated IP addresses for the provisioned nodes. Default value is 10.11.12.100–10.11.12.200.
vCenter Configuration Manager Advanced Installation Guide Procedure 1. On the OS Provisioning Server, log in as root. 2. Run ospctrl --showconfig. The following results verify that the TFTP and Apache services are running. TFTP - Configured on * - Running Apache - Configured on * - Running 3. Run ospctrl --configure --privateip . The configuration process runs. The IP address is 10.11.12.1. Shutting down FStftpd: [ OK ] Starting FStftpd: [ OK ] TFTP - Configured on 10.11.12.
Installing, Configuring, and Upgrading the OS Provisioning Server and Components 4. From the Windows command line, run bin\osp --osphome="c: -deploymenturl= --waik=". Option Description osphome The path to the files copied from the OS Provisioning Server. For example, c:\Program Files\osp\deployment. If you run the command from the directory, you can use --osphome=.
vCenter Configuration Manager Advanced Installation Guide Import Distributions into the OS Provisioning Server Repository To install operating system distributions on target machines, you must import the distributions into the OS Provisioning Server repository. For supported operating systems, see "Hardware and Operating System Requirements for VCM Managed Machines" on page 158. Prerequisites Confirm that you installed OS Provisioning Server and configured all the options.
Installing, Configuring, and Upgrading the OS Provisioning Server and Components What to do next Import Windows distributions into your repository. See "Import Windows Distributions" on page 182. Import Windows Distributions Windows distributions are the operating system installation files that you import into the OS Provisioning Server repository. After importing the distribution, you use VCM provisioning actions to install the operating system on target machines.
vCenter Configuration Manager Advanced Installation Guide For example, Windows. You must provide a unique family name to import different operating systems in the same family. No other family can exist with the same combination of name, version, and architecture values. 5. Type the Family Version. For example, 2008R2. 6. Type the Family Architecture. For example, either i386 or x86_64. 7. Type the Provenance. For example, CD, hotfix, or SP. 8.
Installing, Configuring, and Upgrading the OS Provisioning Server and Components Prerequisites n Verify that the distributions you are importing do not include spaces in the filenames. Before you import, remove the spaces or replace them with underscores. n Confirm that the current OS Provisioning Server IP address is correct for your production environment. You cannot change the OS Provisioning Server IP address at a later time.
vCenter Configuration Manager Advanced Installation Guide 6. RedHat Enterprise Linux 5.0 7. Suse Linux Enterprise 11.1 8. Suse Linux Enterprise 10.3 If you select the incorrect distribution, you can import the distribution, but you cannot install it. The distribution is imported. What to do next Use VCM to install your distributions on target machines. See the VCM Administration Guide.
Installing, Configuring, and Upgrading the OS Provisioning Server and Components n Add the missing required packages back into the ISO and re-import it into the repository. Run the Provision wizard again to create a new configured session with the updated distribution. The installation of the distribution on the target machines will proceed without an error and the required list remains as it was provided in the OS Provisioning Server.
vCenter Configuration Manager Advanced Installation Guide fsmesgd (pid 3517) is running... fsrepod (pid 3683) is running... fsadmin (pid 12618) is running... dhcpd is stopped tftpd (pid 12057) is running fsjobd (pid 4237) is running... fshinvd (pid 4249) is stopped... An unsuccessful installation displays FastScale: unrecognized service or several services are not running. Review the logs to determine possible problems. 10.
Installing, Configuring, and Upgrading the OS Provisioning Server and Components Managing the OS Provisioning Server System Logs The OS Provisioning Server log files are located in the /opt/FastScale/logs and /var/log directories. You must monitor the space used and truncate the files if they begin to consume more disk space on the server than you have space to store. Table 17–2. Log File Locations Directory File Name Description /opt/FastScale/logs fsadmin.err Messages from the Apache Web server.
vCenter Configuration Manager Advanced Installation Guide ospctrl Command Options Use the ospctrl command-line options to configure your TFTP and Apache services with the OS provisioning private IP address and to back up and restore the OS Provisioning Server repository and distribution files. Table 17–3. ospctrl Command Options 189 Option Description --help Displays and describes the ospctrl options.
Index 3 32-bit environment migrations 137 A account database server 55, 82, 107 Kerberos, database server 55, 82, 107 accounts clustered servers 46, 70, 95 administrator rights 21 agent 24 communication settings 151 disk sizing 167 EXE installer 32 folder 24 hardware 158 software provisioning 161 MSI installer 32 non-English Windows platforms 158 OS platform support 10 patch assessment 162 platforms supported 131 software software provisioning 161 UNIX/Linux upgrade 132-133 upgrade for UNIX/Linux 131 upgr
vCenter Configuration Manager Advanced Installation Guide provisioning, operating system 174-175 SQL Server 122 SQL Server processor settings 123 SSRS 79 SSRS, two-tier 77, 103 Web components 37, 47, 62, 72, 87, 96 Web Service URL 53, 79, 105 content architecture for patch assessment 162 CPU requirements VCM on virtual machine 27 Cryptographic DSS Enhanced Modules 166 Cryptographic RSA Enhanced Modules 166 Cryptographic Service Providers 165 customize VCM 150 D dashboard errors in SSRS 51, 102 data collec
Index K Kerberos on database server 54, 81, 107 Kerberos network protocol 54, 81, 107 key backup for SSRS 51, 77, 102 keys SQL Server Reporting Service (SSRS) 77, 102 L language packs for Windows machines 158 licensing servers, workstations 131 Linux, custom distribution provisioning, operating system 185 Linux/ESX provisioning, operating system import 183 local administration rights 21 local package UNIX/Linux agent upgrade 132 locale settings 39, 64, 89 logs provisioning, operating system 188 M Mac OS
vCenter Configuration Manager Advanced Installation Guide importing basicimport 185 install 174-175 logs 188 network 171 ospctrl commands 189 requirements 170 server platform 170 server requirements 170 software 171 supported platforms 161 system requirements 170 TFTP 179 uninstall 176 upgrade 186 Windows boot image 179 public key infrastructure 30 R RAID levels for SQL Server 123 recover collector 147 recovery models for database 152 recovery plan 156 recovery settings configure 153 register vSphere Clie
Index sysadmin 46, 70, 95 system checks 20 system prerequisites 20 T TFTP provisioning, operating system 179 three-tier split installation 18, 86 prerequisites 87 procedure 87 throughput with SQLIO 126 TLS 119 server authentication 30 trust certificate 31 chain 31 two-tier installation procedure 61 two-tier split installation 18, 60 prerequisites 61 U uninstall provisioning, operating system 176 troubleshooting 117 uninstall agent 24 MSI installer 24 UNIX/Linux agent communication settings 151 data file
vCenter Configuration Manager Advanced Installation Guide 195 VMware, Inc.