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
n
Verify that the machine on which you intend to install the Agent has enough free disk space. For more
information, see the VCM Installation Guide.
n
If you run an installation in silent mode, modify the appropriate csi.config file variable options. See
"Installation Options for UNIX/Linux csi.config " on page 113.
n
If you select (x)inetd/launchd for CSI_AGENT_RUN_OPTION, verify that (x)inetd/launchd is
running on the target machines. On some versions, when (x)inetd/launchd services are not
configured, (x)inetd/launchd will not stay running. To ensure the Agent installation finishes
successfully, pass a - stayalive option to (x)inetd/launchd. See "Installation Options for
UNIX/Linux csi.config " on page 113.
n
Log in to the target UNIX/Linux machine as root.
n
Disable or reconfigure firewalls on SUSE and Red Hat machines to install the Agent.
n
Select the method that you want to use to copy files to the target machines. You can use ftp, sftp, or
cp using an NFS share. If you use ftp to copy the package to your machine, you must use binary
mode.
Procedure
1. Copy the appropriate Agent binary installation package from the Collector to the machine on which
you will install the Agent.
The Agent packages are located on the Collector in \Program Files
(x86)\VMware\VCM\Installer\Packages.
Operating SystemVersion Agent Binary
Red Hat (Enterprise) Linux Edition (Version 3.0,
4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5, 5.6, 5.7, 6, 6.1, 6.2). Red
Hat 3.0 requires the CMAgent.5.4.0.Linux Agent.
SUSE Linux Enterprise Server (9, 10.0–10.4, 11.0–
11.1),
Debian (4). SUSE 9 requires the
CMAgent.5.4.0.Linux Agent.
CMAgent.<version>.Linux
Solaris (Versions 9 and 10 supported on Sparc)
CMAgent.<version>.SunOS
Solaris (Version 10 for x86)
CMAgent.<version>.SunOS.x86.5.10
HP-UX 11i Versions 1.0, 2.0, 3.0 (11.11, 11.23, and
11.31; Supported on PA-RISC)
CMAgent.<version>.HP-UX.11.pa
HP-UX 11i Version 2.0, 3.0 (11.23 and 11.31-
Supported on Itanium)
CMAgent.<version>.HPUX.11.ia64
AIX Version 5L (5.3, 6L (6.1), 7.1)
CMAgent.<version>.AIX.5
2. On the target machine, run chmod u+x <filename> to set the execute permission for the file owner
on the Agent binary file.
3. In the directory to which you copied the file, run ./CMAgent.<version>.<Agent binary name> to
create the necessary directory structure and extract the files.
vCenter Configuration Manager Administration Guide
110
VMware, Inc.