Installation guide

Installing on Windows with CMAgtInstall.exe
The CMAgtInstall.exe installer executable file does not contain certificates for Agents. Instead,
CMAgtInstall.exe requests the location of your VCM certificate, so you must have it preloaded on the
managed machine before installing. To do so, copy the certificate file with the .pem extension from the
CollectorData folder of the Collector.
NOTE The same guidelines apply if you are installing from an MSI installer.
Installing on Linux, UNIX, or Mac OS Packages
Each Linux, UNIX, or Mac OS X installation package is targeted for one or more supported platforms. If
certificates were specified when the Collector was installed, they are embedded in the Agent installation
package.
To manage the VCM UNIX Agent certificate store, use the CSI_ ManageCertificateStore utility and related
help provided with your UNIX Agent installation package. For more information about Linux, UNIX, or
Mac OS X Agent installation or packages and platforms, see the VCM Administration Guide.
Installing Using Provisioning
You can install the VCM Agent using a provisioning system or software push.
Installing the Agent with Provisioning on Windows
The manual installation program is available in EXE and MSI formats. Both versions allow you to specify
the Enterprise certificate file with a command-line switch. The certificate installation step can also be
omitted with a command-line switch. When these programs are run through a provisioning system, you
must ensure that the Enterprise certificate is available and still secure, and configure the program options
appropriately.
Alternatively, you can push the Enterprise certificate to Agents by some other means and configure the
provisioning system to omit certificate installation.
Installing the Agent with Provisioning on Linux, UNIX, or Mac OS X
Each Linux, UNIX, or Mac OS X installation package is targeted for one or more supported platforms. To
install the Linux, UNIX, or Mac OS X Agent using a provisioning system, extract the installation package as
appropriate, and deploy the extracted file with the provisioning system. The Enterprise certificate is
embedded in the installation package. For more information about Linux, UNIX, or Mac OS X Agent
installation, see the VCM Administration Guide.
Changing the Communication Protocol
For Windows Agents, you can change the communication protocol from DCOM to HTTP, or the reverse.
n
Changing the protocol to HTTP installs the EcmComSocketListenerService module. The current
Enterprise certificate is delivered with the EcmComSocketListenerService module.
n
Changing the protocol to DCOM uninstalls the EcmComSocketListenerService module from the Agent.
Because DCOM does not use certificates, the Agent stops using them. Changes to the Enterprise
certificate are not propagated to the Agent until you set the protocol back to HTTP, at which point the
current Enterprise certificate is delivered or redelivered.
Authentication
VMware, Inc.
67