Console Access to VMware vCloud Director might not work after upgrade

When customers upgrade from VMware vCloud Director (vCD) 5.5.6 (or some other version) to f. ex. 8.0.2, they may run into the problem that console access to a virtual machine (VM) in a vApp doesn’t work (you see Disconnected in your browser). In the following, I used my testlab with vCD 8.20.0.2, Microsoft Server SQL Server (MS SQL), and a Microsoft Windows 7 (MS Win 7) client. By the way, I would recommend using Mozilla Firefox ESR (Extended Support Release). I have linked an ESR Overview https://www.mozilla.org/en-US/firefox/organizations/faq/ and the Download location https://www.mozilla.org/en-US/firefox/organizations/all/

There are two ways accessing the console of a VM in vCD:

  1. WebMKSConsole (recommended according to https://kb.vmware.com/kb/2117384)
  2. VMRC (requires VMware CIP and Browsers to use NPAPI)

Let us start.

1. WebMKSConsole

WebMKSConsole with Mozilla Firefox ESR:

Console displays DISCONNECTED – please see the versions involved:

According to https://kb.vmware.com/kb/2117384 you first need to insert some values into the SQL Server database:

As these settings are used for VMRC, you need to change them according to the article mentioned above (or https://kb.vmware.com/kb/2145111 as well):

But you may not be able to access the console. Following describes my steps:

Trust the certificate of the console proxy and with the help of Microsoft Internet Explorer 11 (MS IE), install/import the certificate with the corresponding assistant in Windows.

After you have installed/imported the certificate of the consoleproxy, you should be able to access the console:

WebMKSConsole with Microsoft Internet Explorer 11:

If you are using MS IE as well, you first need to change the database setting:

In MS IE you need to make sure to use compatibility views by adding the website of the consoleproxy. Then access should be fine:

2. VMRC

Using VMRC with Mozilla Firefox ESR:

As the database values already exist in our case, we change them:

After restarting Mozilla Firefox ESR, you need to install the Client Integration Plug-in (see https://kb.vmware.com/kb/2145401 for more information):

Next, allow the plug-in:

Access should be fine now:

Using VMRC with Microsoft Internet Explorer 11:

As the database value already exists in our case, we change it:

Advertisements

Firefox: CONSOLE ACCESS TO VCLOUD DIRECTOR 8.20 VIA WEBMKS

In my previous post about Google Chrome I already described what you might need to do with your certificates to get connected to the console of a VM in a vApp.

Here you will find a step by step description for Firefox and Adobe Flash Player

Access your vCloud Director Portal:

Adobe Flash Player:

flash1

So here you need to configure Firefox to accept the Flash Plugin (enter about:config):

Create a Boolean entry:

Set to true:

After these steps, go ahead connecting to your console port proxy (8443 in my case):

If you see the white and empty browser window, everything is good. Go ahead with downloading and installing the Adobe Flash Player Plugin.

After restarting your browser you are finished:

Google Chrome: Console access to vCloud Director 8.20 via WebMKS

Access to your vCloud Director frontend is working but you may have had the following problem accessing a console of a VM in a vApp:

Disconnected

Assuming you use port 8443 for your console port, you get the following:

IE_no_secure_connection

Click Advanced:

IE_no_secure_connection_advanced

So let’s go to fix it:

You need to use Internet Explorer to deal with the certificates. So you start like described above. After you continue to the insecure webpage:

IE_no_secure_connection_insecure

You see the Certificate error:

IE_no_secure_connection_Certificate_error

You need to be Administrator to import the certificate. Click on the untrusted certificate, View certificates:

IE_no_secure_connection_Certificate_error_View

Next is to install it:

IE_no_secure_connection_Certificate_Install

Use the wizard:

Import1

Import2

Click Browse and select Trusted Root Certification Authorities:

Import3

Import4

Import5

Import6

Import7

After you have restarted your Internet Explorer, connecting again to the console port you see no longer a Certificate error:

Import8

Now you go back to Google Chrome, see version used here:

Connected