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
1. Installation wizard Object level credentials
2. Installation wizard Job level credentials
3. Administrative parameter Machine context credentials
4. Administrative parameter Machine Group context credentials
5. Administrative parameter Domain context credentials
6. Administrative parameter SRF Action Script Global context credentials
Credential Processing Scenarios
The following scenarios further demonstrates how the credentials are processed.
n
You do not provide object or job level credentials, nor did you configure any administrative
parameters.
The installation job fails due to lack of credentials.
n
You provide object or job level credentials, but you did not configure any administrative parameters.
The installation job runs using the credentials you provided in the installation wizard.
n
You do not provide object or job level credentials, but you already configured administrative
parameters for one or more of the credential contexts, which are Machine, Machine Group, Domain, or
SRF Action Script Global.
The installation job runs using the credentials configured in the administrative parameters.
n
You provide user name and password credentials that have root privileges, in the installation wizard or
in the administrative parameters, but you do not provide the root password.
The installation fails due to insufficient privileges.
Configure Collections from Linux, UNIX, and Mac OS X Machines
To collect Linux, UNIX, and Mac OS X data from your virtual or physical machines, you must install the
VCM Agent. To install the Agent, you must configure an Installation Delegate, either the Collector or
another Windows machine, add the target machines, license them for use, and install the VCM Agent.
Procedure
1. "Configure Installation Delegate Machines to Install Linux, UNIX, and Mac OS X Agents" on page 121
The Installation Delegate machines are one or more virtual or physical machines that manage the
communication between the Collector and your target Linux, UNIX, or Mac OS X machines during the
VCM Agent installation process.
2. "Configure the HTTPS Bypass Setting for Linux Agent Installations" on page 123
If your Collector is not configured to use HTTPS, you must configure the Collector to allow HTTP
communication when entering sensitive parameter values.
3. "Enable Linux, UNIX, and Mac OS X Agent Installation" on page 123
You configure the Enable Automated Linux Agent Install option so that you can use VCM to install the
Agent on Linux, UNIX, and Mac OS X machines.
4. "Add and License Linux, UNIX, and Mac OS X Machines for Agent Installation" on page 124
You must add and license Linux, UNIX, and Mac OS X machines so that you can install the Agent
manage them in VCM.
vCenter Configuration Manager Administration Guide
120
VMware, Inc.