User`s guide
Table Of Contents
- VMware vCenter Configuration ManagerInstallation and Getting Started Guide
- About This Book
- Preparing for Installation
- Installation Manager
- Installation Configurations
- Tools Installation
- General Prerequisites to Install VCM
- Verify Hardware and Software Requirements
- Verify Administration Rights
- Set the Default Network Authority Account
- Specify the Collector Services Account
- Change the Collector Services Account Password in the Services Management Con...
- Change the Collector Services Account Password in the Component Services DCOM...
- Verify the VMware Application Services Account
- Determine the VCM Remote Virtual Directory
- Use Secure Communications Certificates
- Understand Server Authentication
- Verify the Foundation Checker System Checks
- Install UNIX Patch for HP-UX 11.11
- VCM Uses FIPS Cryptography
- Installing VCM
- Installing, Configuring, and Upgrading the OS Provisioning Server and Components
- Upgrading or Migrating VCM
- Upgrades
- Migrations
- Prerequisites to Migrate VCM
- Back Up Your Databases
- Back up Your Files
- Export and Back up Your Certificates
- Migrating 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.4.1
- Migrate a 64-bit Environment Running VCM 5.3 or Earlier to VCM 5.4.1
- Migrate a Split Installation of VCM 5.3 or Earlier to a Single-Server Install...
- How to Recover Your Collector Machine if the Migration is not Successful
- Upgrading VCM and Components
- Maintaining VCM After Installation
- Getting Started with VCM Components and Tools
- Getting Started with VCM
- Discover, License, and Install Windows Machines
- Discover, License, and Install Windows Machines
- Verify Available Domains
- Check the Network Authority
- Assign Network Authority Accounts
- Discover Windows Machines
- License Windows Machines
- Disable User Account Control for VCM Agent Installation
- Install the VCM Windows Agent on Your Windows Machines
- Enable UAC After VCM Agent Installation
- Collect Windows Data
- Windows Collection Results
- Getting Started with Windows Custom Information
- Discover, License, and Install UNIX/Linux Machines
- Discover, License, and Install Mac OS X Machines
- Discover, Configure, and Collect Oracle Data from UNIX Machines
- Customize VCM for your Environment
- How to Set Up and Use VCM Auditing
- Discover, License, and Install Windows Machines
- Getting Started with VCM for Virtualization
- Getting Started with VCM Remote
- Getting Started with VCM Patching
- Getting Started with Operating System Provisioning
- Getting Started with Software Provisioning
- Using Package Studio to Create Software Packages and Publish to Repositories
- Software Repository for Windows
- Package Manager for Windows
- Software Provisioning Component Relationships
- Install the Software Provisioning Components
- Using Package Studio to Create Software Packages and Publish to Repositories
- Using VCM Software Provisioning for Windows
- Related Software Provisioning Actions
- Getting Started with VCM Management Extensions for Assets
- Getting Started with VCM Service Desk Integration
- Getting Started with VCM for Active Directory
- Installing and Getting Started with VCM Tools
- Index
To identify the vCloud Director virtual machines, you configure discovery rules that analyze data collected
from the vCloud Director REST API and use the vApp virtual machine information to add new virtual
machines to VCM. After installing the Agent and licensing the virtual machines, you manage the new
machines based on their operating systems. The machines appear in VCM based on your configured
naming convention.
Prerequisites
Review how network address translation is used in your vCloud Director environment. See "Network
Address Translation and vCloud Director vApp Discovery Rules" on page 153.
Procedure
1. "Generate vCloud Director Collection Credentials" on page 155
To collect vCloud Director data, you must generate encrypted user credentials that the collection filters
use to access vCloud Director.
2. "Create vCloud Director Data Collection Filters" on page 156
For each of your vCloud Director instances, you clone the custom information collection filter template
to create a unique collection filter for each instance.
3. "Collect vCloud Director Data" on page 158
You collect the vCloud Director data using the collection filters configured for each vCloud Director
instance. You must run the collection against the Collector, not the vCloud Director.
4. "Discover vCloud Director vApp Virtual Machines" on page 158
To begin managing the vCloud Director vApp virtual machines, you create and run a VCM discovery
rule. The rule runs against the collected vCloud Director data in the VCM database.
The vCloud Director data is collected using a collection filter with the Custom Information (Win) data type.
The collected data appears in the Console. The discovered vApp virtual machines appear in
Administration. After you license the virtual machines and install the Agent, you manage them based on
their operating system.The collected vCloud Director data appears in the Console. The discovered virtual
machines appear on Administration. After you license the virtual machines and install the Agent, you
manage them based on their operating system. See "vCloud Director Collection Results" on page 162.
Network Address Translation and vCloud Director vApp Discovery Rules
To configure the connection string when creating a vCloud Director virtual machines discovery rule, you
must know how network address translation (NAT) is implemented in your vCloud Director instances.
The vCloud Director administrator configures the NATmapping. How the virtual machines are
configured with NATand where VCM is in the network determines the connection string that VCM uses
to communicate with the virtual machines.
vCloud Director 1.0 and 1.5 support a variety of vApp network configurations. VCM supports these
scenarios.
Getting Started with VCM for Virtualization
VMware, Inc. 153