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
To ensure that Linux, UNIX, and Windows managed machines always include the latest patches, you
can have VCM deploy patches to the managed machines when certain events occur in your
environment. After you perform the initial configuration for the automatic deployment, no
intervention is required to deploy patches to managed machines.
5. "Configure VCM for Automatic Scheduled Patch Assessment and Deployment" on page 176
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.
What to do next
n
For Linux and UNIX patching, after a job triggers, view the job chain in the VCM Job Manager, and the
finished job chain jobs in Job Manager History. See "How the Linux and UNIX Patching Job Chain
Works" on page 178.
n
(Optional) You can schedule an automatic patch deployment. See "Configure VCM for Automatic
Scheduled Patch Assessment and Deployment" on page 176.
Configuring the Patching Repository Machine
To patch managed Linux and UNIX machines, you must install a Red Hat Linux 6, 64-bit machine as the
patching repository, configure the communication protocols, and download and configure the Software
Contentī ±Repository (SCR) Tool.
CAUTION To ensure security in a geographically distributed Linux and UNIX patching
environment, the credentials that you use to transfer patches from the patching repository to the
alternate location must be different from the credentials that you use to copy patches from the
alternate location to the target managed machines. The credentials used to transfer patch files to the
alternate location must have read and write privileges. Use read-only credentials to stage patches
from an alternate location to a managed machine.
If you already configured the Red Hat Linux patching repository machine for manual patching with VCM,
you can skip this procedure.
Prerequisites
n
Verify that the Red Hat Linux patching repository machine can access the Internet.
n
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. See "Communication Protocols to Stage
Linux and UNIX Patches" on page 159.
n
Decide which protocol to use to copy patches from the patching repository machine to the optional
alternate location machines. To configure the protocol, see http://kb.vmware.com/kb/2051632 and the
Red Hat Linux information online.
vCenter Configuration Manager Administration Guide
158
VMware, Inc.