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
8. (Optional) If you selected Obtain patches from an Alternate Location, you must provide the path and
connection information to copy the patches from the alternate location machine to the target managed
machines.
a. (Optional) If necessary, change the path where the patches reside.
VCM populates this path from the previous screen to match it to the patching repository file
structure.
b. Select the protocol used to copy patches from the alternate location machine to the target managed
machines.
This read operation uses HTTPS, HTTP, FTP, NFS, or File, a premounted file system.
c. Select the port that the selected protocol uses to copy the patches.
d. To require credentials to copy the patches, type the user name and password and click Finish.
What to do next
Configure the machine group mapping for VCMto use to patch the target managed machines. See
"Configure the Machine Group Mapping to Use the Patch Staging Configuration" on page 167.
Configure the Machine Group Mapping to Use the Patch Staging Configuration
You must configure the machine group for VCMto use to deploy Linux and UNIX patches to target
managed machines. You can combine Linux and UNIX managed machines into a single machine group,
and have VCMuse a single action to deploy the patches to all of the managed machines in that group.
VCMuses the alternate location defined in the machine group mapping to deploy patches to the managed
machines. During the patch deployment, VCMstages the Linux and UNIXpatches from the patching
repository or the optional alternate location machine to the target managed machines, then deploys the
patches to those machines.
By default, VCM stages the patches in the /tmp directory on the managed machines. However, vendors
such as HP, Oracle, and IBM, can bundle multiple patches into a set, and the /var/tmp directory is used to
process the patches during patch deployment.
Prerequisites
n
Configure how the target managed machines obtain and stage the patches for VCM to deploy to the
managed machines. See "Configure How Managed Machines Stage Patches for Deployment" on page
165.
n
Verify that the machine groups for VCMto use during the patch deployment are defined. If machine
groups are not available to patch your specific groups of managed machines, you must add them. See
the VCM online help.
Patching Managed Machines
VMware, Inc.
167