5.6
Table Of Contents
- VMware vCenter Configuration Manager Advanced Installation Guide
- Contents
- About This Book
- Achieving a Successful VCM Installation
- Hardware Requirements for Collector Machines
- Software and Operating System Requirements for Collector Machines
- Preparing for Installation
- System Prerequisites to Install VCM
- Configure Resources to Install VCM on a Virtual Machine
- Secure Communications Certificates
- Single-Tier Server Installation
- Configure a Single-Tier Installation Environment
- Verify that the Installing User is an Administrator
- Install and Configure a Windows Server 2008 R2 Operating System
- Install the .NET Framework
- Configuring the Database Components of the VCM Collector
- Configure the Web Components
- Configure SSRS on the VCM Collector
- Configure the VCM Collector Components
- Two-Tier Split Installation
- Configuring a Two-Tier Split Installation Environment
- Verify that the Installing User is an Administrator
- Install and Configure a Windows Server 2008 R2 Operating System
- Configuring the VCM Database Server
- Disable the Firewall or Add an Exception for SQL Server Port 1433
- Install SQL Server on the Database Server
- Verify and Configure the SQL Server Properties
- Verify Matching SQL Server and Computer Names
- Verify the SQL Server Agent Service Account is a sysadmin
- Select the SQL Server Agent Service Account
- Establish SQL Server Administration Rights
- Configure the Combined VCM Collector and Web Server
- Three-Tier Split Installation
- Installing VCM
- Configuring SQL Server for VCM
- Upgrading or Migrating VCM
- Upgrading VCM and Components
- Upgrading Virtual Environments Collections
- Migrating VCM
- Prerequisites to Migrate VCM
- Migrate Only Your Database
- Replace Your Existing 32-Bit Environment with a Supported 64-bit Environment
- Migrate a 32-bit Environment Running VCM 5.3 or Earlier to VCM 5.6
- Migrate a 64-bit Environment Running VCM 5.3 or Earlier to VCM 5.6
- Migrate a Split Installation of VCM 5.3 or Earlier to a Single-Tier, Two-Tier...
- How to Recover Your Collector Machine if the Migration is not Successful
- Maintaining VCM After Installation
- Hardware and Operating System Requirements for VCM Managed Machines
- VCM Agent Support on Non-English Windows Platforms
- VCM Managed Machine Requirements
- Windows Custom Information Supports PowerShell 2.0
- Supported OS Provisioning Target Systems
- Software Provisioning Requirements
- UNIX and Linux Patch Assessment and Deployment Requirements
- Support for VMware Cloud Infrastructure
- vCenter Operations Manager Integration Features
- FIPS Requirements
- Agent Sizing Information
- Hardware and Software Requirements for the Operating System Provisioning Server
- Installing, Configuring, and Upgrading the OS Provisioning Server and Components
- Index
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. For Windows 2008 R2, Windows 7, and Windows 2003 only, type the Build Type.
For example, either volume or retail.
If you 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.
9. In the OS platform list, select 1. Microsoft Windows.
10. In the OS distributions list, select the number that most closely corresponds to the operating system
you are importing.
1. Microsoft Windows Server 2008 R2
2. Microsoft Windows Server 2008 SP2
3. Microsoft Windows Server 2008 SP1
4. Microsoft Windows 7
5. Microsoft Windows 2003, Enterprise Edition R2 SP2
6. Microsoft Windows 2003, Standard Edition R2 SP2
If you select the incorrect distribution, you can import the distribution, but you cannot install it.
11. Type the Build Type, either retail or volume.
The distribution is imported.
What to do next
Import Linux distributions into the OS Provisioning Server repository. See the VCM Administration Guide.
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. When you import a standard image, you type the
required metadata during the import process. If the import process detects a custom image, you must
select specific values for the platform and distribution.
Use this procedure to import Linux distributions. For SUSE distributions that are issued on multiple DVDs,
you use only the first disk and import the distribution using this procedure.
vCenter Configuration Manager Advanced Installation Guide
183
VMware, Inc.