User`s guide
Table Of Contents
- VMware vCenter Configuration ManagerInstallation and Getting Started Guide
- About This Book
- Preparing for Installation
- Installation Manager
- Installation Configurations
- Tools Installation
- General Prerequisites to Install VCM
- Verify Hardware and Software Requirements
- Verify Administration Rights
- Set the Default Network Authority Account
- Specify the Collector Services Account
- Change the Collector Services Account Password in the Services Management Con...
- Change the Collector Services Account Password in the Component Services DCOM...
- Verify the VMware Application Services Account
- Determine the VCM Remote Virtual Directory
- Use Secure Communications Certificates
- Understand Server Authentication
- Verify the Foundation Checker System Checks
- Install UNIX Patch for HP-UX 11.11
- VCM Uses FIPS Cryptography
- Installing VCM
- Installing, Configuring, and Upgrading the OS Provisioning Server and Components
- Upgrading or Migrating VCM
- Upgrades
- Migrations
- Prerequisites to Migrate VCM
- Back Up Your Databases
- Back up Your Files
- Export and Back up Your Certificates
- Migrating VCM
- Migrate Only Your Database
- Replace Your Existing 32-Bit Environment with a Supported 64-bit Environment
- Migrate a 32-bit Environment Running VCM 5.3 or Earlier to VCM 5.4.1
- Migrate a 64-bit Environment Running VCM 5.3 or Earlier to VCM 5.4.1
- Migrate a Split Installation of VCM 5.3 or Earlier to a Single-Server Install...
- How to Recover Your Collector Machine if the Migration is not Successful
- Upgrading VCM and Components
- Maintaining VCM After Installation
- Getting Started with VCM Components and Tools
- Getting Started with VCM
- Discover, License, and Install Windows Machines
- Discover, License, and Install 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
- Discover, License, and Install UNIX/Linux Machines
- Discover, License, and Install Mac OS X Machines
- Discover, Configure, and Collect Oracle Data from UNIX Machines
- Customize VCM for your Environment
- How to Set Up and Use VCM Auditing
- Discover, License, and Install Windows Machines
- Getting Started with VCM for Virtualization
- Getting Started with VCM Remote
- Getting Started with VCM Patching
- Getting Started with Operating System Provisioning
- Getting Started with Software Provisioning
- 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
- Getting Started with VCM Management Extensions for Assets
- Getting Started with VCM Service Desk Integration
- Getting Started with VCM for Active Directory
- Installing and Getting Started with VCM Tools
- 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 Hardware and Software Requirements 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 118.
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 completes
successfully, pass a - stayalive option to (x)inetd/launchd. See "Installation Options for
UNIX/Linux csi.config " on page 118.
n
Log on 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 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 SystemVersion Agent Binary
Red Hat (Enterprise) Linux Edition (Version 3.0,
4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5, 6)
SUSE Linux Enterprise Server (9, 10, 11, 11.1),
Debian (4)
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 and 6L (6.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.
To force an overwrite of any existing files, include the -o option. For example:
/CMAgent.<version>.SunOS -o.
The command and output is similar to the following example, but with different file names depending
on the operating system.
Getting Started with VCM
VMware, Inc. 115