Installation

Table Of Contents
Troubleshooting Certificate Issues on View Connection Server and
Security Server
Certicate issues on a View server prevent you from connecting to View Administrator or cause a red health
indicator to be displayed for a server.
Problem
You cannot connect to View Administrator on the View Connection Server instance with the problem. When
you connect to View Administrator on another View Connection Server instance in the same pod, you see
that the dashboard health indicator is red for the problem View Connection Server instance.
From the other View Connection Server instance, clicking the red health indicator displays SSL
Certificate: Invalid and Status: (blank), indicating that a valid certicate could not be found. The View
log le contains a log entry of type ERROR with the following error text: No qualifying certificates in
keystore.
The View log data is located in C:\ProgramData\VMware\VDM\logs\log-*.txt on the View Connection Server
instance.
Cause
A certicate might not be installed successfully on a View server for any of the following reasons:
n
The certicate is not in the Personal folder in the Windows local computer certicate store.
n
The certicate store does not have a private key for the certicate.
n
The certicate does not have a friendly name of vdm.
n
The certicate was generated from a v3 certicate template, for a Windows Server 2008 or later server.
View cannot detect a private key, but if you use the Certicate snap-in to examine the Windows
certicate store, the store indicates that there is a private key.
Solution
n
Verify that the certicate is imported into the Personal folder in the Windows local computer certicate
store.
See “Import a Signed Server Certicate into a Windows Certicate Store,” on page 84.
n
Verify that the certicate contains a private key.
See “Import a Signed Server Certicate into a Windows Certicate Store,” on page 84.
n
Verify that the certicate has a friendly name of vdm.
See “Modify the Certicate Friendly Name,” on page 85.
n
If the certicate was generated from a v3 certicate template, obtain a valid, signed certicate from a
CA that does not use a v3 template.
See “Obtaining a Signed SSL Certicate from a CA,” on page 82.
View Installation
96 VMware, Inc.