Installation guide
Table Of Contents
- VMware vCenter Configuration Manager Administration Guide
- Contents
- About This Book
- Getting Started with VCM
- Installing and Getting Started with VCM Tools
- Configuring VMware Cloud Infrastructure
- Virtual Environments Configuration
- Configure Virtual Environments Collections
- Configure Managing Agent Machines for Virtual Environment Management
- Obtain the SSL Certificate Thumbprint
- Configure vCenter Server Data Collections
- Configure vCenter Server Virtual Machine Collections
- Configure vCloud Director Collections
- Configure vCloud Director vApp Virtual Machines Collections
- Configure vShield Manager Collections
- Configure ESX Service Console OS Collections
- Configure the vSphere Client VCM Plug-In
- Running Compliance for the VMware Cloud Infrastructure
- Create and Run Virtual Environment Compliance Templates
- Create Virtual Environment Compliance Rule Groups
- Create and Test Virtual Environment Compliance Rules
- Create and Test Virtual Environment Compliance Filters
- Preview Virtual Environment Compliance Rule Groups
- Create Virtual Environment Compliance Templates
- Run Virtual Environment Compliance Templates
- Create Virtual Environment Compliance Exceptions
- Resolve Noncompliant Virtual Environments Template Results
- Configure Alerts and Schedule Virtual Environment Compliance Runs
- Configuring vCenter Operations Manager Integration
- Auditing Security Changes in Your Environment
- Configuring Windows Machines
- Configure Windows Machines
- Windows Collection Results
- Getting Started with Windows Custom Information
- Prerequisites to Collect Windows Custom Information
- Using PowerShell Scripts for WCI Collections
- Windows Custom Information Change Management
- Collecting Windows Custom Information
- Create Your Own WCI PowerShell Collection Script
- Verify that Your Custom PowerShell Script is Valid
- Install PowerShell
- Collect Windows Custom Information Data
- Run the Script-Based Collection Filter
- View Windows Custom Information Job Status Details
- Windows Custom Information Collection Results
- Run Windows Custom Information Reports
- Troubleshooting Custom PowerShell Scripts
- Configuring Linux, UNIX, and Mac OS X Machines
- Linux, UNIX, and Mac OS X Machine Management
- Linux, UNIX, or Mac OS X Installation Credentials
- Configure Collections from Linux, UNIX, and Mac OS X Machines
- Configure Installation Delegate Machines to Install Linux, UNIX, and Mac OS X...
- Configure the HTTPS Bypass Setting for Linux Agent Installations
- Enable Linux, UNIX, and Mac OS X Agent Installation
- Add and License Linux, UNIX, and Mac OS X Machines for Agent Installation
- Install the VCM Agent on Linux, UNIX, and Mac OS X Operating Systems
- Collect Linux, UNIX, and Mac OS X Data
- Linux, UNIX, and Mac OS X Collection Results
- Configure Scheduled Linux, UNIX, and Mac OS X Collections
- Patching Managed Machines
- Patch Assessment and Deployment
- Prerequisite Tasks and Requirements
- Manually Patching Managed Machines
- Getting Started with VCM Manual Patching
- Configuring An Automated Patch Deployment Environment
- Deploying Patches with Automated Patch Assessment and Deployment
- Configure VCM for Automatic Event-Driven Patch Assessment and Deployment
- Generate a Patch Assessment Template
- Run a Patch Assessment on Managed Machines
- Add Exceptions for Patching Managed Machines
- Configure the VCM Administration Settings
- Generate a Patch Deployment Mapping
- Configure VCM for Automatic Scheduled Patch Assessment and Deployment
- How the Linux and UNIX Patch Staging Works
- How the Linux and UNIX Patching Job Chain Works
- How the Deploy Action Works
- Patch Deployment Wizards
- Running Patching Reports
- Running and Enforcing Compliance
- Provisioning Physical or Virtual Machine Operating Systems
- Provisioning Software on Managed Machines
- 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
- Configuring Active Directory Environments
- Configuring Remote Machines
- Tracking Unmanaged Hardware and Software Asset Data
- Managing Changes with Service Desk Integration
- Index
How the Linux and UNIX Patch Staging Works
As a patch administrator, you can stage patches on target Linux and UNIX managed machines for VCMto
deploy. With patch staging, the patches are available in a directory on the target managed machines in
preparation for deployment.
Target managed machines copy the patches from either the patching repository machine or an alternate
location machine. After the patches are stored in the patch repository or on the alternate location
machines, during the patch deployment you can schedule the patch staging to target managed machines
before the deployment occurs. You can have VCM deploy the patches immediately after you stage them
or when certain conditions occur, which trigger an automatic patch deployment.
With the patch deployment schedule, you can stage the patches on the target managed machines
immediately or at a later time before the scheduled deployment occurs. Otherwise, you must manually
stage the patches on the target managed machines.
When you set up a patching repository machine and alternate location machines, you must ensure that
users have proper permissions and protocols configured to read patches from the patching repository
machine and write patches to the alternate location machines.
VCM staging of Linux and UNIX patches performs the following actions.
n
The patching repository machine retrieves Linux and UNIX patches from the vendor Web sites and
stores them in its local patch repository.
n
To make the patches available for deployment to target managed machines, VCM copies the patches
from the patching repository to the alternate locations, or to the target managed machines, depending
on whether you have alternate location machines in your patching environment.
Option Description
Copy patches
from the
patching
repository
Target managed machines copy patches from the patching repository to stage
the patches for deployment.
Copy patches
from an
alternate
location
In a geographically distributed patching environment, VCM copies patches
from the patching repository machine to an alternate location machine to stage
the patches on the target managed machines for deployment.
n
VCM uses FTP, NFS, or File, a premounted file system, to copy the patches
to the alternate location machine.
n
VCM uses HTTP, HTTPS, FTP, NFS, or File, a premounted file system, to
copy the patches from an alternate location to the target managed
machines.
n
In the patch deployment action, VCM stages the patches in the standard or custom patch directory on
the target Linux and UNIX managed machines. Then VCM deploys the patches immediately or at the
time that you schedule the patch deployment in the Deploy wizard.
After VCM finishes the patch deployment, you can run another patch assessment to verify that the
patches are applied to the managed machines.
Patching Managed Machines
VMware, Inc.
177