Installation guide
Table Of Contents
- VMware vCenter Configuration ManagerAdministration Guide
- 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
- 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
- Configuring vCenter Operations Manager Integration
- Auditing Security Changes in Your Environment
- Configuring Windows Machines
- Verify Available Domains
- Check the Network Authority
- Assign Network Authority Accounts
- Discover Windows Machines
- License Windows Machines
- Disable User Account Control for VCM Agent Installation
- Install the VCM Windows Agent on Your Windows Machines
- Enable UAC After VCM Agent Installation
- Collect Windows Data
- 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 and UNIX Machines
- Configuring Mac OS X Machines
- Patching Managed Machines
- VCM Patching for Windows Machines
- VCM Patching for UNIX and Linux Machines
- UNIX and Linux Patch Assessment and Deployment
- Getting Started with VCM Patching
- Getting Started with VCM Patching for Windows Machines
- Check for Updates to Bulletins
- Collect Data from Windows Machines by Using the VCM Patching Filter Sets
- Assess Windows Machines
- Review VCM Patching Windows Assessment Results
- Prerequisites for Patch Deployment
- Default Location for UNIX/Linux Patches
- Location for UNIX/Linux Patches
- Default Location for UNIX/Linux Patches
- vCenter Software Content Repository Tool
- Deploy Patches to Windows Machines
- Getting Started with VCM Patching for UNIX and Linux Machines
- Check for Updates to Bulletins
- Collect Patch Assessment Data from UNIX and Linux Machines
- Explore Assessment Results and Acquire and Store the Patches
- Default Location for UNIX/Linux Patches
- Deploy Patches to UNIX/Linux Machines
- How the Deploy Action Works
- Running VCM Patching Reports
- Customize Your Environment for VCM Patching
- 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
Prerequisites
Configure the vCloud Director settings. See "Configure the vCloud Director Settings" on page 36.
Procedure
1. Click Administration.
2. Select Machines Manager > Licensed Machines > Licensed Virtual Environments.
3. Select the vCloud Director instances and click Collect on the VCM toolbar.
4. On the Collection Type page, select Machine Data and click OK.
5. On the Machines page, verify that the Selected list includes all the vCloud Director instances from
which you are collecting and click Next.
6. On the Data Types page, select the Virtualization vCloud Director data type that you want to collect
from the vCloud Director instances and click Next.
7. On the Important page, resolve any conflicts and click Finish.
What to do next
Review the collected virtualization data. Click Console and select Virtual Environments > vCloud
Director.
Discover the vApp virtual machines created by the vCloud Director and make them available in VCM. See
"Discover vCloud Director vApp Virtual Machines" on page 41.
vCloud Director Collection Results
The collected vCloud Director data appears in the Console. The discovered virtual machines appear on
Administration. After you license the virtual machines and install the Agent, you manage them based on
their operating system.
The displayed data is only as current as the last time you collected data from your vCloud Director
instances and from your managed machines.
Option Description
Console View collected vCloud Director instance data. Click Console and
selectVirtual Environments > vCloud Director.
View the change logs for the virtual environments. Click Console and
select Change Management to access the collected data.
Compliance Access compliance rules that you create based on the collected vCloud
Director data using the Virtual Environment Compliance node. You
cannot create enforceable compliance rules for vCloud Director data.
The compliance rules for the virtual machines that you license and on
which you install the Agent are managed in the Machine Group
Compliance node.
Reports Run a configured vCloud Director report. Click Reports and select
Machine Group Reports > Virtual Environments > vCloud Director
Managed VMs. The report includes the vCloud Director Instance,
Organization, Organization virtual datacenter, vApp Name, the VC
Machine Name, and the related networking data.
Create reports based collected vCloud Director objects. Click Reports
and select Virtual Object Reports.
vCenter Configuration Manager Administration Guide
38
VMware, Inc.