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
n
Bulletins: Collect patching data using the Patch Assessment collection filter. Because UNIX and Linux
assessments are VCMcollections, you can schedule these assessments.
n
Assessment template: Collect patching data using a template that filters the patch assessment results.
n
Collect wizard: Collect patching data using the Patch Assessment Data Class filter.
NOTE Assessments of UNIX and Linux machines operate differently from Windows assessments. UNIX
and Linux assessments require you to collect new data. Windows assessments are performed against
previously collected data.
Assessments of UNIX and Linux machines are run against the patches known by VMware at the time the
assessment is performed.
Patch assessments of UNIX and Linux machines are based on the OS version and machine architecture.
When you collect assessment data using templates, you must match the bulletins, either 32-bit or 64-bit, to
the machine architecture.
For a patch assessment that did not return any results, see the troubleshooting section.
If machine data has not been collected, the assessment results might not appear and the machine will not
be available for deployment. If this situation occurs, a patch-machine mismatch status results. You can
display or hide the patch-machine mismatch status. Click VCM Patching and select VCM Patching
Administration > UNIX > Settings > Bulletin and Update.
Prerequisites
n
Confirm that assessments finished successfully.
n
Verify that the patch signature files (.pls files) exist on the Collector.
The .pls files determine whether required patches are installed on the machine. By default, VCM
Patching downloads the .pls files automatically every 4 hours.
Patch files appear in Console > UNIX > Security > Patches > Assessment or Console > Change
Management > Non VCM Initiated > By Machine. During an assessment of the machines using the
Patch Assessment Data Class, the .pls files are sent from the Collector to the machine. A delay might
occur during this process.
n
Verify that the VCM Agent is installed on the UNIX or Linux machine.
n
Verify that the UNIX or Linux machine is licensed for VCM Patching.
n
Verify that you already have pre-configured filters if you choose Filters in the following procedure. See
"Create UNIX and Linux Patch Assessment Filters" on page 194.
The following procedure runs the assessment using patch bulletins.
Procedure
1. On the toolbar, select the All UNIXMachines machine group.
2. Click Patching
3. Select UNIX/Linux Platform > Bulletins > By Bulletin.
4. Select Assess.
5. In the UNIX Patch Assessment wizard, select Default Filter or Filters.
If you selected Filters, you must select a specific filter.
6. Click Next and Finish to begin the assessment on all machines in the selected machine group.
Getting Started with VCM Patching
VMware, Inc. 193