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
Deploying some patches might fail on AIX machines if the patch prerequisites cannot be resolved by VCM
using the downloaded patch bulletin content. This problem can arise with an AIX patch whose status is
"StatusNotPatched", and where the Bulletin Detail indicates a patch dependency on another set of patches
whose dependencies cannot be met.
Although dependencies may or may not appear the Bulletin Detail, one or more currently irresolvable
patch dependencies may actually exist. The missing patch prerequisites can occur when some patch
versions do not become applicable until after other patches are installed. In particular, Maintenance Level
(ML) or Technology Level (TL) packages and their corresponding bulletins that are intended to upgrade
between levels may not show as applicable until the ML/TL upgrade has been met or exceeded. For
example, if you are applying a patch that depends on an intermediate ML that has not yet been applied,
deploying the patch will fail since the prerequisite patch dependency has not been met.
To resolve the patch interdependencies on AIX machines, you must determine the patch strategy used for
the filesets/APARS/MLs/TLs that are being updated.
Default Location for UNIX/Linux Patches
If you do not define an alternate location for the patches using Machine Group Mapping, the default
location of /tmp is used. A temporary expansion of the patches occurs in the /tmp directory.
vCenter Software Content Repository Tool
To help you obtain UNIX patches for deployment, a deployment tool is available from VMware Technical
Support. For more information, contact VMware Technical Support.
Deploy Patches to Windows Machines
Deploy patches to Windows machines that are managed by VCM Patching. These machines appear in
Patching > VCM Patching Administration > Windows > Machines Manager > Licensed Machines.
Prerequisites
n
Follow the guidelines in "vCenter Software Content Repository Tool" on page 190 before you deploy a
patch.
n
Make sure the Windows Update service is running (set to something other than Disabled) before you
patch Windows 2008 servers and Windows 7 machines, or the patch deployment will fail.
Procedure
1. Click Patching.
2. Select Windows > Assessment Templates and select the template used for the assessment.
3. Make sure the data grid view is visible so that you can view the machines and bulletins.
4. Locate the rows that display the StatusNotPatched status.
To easily identify the machines that must be patched, group the Patch Status column.
5. Highlight the row containing the machine to be patched and select Deploy.
If you have VCM Service Desk Integration licensed, the Service Desk Connector dialog box appears
prior to the VCM Patching Deploy wizard.
If you licensed and activated VCM Service Desk Integration, VCM Orchestrator must approve the
deployment job before it can run.
6. (Optional) Although the Deploy wizard automatically selects the machine and the patch to be
deployed, you can select additional machine and patch combinations to include.
vCenter Configuration Manager Installation and Getting Started Guide
190 VMware, Inc.