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
Procedure
1. To modify the automatic patching settings, click Administration.
2. Click Settings > General Settings > Patching > UNIX > Additional Settings.
3. According to your patch assessment and deployment strategy, click Edit Setting for each of the
automatic patch deployment settings, then modify and save the setting.
Option Description
Automatic patch
deployment-
Automatically deploy
patches whenever
membership of
associated machine
groups changes
VCM deploys patches when you add a machine to a machine group
and the membership is updated for any machine group that is
associated with an automatic deployment. VCM begins the automatic
patch deployment, and the results are updated for static or dynamic
patching templates.
Automatic patch
deployment-
Automatically deploy
patches whenever
membership of
associated templates
changes
VCM deploys patches when new downloaded patch content matches
the filter used in a dynamic patching assessment template, or you edit
the template to change the bulletins included in it. VCM updates the
bulletin membership in the patch assessment template and triggers
an automatic patch deployment.
Automatic patch
deployment-
Automatically deploy
patches whenever patch
applicability changes
VCM deploys patches when you collect the patch status from
managed machines, and run a patch assessment on those machines. If
the machines are part of the machine group that is mapped to an
assessment template in the automatic deployment wizard, VCM
determines which managed machines require patches and begins the
automatic patch deployment. If the template is assessed after a
collection, the change in patch applicability triggers an automatic
patch deployment.
Automatic patch
deployment-Default
threshold data age
(days)
Sets the patching data age threshold, in days, for the collected patch
data, which defines how old the collected patch data can be before
VCM deploys the patches. When the data age of the bulletin is
greater than the threshold data age, VCM does not deploy the
patches. You must run a new collection and assessment to update the
data age for the patch bulletin.
4. Review the additional patching settings, and make any changes required for your environment.
a. Set the patching content download to match the licensed platform types.
b. Set the default machine group mapping path for temporary files during patch deployment.
c. Set the default machine group mapping location for patch deployments.
d. Set the default Linux and UNIX repository host, path, and SCR base path.
e. Define the platforms for which patching content is downloaded and parsed.
vCenter Configuration Manager Administration Guide
174
VMware, Inc.