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
Collect Package Manager Information from Machines
To view information about packages and Package Managers in VCM, you must collect Package Manager
data from managed machines.
As you work with provisioning, you will want to regularly collect Package Manager data to determine if
your machines are remaining current with the necessary software packages.
Prerequisites
n
Package Manager is installed on the target machines. Package Manager is automatically installed when
you install the VCM 5.3 Agent or later. See "Install Package Manager on Managed Machines" on page
222.
n
Verify that you created software provisioning packages using VMware vCenter Configuration
Manager Package Studio and published the packages to the repositories. See "Creating Packages" on
page 223.
Procedure
1. Click Collect.
2. Select Machine Data.
3. Click OK.
4. On the Machines page, verify that the Selected pane displays all the machines from which you are
collecting package manager data and click Next.
5. On the Data Types page, expand Windows, select Software Provisioning - Package Managers, and
click Next.
6. On the Confirmation page, review the information, resolve any conflicts, and then click Finish.
You can monitor the process in the Jobs Manager. See "Viewing Provisioning Jobs in the Job Manager"
on page 230 for more information.
What to do next
n
When the collection is finished, view the collected data. Click Console and select Windows tab >
Operating System > Software Provisioning > Package Managers. The data grid displays the packages
and their current status.
n
Collect repository data from the Software Repository for Windows. See "Collect Software Repository
Data" on page 226.
Collect Software Repository Data
Collect the repository data to identify which software packages are in which repositories. From the
collected information, you can determine which repositories to assign to machines based on the available
packages.
To better manage your repository machines, create a machine group containing all the machines on which
the software repository is installed.
Prerequisites
Verify that you created software provisioning packages using VMware vCenter Configuration Manager
Package Studio and published the packages to the repositories. See "Creating Packages" on page 223.
vCenter Configuration Manager Installation and Getting Started Guide
226 VMware, Inc.