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
n
Verify that the machine groups to be used for Linux and UNIX patching are defined in VCM, and add
any new machine groups for VCMto patch specific groups of managed machines. See the VCM online
help.
n
(Optional) If your VCM Collector is not configured to use HTTPS, before you add a patch staging
configuration you must allow the Collector to bypass the HTTPS setting. Select Administration >
Settings > General Setting > Collector. Change the value of the setting named Allow HTTP
communication (HTTPS bypass) when entering sensitive parameter values to Yes.
Procedure
1. "Enable the Trust and Patching Status for the Patching Repository Machine" on page 164
You must enable the trust and patching repository status for the Red Hat Linux patching repository
machine, to designate it as a trusted patching machine for security purposes.
2. "Configure How Managed Machines Stage Patches for Deployment" on page 165
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.
3. "Configure the Machine Group Mapping to Use the Patch Staging Configuration" on page 167
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.
4. "Verify the SCR Tool Base Path for the Patching Repository" on page 168
The setting for the Software Content Repository (SCR) Tool base path in VCM must point to the
location where you installed the SCR Tool on the patching repository machine.
What to do next
n
Run a patch assessment on the managed machines that are targeted for patch deployment, examine the
results.See the VCM online help.
n
Use VCM's automated patch assessment and deployment to deploy patches. See "Deploying Patches
with Automated Patch Assessment and Deployment" on page 169.
Enable the Trust and Patching Status for the Patching Repository Machine
You must enable the trust and patching repository status for the Red Hat Linux patching repository
machine, to designate it as a trusted patching machine for security purposes.
You can use a single patching repository machine. The Red Hat Linux patching repository machine hosts
the Software Content Repository (SCR) Tool that VCM uses to download patches from the vendor Web
sites.
Prerequisites
n
Set up a physical or virtual Red Hat Linux machine, running Red Hat version 6 or later, 64-bit, to be
used for the Linux and UNIXpatching repository. See the online Red Hat Customer Portal.
n
(Optional) Set up one or more geographically distributed alternate location Red Hat Linux machines,
running Red Hat 6, 64-bit. See the online Red Hat Customer Portal.
vCenter Configuration Manager Administration Guide
164
VMware, Inc.