User`s guide
Table Of Contents
- VCM Installation and Getting Started Guide
- Updated Information
- About This Book
- Preparing for Installation
- Installing VCM
- Using Installation Manager
- Installing and Configuring the OS Provisioning Server and Components
- Installing the Operating System Provisioning Server
- Preparing Boot Images for Windows Provisioning
- Copy the VCM Certificate to the OS Provisioning Server for Linux Provisioning
- Importing Distributions into the OS Provisioning Server Repository
- Configuring the OS Provisioning Server Integration with the VCM Collector
- Maintaining Operating System Provisioning Servers
- Upgrading or Migrating vCenter Configuration Manager
- Upgrade and Migration Scenarios
- Prerequisites
- Back up Your Databases
- Back up Your Files
- Back up Your Certificates
- Software Supported by the VCM Collector
- Migration Process
- Prerequisites
- Foundation Checker Must Run Successfully
- Use the SQL Migration Helper Tool
- Migrate Only Your Database
- Replace your existing 32-Bit Environment with the Supported 64-bit Environment
- How to Recover Your Machine if the Migration is not Successful
- Migrate a 32-bit environment running VCM 5.3 or earlier to VCM 5.4
- Migrate a 64-bit environment running VCM 5.3 or earlier to VCM 5.4
- Migrate a split installation of VCM 5.3 or earlier to a single-server install...
- After You Migrate VCM
- Upgrade Process
- Upgrading Existing Windows Agents
- Upgrading Existing Remote Clients
- Upgrading Existing UNIX Agents
- Upgrading VCM for Virtualization
- Getting Started with VCM Components and Tools
- Getting Started with VCM
- Discover, License, and Install Windows Machines
- Verifying Available Domains
- Checking the Network Authority
- Assigning Network Authority Accounts
- Discovering Windows Machines
- Licensing Windows Machines
- Installing the VCM Windows Agent on your Windows Machines
- Performing an Initial Collection
- Exploring Windows Collection Results
- Getting Started Collecting Windows Custom Information
- Discover, License, and Install UNIX/Linux Machines
- Discover, License, and Install Mac OS X Machines
- Discover, License, 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
- Getting Started with VCM Management Extensions for Assets
- Getting Started with VCM Service Desk Integration
- Getting Started with VCM for Active Directory
- Accessing Additional Compliance Content
- Installing and Getting Started with VCM Tools
- Maintaining VCM After Installation
- Troubleshooting Problems with VCM
- Index
vCenter Server Collections
When collecting data from vCenter Server, you must license the Windows machine running the vCenter
Server and install a VCM Agent (version 5.4 or later), PowerShell, and vSphere PowerCLI. The Agent runs
the vCenter Server collection by using vSphere PowerCLI to access the vSphere API on vCenter server.
The data is relayed to the Collector and added to the database.
Configuring vCenter Server Data Collections
Collecting vCenter server data is based on a process that extends beyond the standard Windows
collection. The configuration of the process has several prerequisites. When the prerequisites are met, data
is collected from vCenter Server by using default collection filters.
The configuration process includes several tasks.
n
"vCenter Server Collection Prerequisites" on page 135
n
"Collect vCenter Server Data" on page 137
n
"Reviewing Collected vCenter Server Data" on page 137
n
"Troubleshooting vCenter Server Data Collections" on page 138
vCenter Server Collection Upgrade Considerations
A new method for collecting vCenter Server data is introduced in VCM 5.4 that is simpler to implement
and manage. The older method (5.3 and earlier), implemented using Windows remote commands, has
been replaced with this new method.
Data that you previously collected by using the vCenter Server remote commands is no longer available.
You must recreate scheduled collections to accommodate the new method. However, previously
configured compliance rules, reports, and alerts based on the previously collected data are automatically
redirected to the data in the new data grids.
vCenter Server Collection Prerequisites
The vCenter Server collection prerequisites prepare your environment for collecting data from vCenter
Servers.
n
"Configure the VCM Agent with HTTP Communication" on page 135
n
"Add vCenter Server User with Administrator Role" on page 136
n
"Remove PowerShell v1.x from vCenter Servers" on page 136
n
"Download and Install PowerShell v2.0 " on page 136
n
"Download and Install VMware vSphere PowerCLI" on page 137
Configure the VCM Agent with HTTP Communication
You must configure the VCM Agent (5.4 or later) on the vCenter server with HTTP communication. You
cannot collect vCenter Server data if the Agent is not configured to use HTTP.
Prerequisites
Install the Agent (5.4 or later) on the vCenter server. See "Discover, License, and Install Windows
Machines" on page 69.
Getting Started with VCM for Virtualization
VMware, Inc. 135