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. Click Administration and select Settings >General Settings > Patching > Machine Group Mapping.
2. Select a machine group and click Edit.
3. Select a deployment type.
Option Description
Standard
Deployment
VCMdeploys the Linux and UNIX patches from a standard predefined patch
directory, such as /tmp, on the target managed machines.
The standard path for deployment is defined in UNIXAdditional Settings.
Custom
Deployment
VCMdeploys the Linux and UNIX patches from a custom patch directory on the
target managed machines. You must type the path to the directory where the
patches reside on the target managed machines.
4. Select a source for the patches for VCMto use to stage the patches on the target managed machines
during patch deployment.
The source can be the patching repository machine, a geographically distributed alternate location
machine, or None. If you select None, you must manually stage the patches on the target managed
machines.
5. Select the type of temporary path to use on the target managed machines for VCM to extract the
Linux and UNIX patches and temporary files.
Option Description
StandardTemp
Path
VCMdeploys Linux and UNIX patches from a standard predefined patch
directory on the target managed machines, such as /var/tmp.
The standard path is defined in UNIXAdditional Settings for the setting
named Default Machine Group Mapping location for patch deployments.
CustomTemp
Path
VCMdeploys Linux and UNIX patches from a custom path. You must type
the custom path in the text box.
The custom path is defined in UNIXAdditional Settings for the setting named
Default Machine Group Mapping for temporary files during patch
deployment.
6. Type the path to the temporary files on the managed machines and click Next
7. Review the settings and click Finish.
What to do next
n
Verify that the Software Content Repository (SCR) Tool base path in VCM points to the location where
you installed the SCR Tool on the patching repository machine. See "Verify the SCR Tool Base Path for
the Patching Repository" on page 168.
n
Use VCM to deploy the patches to target Linux and UNIX managed machines. See "Deploying Patches
with Automated Patch Assessment and Deployment" on page 169.
Verify the SCR Tool Base Path for the Patching Repository
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.
vCenter Configuration Manager Administration Guide
168
VMware, Inc.