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
9. On the Patch Deployment Schedule page, set the timing for the patch deployment job.
10. On the Reboot Options page, select the options to reboot the machine and send a message or select to
avoid a reboot.
11. On the Confirmation page, confirm the patch summary information and complete the wizard to
deploy the patch.
After you deploy patches, VCM collects assessment data again to confirm the patches were applied.
VCM saves UNIX and Linux patching change actions in the VCM change log. Click Console and select
Change Management > VCM or Non VCM Initiated Change > By Data Type > Patch Assessment.
These change actions are available to Compliance and Reports.
IMPORTANT If a failure occurs at any point in the patch deployment job, the System Administrator must
check the status of the system, resolve any issues, and then reassess the machines.
How the Deploy Action Works
The Deploy action runs a command from the Collector to the VCM managed machines.
The VCM job command performs the following actions.
n
Assesses VCM managed machines to determine whether the patch was installed since the last
assessment.
n
Runs a pre-install script (remote command) if specified.
n
Installs the patch that already resides on the VCM managed machine’s NFS mounted or local file
system.
n
Runs a post-install script (remote command) if specified.
n
Assesses whether the patch was installed on the VCM managed machine.
The pre-install and post-install scripts used in the Deploy actions are remote commands, which differ from
using a VCMremote command to install a patch. The patch assessment and deployment process for UNIX
and Linux does not use remote commands. If you choose to deploy a patch using a user-created remote
command, be aware that the patch will not be assessed until you run an assessment.
Running VCM Patching Reports
You can run patch status reports on UNIX and Windows machines based on trends, details, template
summary, bulletins, affected software products, and patch deployment history.
With real-time assessment reports you can generate SQLreports for machines assessed against bulletins
and affected software products. With the patch deployment history report, you can report on the history
of patch deployments using VCM Patching assessment results.
You can generate several reports.
n
Create real-time assessment reports by bulletins or products.
n
Create real-time assessment reports by affected software products.
n
Create real-time assessment reports of bulletins and products.
n
Create a patch deployment history report.
When you generate reports, you can take the following actions.
n
Manually update VCM Patching Windows content.
n
Run reports without Internet access.
Getting Started with VCM Patching
VMware, Inc. 197