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
What to do next
n
After VCMî ħtriggers a patch assessment, view the patch assessment results. See the VCM online help.
n
(Optional) You can schedule an automatic patch deployment. When you schedule VCM to run an
automatic patch deployment later, and collected patch data or scheduled the patch data collection after
you created the automatic deployment but before the scheduled time to run the automatic deployment.
VCM begins the automatic patch deployment at the scheduled time. See "Configure VCM for
Automatic Scheduled Patch Assessment and Deployment" on page 176.
Configure VCM for Automatic Scheduled Patch Assessment and
Deployment
To ensure that Linux, UNIX, and Windows managed machines are updated with the latest patches on a
regular basis, you can schedule VCM to deploy patches to the managed machines. The automatic
scheduled patch assessment and deployment matches a machine group to a patch assessment template.
To configure the automatic scheduled patch assessment and deployment, you must generate a patch
assessment template. Optionally, you can add exceptions for the automatic patch deployment.
Prerequisites
Configure VCM. See "Configuring VCM to Work with the Patching Repository and Alternate Locations"
on page 162.
Procedure
1. Click Patching and select All UNIX/Linux Platforms > Automatic Deployment.
2. To add an automatic deployment mapping, click Add, type a name and description for the mapping,
and click Next.
3. Click the Linux, UNIX, or Windows machine group to use for the automatic scheduled patch
deployment.
4. Click the patching assessment template that you created, and click Next.
5. Select the Scheduled Automatic Deployment Run for the type of automatic deployment run option.
6. Select an automatic deployment reboot option.
7. Type a number for the threshold data age and click Next.
The threshold data age indicates the number of days allowed since the last patch assessment was run
on the managed machine, before VCM can run the automatic patch deployment on the managed
machine.
8. Define the schedule to run the automatic patch deployment, including how often the automatic
patching occurs, the time of day, and the start and end dates, and click Next.
9. Review the summary and click Finish to schedule the automatic patch deployment.
What to do next
n
For Linux and UNIX patching, after a job triggers, view the job chain in the VCM Job Manager, and
finished job chain jobs in Job Manager History. See "How the Linux and UNIX Patching Job Chain
Works" on page 178.
vCenter Configuration Manager Administration Guide
176
VMware, Inc.