To Resolve the Problem
1. Open a command prompt.
2. Navigate to the
C:\Program Files\VMware\VCM\AgentData\protected
directory, and delete
these two files:
ECMv.csi.pds
and
ECMv.csi.pds.lck
.
3. Execute the following command:
GenerateAgentProxyKeys.cmd
.
4. Verify that the following files were generated:
<machine>_securecomm_public_key.txt
<machine>_ssh_public_key.txt
5. From the command prompt, execute the following command:
DatabaseUploadKey.cmd
<machine>_securecomm_public_key.txt
(where <machine> is the name of the Agent Proxy
machine).
For more information about generating key pairs on the Agent Proxy Machine, see Chapter 6.
Resetting the Required Secure Channel (SSL)
When using SSL on the VCM collector, the following settings must be configured for VCM to work
properly with SSL:
n
Web.config file in the WebConsole directory
n
Require secure channel (SSL) setting in IIS – for the VCM virtual directory
n
IIS HTTP string http or https Database setting in VCM
When upgrading the Collector, the Require secure channel (SSL) check box in the VCM virtual directory
properties may become unchecked. This problem can occur on a VCM Collector that is using SSL, when all
of the settings listed above have been configured.
After upgrading VCM, log in and verify whether https is still required. If not, confirm that the settings to
the Web.config configuration file, the VCM virtual directory, and the IIS settings are correct by using the
procedures described in the sections below.
Updating the Web.config Configuration File
To modify the Web.config file, follow these steps:
1. On the Client/Collector machine where the SSL Certificate was issued, navigate to
C:\Program
Files\VMware\VCM\WebConsole
.
2. Locate the
Web.config
file using Internet Explorer. Disable the
read-only
check box so that you can
save the file by right-clicking the file, select
Properties
, and then uncheck the
read-only
check box. Click
OK
.
3. Open the
Web.config
file using Notepad.
4. In the
Web.config
file, search for the following tag:
<add key="WebConsole.ReportingServices.ReportingService"
value="https://COLLECTORNAME/ ReportServer/ReportService.asmx"
5. Verify that the URL listed after value begins with
https
instead of
http
.
Troubleshooting Problems with VCM
VMware, Inc.
261
Summary of Contents for VCENTER CONFIGURATION MANAGER 5.3
Page 8: ...vCenter Configuration Manager Installation and Getting Started Guide 8 VMware Inc...
Page 46: ...vCenter Configuration Manager Installation and Getting Started Guide 46 VMware Inc...
Page 158: ...vCenter Configuration Manager Installation and Getting Started Guide 158 VMware Inc...
Page 178: ...vCenter Configuration Manager Installation and Getting Started Guide 178 VMware Inc...
Page 194: ...vCenter Configuration Manager Installation and Getting Started Guide 194 VMware Inc...
Page 204: ...vCenter Configuration Manager Installation and Getting Started Guide 204 VMware Inc...
Page 208: ...vCenter Configuration Manager Installation and Getting Started Guide 208 VMware Inc...
Page 234: ...vCenter Configuration Manager Installation and Getting Started Guide 234 VMware Inc...
Page 264: ...vCenter Configuration Manager Installation and Getting Started Guide 264 VMware Inc...
Page 274: ...274 VMware Inc vCenter Configuration Manager Installation and Getting Started Guide...