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. In VCM on the VCM Collector, to set the repository status for the patching repository machine, click
Administration and click Certificates.
2. (Optional) If the patching repository status is set for a different patching repository machine, disable
the patching repository status to stop using that machine as the patching repository.
a. In the Certificates data grid, click the existing Red Hat Linux machine that has the Patching
Repository Status enabled.
b. Click Patching Repository.
c. Click Disable, click Next, and click Finish.
3. Enable the trust status for the Red Hat Linux machine that you are designating as the patching
repository.
a. In the Certificates data grid, click a single Red Hat Linux machine.
b. Click Change Trust Status.
c. Select the Check to trust or uncheck to untrust the selected machines check box and click Next.
4. Enable the patching repository status for the Red Hat Linux machine that you are designating as the
patching repository.
a. Click the Red Hat Linux machine.
b. Click Patching Repository.
c. Click Enable, click Next, and click Finish.
What to do next
Select a patching repository machine and an optional alternate location to store the Linux and UNIX
patches. See "Configure How Managed Machines Stage Patches for Deployment" on page 165.
Configure How Managed Machines Stage Patches for Deployment
You must configure how the target managed machines obtain and stage the patches for VCM to deploy to
the managed machines. VCM 5.7 supports staging patch files as large as 5GB.
For VCM to stage the Linux and UNIX patches and deploy them to managed machines, select a patching
repository machine and an optional geographically distributed alternate location machine.
When a primary patching repository and one or more alternate location repositories are available, VCM
copies the patches from the primary patching repository to either the target managed machines or to an
alternate location machine for deployment to the target managed machines, depending on your selections.
The target managed machines must be able to resolve the name of the alternate location machine that you
type in the VCM Patch Staging wizard.
Prerequisites
n
Configure the patching repository machine as a trusted machine and a patching repository. See "Enable
the Trust and Patching Status for the Patching Repository Machine" on page 164.
n
If you use credentials for patch staging, verify that the managed machine's certificate is trusted. See the
VCM online help.
n
Ensure you understand secure communication for patching. See the VCM Security Guide.
Patching Managed Machines
VMware, Inc.
165