5.8

Table Of Contents
n IPC$share must exist.
RPC uses IPC$.
n Windows Server Service must be running.
The Collector uses the server services to resolve the target machine's share to a local path to register
the bootstrap service, the Registration Service, with the Remote Service Control Manager (SCM).
n You must be able to attach to the share files using the credentials provided during installation.
n DNS must correctly resolve the machine and share to the appropriate machine.
n Collector service authority must correctly attach to the SCM.
n DCOM must be set to receive DCOM creation requests for various components. DCOMrequires the
following settings.
n DCOM must be enabled on the target machine. On Windows 2003 Servers, this option is turned off
by default.
n On machines running the Windows NT operating systems, configure the default DCOM security
authorities for Access, Launch, and Configuration.
n Verify that the default authentication level is Connect and that the default Impersonation level is
Identify.
Windows Agent Installation Collector Credentials
The Collector must have domain accounts with the necessary domain authority so that you can install the
VCM Windows Agent on your target physical or virtual machines.
In VCM, define one or more domain administrator accounts in the Available Accounts data grid. These
accounts are associated By Domain or By Machine Group with each target machine. You can configure
multiple accounts that are specified in priority order.
When you install the Agent, the Collector cycles through these accounts until it locates the account needed
to establish communication with each target machine.
Configure the accounts in VCM in the network authority available account settings.
Windows Agent Installation Process
When you install the VCM Windows Agent from the Collector using install Agent action rather than a
manual action, the installation process comprises many steps, the success and failure of which are tracked
in the Jobs Manager. If an Agent installation fails, you can evaluate the job as it is running or view the
details in the history to determine which part of the process you must evaluate more closely.
Review the job history, identify the step that failed, and determine what might be impeding the
installation of the Agent.
Detect Previous Install
The detect previous install action evaluates the target Windows machine to determine whether a previous
version of the VCM Agent is installed.
When installing VCM 4.11.x Agent or later, if a previous Agent version is detected, VCM must remove it
before installing the new Agent.
VCM Troubleshooting Guide
42
VMware, Inc.