VMware vCenter Configuration Manager 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 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 7 Achieving a Successful VCM Installation 9 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 Ove
vCenter Configuration Manager Installation Guide Configuring a Two-Tier Split Installation Environment Installation Prerequisites for Both Servers Install and Configure a Windows Server 2008 R2 Operating System Install the .
Contents Use SQLIO to Determine IO Channel Throughput Upgrading or Migrating VCM Upgrading VCM and Components Upgrade VCM Upgrade Existing Windows Agents Upgrade Existing VCM Remote Clients Red Hat Server and Workstation Licensing Upgrade Existing UNIX Agents Upgrading Virtual Environments Collections Upgrade the Managing Agent Upgrading the vSphere Client VCM Plug-In Upgrading Agent Proxy Machines Migrating VCM Prerequisites to Migrate VCM Migrate Only Your Database Replace Your Existing 32-Bit Environme
vCenter Configuration Manager Installation Guide OS Provisioning Server Network Requirements Provisioning Network Interface Configure the OS Provisioning Server Firewall 134 134 135 Installing, Configuring, and Upgrading the OS Provisioning Server and Components 137 Restricted Network Environment Install and Configure the OS Provisioning Server Install the Operating System Provisioning Server Uninstall the OS Provisioning Server Configure DHCP Configure a DHCP Server Other Than the OS Provisioning Server
About This Book The VCM Installation Guide describes the hardware and software requirements necessary for a successful VMware vCenter Configuration Manager (VCM) installation, and the steps to install VCM in all supported installation configurations.
vCenter Configuration Manager 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. 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.
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 Installation Guide For details about VCM Collector machines, see "Hardware Requirements for Collector Machines" on page 11 and "Software and Operating System Requirements for Collector Machines" on page 15. For details about VCM managed machines, see "Hardware and Operating System Requirements for VCM Managed Machines" on page 121. 10 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 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 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 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 17. To understand the requirements to upgrade or migrate your environment to the latest version of VCM, see "VCM Upgrades and Migrations" on page 16. VCM Upgrades and Migrations To upgrade your version of VCM to the current version, you must have VCM 5.
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 Installation Guide 18 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 Installation Guide n "Verify the VMware Application Services Account" on page 22 Verify that the VMware Application Services Account is a domain user. n "Verify the VCM Agent is Not Installed" on page 23 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.
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 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\System accoun
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 Installation Guide MsiExec.exe /X{7C51E2CA-C932-44EF-8B77-3C03356A24CC} d. If an Uninstall GUID registry key that references the VCM Agent does not exist, the Agent was installed using the manual installer. 4. Uninstall the VCM Agent. a. If the Agent was installed using the MSI installer, to uninstall the Agent click Start and click Run to execute the command line using the UninstallString registry value. An example value is as follows. MsiExec.
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 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 25.
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 27.
vCenter Configuration Manager Installation Guide 28 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 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 Installation Guide 32 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 Installation Guide Figure 8–2. Typical VCM Enterprise-Wide, Single-Server Installation 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.
Single-Tier Server Installation Procedure 1. "Install and Configure a Windows Server 2008 R2 Operating System" on page 35 To prepare your Windows machine for VCM installation, install the Windows Server 2008 R2 operating system on each Windows machine in your installation configuration and verify that the settings are configured for VCM operation. 2.
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.
Single-Tier Server Installation Procedure 1. On the Collector, click Start and select All Programs > Administrative Tools > Server Manager. 2. Expand Roles and click Web Server (IIS). 3. If the Web Server (IIS) role does not appear in the list of Roles, scroll to Role Services, click Add Role Services and add the Web Server (IIS) Role. When you installed IIS, the ASP Role Service, ASP.NET Role Service, and IIS ServerSideIncludes Role Service were installed. 4.
vCenter Configuration Manager Installation Guide 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.5 bindings on the VCM Collector machine to ensure that the settings are correct. Procedure 1. Click Start and select All Programs > Administrative Tools > Internet Information Services (IIS) Manager. 2.
Single-Tier Server Installation VCM operates with a Standard or Enterprise edition of SQL Server. You must install the 64-bit SQL Server 2008 R2, English (United States) version on your designated database server machine and verify that the settings are configured correctly for a VCM installation. For information about installing the VCM Collector on a non-English operating system, see the VMware knowledge base article at http://kb.vmware.com/kb/1035034.
vCenter Configuration Manager Installation Guide Wizard Page Action Feature Selection Select the following features. Instance Features: n Database Engine Services n Reporting 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. To view the detailed system configuration check report, click the link. Instance Select Default Instance.
Single-Tier Server Installation Verify the SQLXML Version SQLXML provides client-side XML functionality and enhancements to existing SQL features. SQLXML 4.0 SP1 is installed with SQL Server 2008 R2. Verify that the correct version is installed. Procedure 1. Click Start and click Control Panel. 2. Click Programs and select Programs and Features. 3. Verify that SQLXML 4.0 SP1 appears in the list of installed programs. 4. If SQLXML 4.0 SP1 does not appear, install it from the Microsoft Download Center.
vCenter Configuration Manager Installation Guide What to do next Review the DCOM and port requirements, and use VCM Installation Manager to install the VCM components. See "Installing VCM" on page 81. 42 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 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 What to do next Review the DCOM and port requirements, and use VCM Installation Manager to install the VCM components. See "Installing VCM" on page 81. Installation Prerequisites for Both Servers Perform the 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.
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.
Two-Tier Split Installation 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.
vCenter Configuration Manager 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.
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 features.
vCenter Configuration Manager Installation Guide What to do next n Reboot the database server machine. Verify the SQLXML Version SQLXML provides client-side XML functionality and enhancements to existing SQL features. SQLXML 4.0 SP1 is installed with SQL Server 2008 R2. Verify that the correct version is installed. Procedure 1. Click Start and click Control Panel. 2. Click Programs and select Programs and Features. 3. Verify that SQLXML 4.0 SP1 appears in the list of installed programs. 4. If SQLXML 4.
Two-Tier Split Installation The Windows machine that hosts the Web components must be running Internet Information Services (IIS) 7.5. IIS is installed when you install Windows Server 2008 R2. Verify the IIS 7.5 Role Services are Enabled Verify that the correct IIS 7.5 Role Services are enabled on the combined VCM Collector and Web server . Procedure 1. On the Collector, click Start and select All Programs > Administrative Tools > Server Manager. 2. Expand Roles and click Web Server (IIS). 3.
vCenter Configuration Manager Installation Guide 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.5 bindings on the combined VCM Collector and Web server to ensure that the settings are correct. Procedure 1.
Two-Tier Split Installation Procedure 1. Start the SQL Server 2008 R2 installation. 2. Perform the actions to install SQL Server Reporting Services. Wizard Page Action SQL Server Installation Center Click New installation or add features to an existing installation. Setup Support Click Install and verify that all of the rules pass. To view the detailed system Rules configuration check report, click the link. Setup Support Click Install to install the setup support files.
vCenter Configuration Manager Installation Guide Wizard Page Action Server Click Use the same account for all SQL Server services. Configuration n If you will not install SSRS on the combined VCM Collector and Web Server machine, enter the NT AUTHORITY\SYSTEM account and password. n If you will install SSRS on the combined VCM Collector and Web Server, use the Network Service account instead of NT AUTHORITY\SYSTEM. It is possible to use a domain account for SQL Server services.
Two-Tier Split Installation e. Verify that the authentication type is set to Current User – Integrated Security and click Test Connection. f. When the test message is successful, close the Test Connection dialog box and click Next. g. On the Database pane, enter a name for the Database and select the language as English (United States). h. Set the Report Server Mode to Native Mode and click Next. i.
vCenter Configuration Manager Installation Guide Update the RSReportServer.config file so that VCM can authenticate users who use the VCM Web console, and users can launch SSRS reports. To configure Basic authentication on the report server, edit the XML elements and values in the RSReportServer.config file. Procedure 1. On the Windows machine where you installed SSRS, locate the rsreportserver.config file. The default location is C:\Program Files\Microsoft SQL ServerReportingServicesInstance\Reporting Se
Two-Tier Split Installation In your two-tier split installation configuration, configure the Web server and VCM Collector components on the same machine. Prerequisites n If you did not install the complete set of Management Tools and support components earlier, verify that you can access the Microsoft Download Center, Microsoft SQL Server 2008 R2 Feature Pack to download and install the SQLCMD utility x64 package (SqlCmdLnUtils.msi). See the online Microsoft Download Center.
vCenter Configuration Manager Installation Guide 58 VMware, Inc.
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 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 Connect the database server machine, Web server machine, and VCM Collector machine to the domain.
Three-Tier Split Installation Install and Configure a Windows Server 2008 R2 Operating System To prepare your Windows machine for VCM installation, install the Windows Server 2008 R2 operating system on each Windows machine in your installation configuration and verify that the settings are configured for VCM operation. Prerequisites n Verify that the computer name settings for your Windows machine is a valid DNS machine name with no underscores.
vCenter Configuration Manager Installation Guide What to do next Ensure that the installation creates the VCM databases. See "Configuring the VCM Database Server" on page 62. 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 three-tier split installation configuration, the VCM database server resides on a dedicated machine. The databases include VCM, VCM_Coll, VCM_Raw, and VCM_UNIX.
Three-Tier Split Installation 6. If the role service is not installed, click Add Role Services and add the ASP.NET role service. Verify the SQLXML Version SQLXML provides client-side XML functionality and enhancements to existing SQL features. SQLXML 4.0 SP1 is installed with SQL Server 2008 R2. Verify that the correct version is installed. Procedure 1. Click Start and click Control Panel. 2. Click Programs and select Programs and Features. 3. Verify that SQLXML 4.
vCenter Configuration Manager Installation Guide Prerequisites n Obtain the SQL Server 2008 R2 Enterprise or Standard edition installation disk or verify access to a file share where the installer resides. Procedure 1. Start the SQL Server 2008 R2 installation. 2. Perform the following actions to install SQL Server 2008 R2 Enterprise or Standard edition. Wizard Page Action SQL Server Installation Center Click New installation or add features to an existing installation.
Three-Tier Split Installation Wizard Page Action Disk Space Review the disk usage summary. Requirements Server Click Use the same account for all SQL Server services and enter the NT Configuration AUTHORITY\SYSTEM account and password. It is possible to use a domain account for SQL Server services. A domain account might be required for split installations, because the SQL Server Agent might need access to the Collector for some activities.
vCenter Configuration Manager Installation Guide a. Select Windows Authentication mode, which is recommended. b. Although SQL Server and Windows Authentication mode is acceptable for VCM, select Windows Authentication mode, which is recommended. 5. Select and confirm the Database Settings page server properties. a. For Default index fill factor, type or select a percentage value, which specifies the amount of free space in each index page when the page is rebuilt.
Three-Tier Split Installation Procedure 1. Click Start and select All Programs > Administrative Tools > Server Manager. 2. Click Roles and verify that the Web Server (IIS) role appears. 3. If the Web Server (IIS) role does not appear, in the Roles Summary area, click Add Roles and add the Web Server (IIS) role. 4. On the Select Server Roles page, select Web Server (IIS) and select the Web Server components to add.
vCenter Configuration Manager Installation Guide Verify whether the IIS ServerSideIncludes 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 down to Role Services. 5. Locate IIS ServerSideIncludes and verify that the role service is installed. 6.
Three-Tier Split Installation Procedure 1. Click Start and select All Programs > Administrative Tools > Internet Information Services (IIS) Manager. 2. Expand , expand Sites, and click Default Web Site. 3. In the Default Web Site Home pane, locate the IIS options. 4. Double-click Authentication and set the authentication. Option Action Anonymous Authentication Set to Disabled. ASP.NET Impersonation Set to Disabled. Basic Authentication Set to Enabled.
vCenter Configuration Manager Installation Guide 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.
Three-Tier Split Installation What to do next n Reboot the Web server machine. Install SQL Server 2008 Utilities The SQL Command Line Tools in the SQL Server 2008 R2 Feature Pack are required on the Web server for a three-tier installation. This installation also requires SQLXML to provide client-side XML functionality and enhancements to existing SQL features. SQLXML 4.0 SP1 is installed with SQL Server 2008 R2.
vCenter Configuration Manager Installation Guide Back Up Your SSRS Key The rskeymgmt utility manages the symmetric keys used by a report server. This utility provides a way to delete encrypted content that can no longer be used if you cannot recover or apply the key. Use the Microsoft command-line utility to back up the symmetric key to an encrypted file. Prerequisites n See the online Microsoft Support center for details about how to use the rskeymgmt utility. Procedure 1.
Three-Tier Split Installation Prerequisites n Use the command-line utility to back up the SSRS key to an encrypted file. See "Back Up Your SSRS Key" on page 72. n Disable the Internet Explorer Protected Mode. See "Disable IE Protected Mode for SSRS" on page 72. 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.
vCenter Configuration Manager Installation Guide 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.
Three-Tier Split 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 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 .
Three-Tier Split Installation Verify the SQLXML Version SQLXML provides client-side XML functionality and enhancements to existing SQL features. SQLXML 4.0 SP1 is installed with SQL Server 2008 R2. Verify that the correct version is installed. Procedure 1. Click Start and click Control Panel. 2. Click Programs and select Programs and Features. 3. Verify that SQLXML 4.0 SP1 appears in the list of installed programs. 4. If SQLXML 4.0 SP1 does not appear, install it from the Microsoft Download Center.
vCenter Configuration Manager Installation Guide 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.
Three-Tier Split Installation Export. a. Click Next. b. On the Export Private Key page, select Yes, export the private key. c. In the Personal Information Exchange area, select Export all extended properties and click Next. 4. On the Password page, type the password for the certificate, type it again to confirm it, and click Next. Remember or record the password, because you must supply it during certificate import process on the Web server machine. 5.
vCenter Configuration Manager Installation Guide What to do next 80 n Review the DCOM and port requirements, and use VCM Installation Manager to install the VCM components. See "Installing VCM" on page 81. n Use the VCM Administration Guide to configure the VCM Remote Client. 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 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 The following directories in L1033\Files serve multiple purposes for users, administrators, and service accounts. n Discovery_Files: Provides access to text files that are used to discover or add machines manually. n ERD_Extracts: Provides access to the default directory that contains extracted emergency repair disk files. Backing up registry files requires the SE_BACKUP_NAME user right. n Exported Reports: Allows access to the exported reports.
vCenter Configuration Manager Installation Guide 84 VMware, Inc.
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 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 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 The Disk Queue Length value is the best initial indicator on whether a logical drive has sufficient throughput and access speed for the tasks being required. The Disk Queue Length should not typically be more than twice the number of processors in the system for more than very short periods of time.
vCenter Configuration Manager Installation Guide 90 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 Installation Guide Procedure n "Upgrade VCM" on page 92 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 93 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 Installation Guide Prerequisites Install the VCM Agent on the managed machines to upgrade. 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.
Upgrading or Migrating VCM Upgrade UNIX Agents Using a Local Package Use UNIX remote commands and the local Agent package to upgrade the VCM UNIX Agent on the UNIX platforms in your environment. 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.
vCenter Configuration Manager Installation Guide The Time of Day settings are based on your user time zone. All VCM jobs run based on the VCM database time zone. Account for the time and date differences between your VCM user time and your VCM database time. For example, if your VCM database server is in the Eastern time zone, and your VCM user is in the Pacific time zone, to run your job at midnight, enter 9 PM. 15. Click Next and Finish. What to do next Upgrade your UNIX Agents using a remote package.
Upgrading or Migrating VCM Procedure 1. Click Console. 2. Select UNIX Remote Commands > UNIX Agent Upgrade. 3. In the UNIX Agent Upgrade data grid, click the appropriate remote upgrade package for the operating system and version of the machines to upgrade. 4. Click Run and follow the wizard to send the remote command and upgrade package to the Agents on the selected machines. The Agent executes the upgrade package. What to do next Upgrade VCM for Virtualization.
vCenter Configuration Manager Installation Guide Upgrade the vSphere Client VCM Plug-In If your version of the vSphere Client VCM Plug-In is 5.3 or earlier, or if the URL to the VCM instance has changed, upgrade the vSphere Client VCM Plug-In. Prerequisites n Unregister the previous version of the vSphere Client VCM Plug-In. See "Unregister the Previous Version of the vSphere Client VCM Plug-In" on page 97. n Locate the procedure to upgrade VCM. See "Upgrading VCM and Components" on page 91.
Upgrading or Migrating VCM n "Use VCM to Upgrade an Agent Proxy Machine" on page 99 Use VCM to upgrade VCM for Virtualization on a non-Collector Agent Proxy Machine. If a new version of the Agent Proxy becomes available, the upgrade process installs the newer version on your Agent Proxy machine. n "Manually Upgrade an Agent Proxy Machine" on page 99 Manually upgrade VCM for Virtualization on a non-Collector Agent Proxy Machine.
vCenter Configuration Manager Installation Guide After the upgrade, all managed Windows machines include the VCM Agent extension for VCM Provisioning. Prerequisites n Upgrade your Collector to VCM 5.6. n Confirm that \VMware\VCM\AgentFiles\CMAgentInstall.exe is accessible from your nonCollector Agent Proxy machine. The path on the Collector machine is C:\Program Files (x86) \VMware\VCM\AgentFiles\CMAgentInstall.exe, or in the path relative to where you installed the software.
Upgrading or Migrating VCM Migrating VCM A migration to VCM 5.6 requires you to prepare new hardware and software for your environment, migrating the databases to the upgraded SQL Server, and moving the VCM files. To prepare your environment for VCM 5.6, you can choose to migrate only your databases, replace an existing 32-bit environment, migrate an existing 32-bit or 64-bit environment, or migrate a split installation. VCM 5.6 supports the following migration paths.
vCenter Configuration Manager Installation Guide n Verify that your VCM version to migrate is either VMware VCM 5.3, EMC Ionix SCM 5.0 or later, or Configuresoft ECM 4.11.1 or later. n If your VCM Collector is installed on a 32-bit Windows machine, understand the system requirements for VCM 5.6. See "Software and Operating System Requirements for Collector Machines" on page 15. n Verify that an existing 32-bit environment includes SQL Server 2005 and SP3.
Upgrading or Migrating VCM Back up Your Files Before you migrate an existing VCM environment to VCM 5.6, back up your files to avoid any potential loss of data. 1. Back up the entire content of the CMFILES$ share. n For 64-bit systems: C:\Program Files (x86)\VMware\VCM\WebConsole\L1033\Files\, or in the path relative to where you installed the software. n For 32-bit systems: C:\Program Files\VMware\VCM\WebConsole\L1033\Files\, or in the path relative to where you installed the software.
vCenter Configuration Manager Installation Guide Prerequisites n Understand the scenarios to migrate your VCM environment to VCM 5.6. See "Upgrading or Migrating VCM" on page 91. n Understand the prerequisites to migrate your VCM environment to VCM 5.6. See "Prerequisites to Migrate VCM" on page 101. n Understand how to attach a SQL server database in SQL Server Management Studio. See the Microsoft MSDN Library. n Install SQL Server 2008 R2 on the Windows machine that will host the VCM database.
Upgrading or Migrating VCM d. VMware VCM 5.3, EMC Ionix SCM 5.0 or later, or Configuresoft ECM 4.11.1 or later 4. Replace your 32-bit Windows Collector machine with a 64-bit machine. 5. Install the 64-bit Windows Server 2008 R2 operating system on the 64-bit Windows Collector machine. 6. Upgrade VCM to VCM 5.6. What to do next n Configure the SQL Server settings to tune your VCM database in SQL Server Management Studio, including the VCM database file growth and database recovery.
vCenter Configuration Manager Installation Guide Procedure 1. On your 64-bit VCM Collector Windows machine, install Windows Server 2008 R2. 2. Install SQL Server 2008 R2 on your 64-bit VCM Collector. 3. Stop the VCM Collector service and the VCM Patch Management service. 4. On your VCM Collector, use SQL Server Management Studio Object Explorer to detach the VCM databases. 5.
Upgrading or Migrating VCM What to do next n Configure the SQL Server settings to tune your VCM database in SQL Server Management Studio, including the VCM database file growth and database recovery. See "Maintaining VCM After Installation" on page 113. n Log in to VCM. Migrate a 64-bit Environment Running VCM 5.3 or Earlier to VCM 5.6 Migrate an existing 64-bit Collector to VCM 5.6. A migration to VCM 5.
vCenter Configuration Manager Installation Guide 5. On your new 64-bit Collector, use SQL Server Management Studio Object Explorer to attach or restore the VCM databases to SQL Server 2008 R2. 6. On your 64-bit Collector, verify that the owner for the restored or attached databases is set to the sa account or the VCM service account. You can use the built-in sp_changedbowner stored procedure to change the ownership of the databases. 7. Start the VCM 5.6 installation and select the Install option.
Upgrading or Migrating VCM In a previous split installation, the VCM databases were installed on separate Windows machines. The Collector machine hosted the VCM_Coll database only, and the database server machine hosted the VCM, VCM_UNIX, ReportServer, master, and msdb databases. In VCM 5.6, you can migrate a previous split installation to any of the following configurations.
vCenter Configuration Manager Installation Guide Procedure 1. On your 64-bit VCM Collector Windows machine, install Windows Server 2008 R2. 2. Install SQL Server 2008 R2 on your 64-bit VCM Collector. 3. Stop the VCM Collector service and the VCM Patch Management service. 4. On your VCM Collector, use SQL Server Management Studio Object Explorer to detach the VCM databases. 5.
Upgrading or Migrating VCM What to do next n Configure the SQL Server settings to tune your VCM database in SQL Server Management Studio, including the VCM database file growth and database recovery. See "Maintaining VCM After Installation" on page 113. n Log in to VCM. How to Recover Your Collector Machine if the Migration is not Successful If the migration to VCM 5.6 failed, you must perform several steps to recover your VCM Collector machine. Before you attempt another migration to VCM 5.
vCenter Configuration Manager Installation Guide 112 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 82.
vCenter Configuration Manager 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 115.
vCenter Configuration Manager 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 117.
vCenter Configuration Manager 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 What to do next 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.
vCenter Configuration Manager Installation Guide 120 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 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 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 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 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 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 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 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 Configure the provisioning network interface on the machine you are using as the OS Provisioning Server with a static IP address so that the OS Provisioning Server can act as a DHCP server. The following are the default and preferred values used throughout OS Provisioning Server installation process. n IP Address: 10.11.12.1 n Netmask: 255.255.255.
vCenter Configuration Manager Installation Guide Prerequisites n Identify the ports for which you must configure the firewall. See "OS Provisioning Server Network Requirements" on page 134. 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 Installation Guide Procedure 1. "Install the Operating System Provisioning Server" on page 138 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 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 Installation Guide Prerequisites Configure your DHCP server. See "Configure DHCP" on page 140. 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.
Installing, Configuring, and Upgrading the OS Provisioning Server and Components Procedure 1. On the OS Provisioning Server, copy /opt/FastScale/deployment to a directory on the Windows machines on which you are creating the boot image. For example, c:\Program Files\osp. 2. Right-click the Command Prompt icon and select Run as administrator. 3. From the Windows command line, change the directory to the location where you copied the deployment files. For example, c:\Program Files\osp\deployment. 4.
vCenter Configuration Manager Installation Guide Procedure Copy the VCM certificate, VMware_VCM_Enterprise_Certificate_*.pem, to the OS Provisioning Server/opt/FastScale/var/fsadmin/basic/ directory. What to do next Import operating system distributions into your repositories. See "Import Distributions into the OS Provisioning Server Repository" on page 144.
Installing, Configuring, and Upgrading the OS Provisioning Server and Components For example, cp -R /media/cdrom/Win2003-R2-SP2-Standard /tmp/Win2003-R2-SP2Standard-Disk1. 3. Replace the first CD with the second CD and run the cp -R /media/cdrom/ /tmp/ command. For example, cp -R /media/cdrom/Win2003-R2-SP2-Standard /tmp/Win2003-R2-SP2Standard-Disk2. When you import the second CD, do not replace any files if you are prompted during the copy operation.
vCenter Configuration Manager Installation Guide 3. Run the sudo basicimport -d /mnt/ -l command. For example, sudo basicimport -d /mnt/Win2k3SE-R2-SP2-i386 -l 10.11.12.1. If you created a /tmp/ directory for a multi-CD distribution, include the path. For example, /tmp/, or /tmp/Win2003-R2-SP2-Standard. For subsequent imports, you can run the command without the -l option. 4. Type the Family Name.
Installing, Configuring, and Upgrading the OS Provisioning Server and Components Import Linux Distributions Linux distributions are the operating system installation files that you import into the OS Provisioning Server repository. After importing the distribution, use VCM provisioning actions to install the operating system on target machines. You can import standard and customized operating system distributions. You can import standard and customized ISO images.
vCenter Configuration Manager Installation Guide If you are importing a standard ISO, the distribution is imported. If the ISO is customized, you must provide additional information about the distribution that is used when installing the operating system. 8. In the OS distributions list, select the number that most closely corresponds to the operating system you are importing. 1. RedHat Enterprise Linux 6 2. RedHat Enterprise Linux 5.6 3. RedHat Enterprise Linux 5.5 4. RedHat Enterprise Linux 5.4 5.
Installing, Configuring, and Upgrading the OS Provisioning Server and Components Working with Custom Linux ISO Distributions The OS Provisioning Server in VCM allows you to import custom Red Hat and SUSE ISO images into the repository and then to install the custom distributions on target machines. To support standard and custom ISO images, OS Provisioning Server includes required package lists for each supported ISO.
vCenter Configuration Manager Installation Guide location of the image. 4. Run the ./UPGRADE-ME command to install server. 5. In the Nixstaller window, click Next. 6. Click Continue. 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...
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 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 152 Option Description --help Displays and describes the ospctrl options.
Index 3 32-bit environment migrations 101 A administrator rights 20 agent 23 communication settings 114 disk sizing 130 EXE installer 31 folder 23 hardware 121 software provisioning 124 MSI installer 31 non-English Windows platforms 121 OS platform support 9 patch assessment 125 platforms supported 94 software software provisioning 124 UNIX/Linux upgrade 95-96 upgrade for UNIX/Linux 94 upgrading 93 agent certificates 30 agent installed status 23 agent machines for new content architecture 125 Agent Proxy
vCenter Configuration Manager Installation Guide Cryptographic DSS Enhanced Modules 129 Cryptographic RSA Enhanced Modules 129 Cryptographic Service Providers 128 customize VCM 113 D dashboard errors in SSRS 72 data collections in virtual environments 97 data file sizing Mac OS X machines 132 UNIX and Linux machines 132 Windows machines 130 database back up 102 backup and disaster recovery plan 119 file growth 115 history cleanup 118 index rebuild setting 118 integrity check 117 recovery models 115 recove
Index maintain VCM installation 113 maintenance backup and disaster recovery plan 119 configure database file growth 115 customize settings 113 database recovery settings 116 maintenance plan for SQL Server 117 managed machines 11, 121 requirements 121 Managing Agent 126 requirements 126 manual upgrade of agent proxy machine 100 memory requirements VCM on virtual machine 27 Microsoft CryptoAPI 128 migrate 32-bit environment 105 64-bit environment 107 databases 104 databases in split environment 109 split i
vCenter Configuration Manager Installation Guide requirements Agent Proxy 126-127 collector software and OS 15 disk configuration 13 installation 9 managed machines 121 Managing Agent 126 operating system 121 OS Provisioning server 133 software sizing impacts 15 split installation ports 82 UNIX/Linux agent machines 125 UNIX/Linux patch deployment 125 VCM CPU on virtual machine 26 VCM disk space on virtual machine 26 VCM memory on virtual machine 27 VCM on virtual machine 25 resource for VCM on virtual mach
Index virtual environments 97 vSphere Client VCM Plug-in 98 Windows agents 93 upgrading 91 URL for Report Manager 55, 74 URL for Web Service 55, 73 user permissions errors for SSRS 72 V vCenter Server 97, 126 vCloud Director 97, 126 VCM component-specific settings 113 database backup 102 database recovery models 115 supports three-tier installations 17 upgrade 92 VCM installation on virtual machine 25 VCM maintenance plan 117 VCM Remote client upgrade 94 VCM Security Guide certificates 29 system prerequis
vCenter Configuration Manager Installation Guide 158 VMware, Inc.
