Skip to main content

Unable to upload and download images or OVF into vCloud director

Recently I got an issue from one of my customer where they were unable to upload or download the files from vCloud Director. At the time or upload or download files into catalog, its prompting below error and ask for download the Client integration plugin, even though the CIP is already installed into the machine from where we are trying to upload the image into Vcd.

“The Client integration Plugin-in must be installed to enable OVF upload and download functionality. Click the link below to download installer. When the download has completed, you must close your browser before you can install the plugin”

To resolve the issue we have followed below steps.

If you are using Internet Explorer 11 and above and facing same error. Please follow below steps to resolve the issue.

1)       Make sure your VCD FQDN is listed into trusted site.

2)       Enable Compatibility mode.

3)       When you load vCloud Director into Internet Explorer, press F12 and it will show the Developers Bar, at the bottom, go  to the Emulation Tab .
        If page is loading as Document Mode: EDGE then It will not Load.
        If the Document mode says 5, 7, 8 or 10 , then it will load the Client Integration plugin without any issue.

4)       Remove any previously created ovftool configuration file: 

        On Windows: Rename ovftool.cfg from "C:\Users\<username>\AppData\Roaming\VMware" 
        On Linux: Rename "ovftool_ssldb" file from the user's home directory (\root for the user root) 
5)       Remove previously created any ovftool settings file 

        On Windows: Rename .csp_ovftool_settings from "C:\Users\<username>\AppData\Roaming\VMware"
        On Linux: Rename ".csp_ovftool_settings" from the user's home directory (\root for the user root)

If you are using Google Chrome and above and facing same error. Please follow below steps to resolve the issue.

1)       Follow below VMware KB 2150215 (

Happy Sharing …J


Popular posts from this blog

Changing the FQDN of the vCenter appliance (VCSA)

This article states how to change the system name or the FQDN of the vCenter appliance 6.x You may not find any way to change the FQDN from the vCenter GUI either from VAMI page of from webclient as the option to change the hostname always be greyed out. Now the option left is from the command line of VCSA appliance. Below steps will make it possible to change the FQDN of the VCSA from the command line. Access the VCSA from console or from Putty session. Login with root permission Use above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_net Opt for option 3 (Hostname) Change the hostname to new name Reboot the VCSA appliance.   After reboot you will be successfully manage to change the FQDN of the VCSA . Note: Above step is unsupported by VMware and may impact your SSL certificate and face problem while logging to vSphere Web Client. If you are using self-signed certificate, you can regenerate the certificate with the

Collecting Logs from NSX-T Edge nodes using CLI

  This article explains how to extract the logs from NSX-T Edge nodes from CLI. Let's view the steps involved: 1) Login to NSX-T  Edge node using CLI from admin credentials. 2) Use of  " get support-bundle " for Log extraction. get support-bundle command will extract the complete logs from NSX-T manager/Edge nodes. nsx-manager-1> get support-bundle file support-bundle.tgz 3) Last step is to us e of " copy file support-bundle.tgz url " command. copy file will forward your collected logs from the NSX-T manager to the destination(URL) host from where you can download the logs. copy file support.bundle.tgz url scp://root@ Here, the URL specified is the ESXi host ( under /tmp partition where logs will be copied and from there one can extract it for further log review. Happy Learning.  :)

Removing NSX-T manager extension from vCenter

In NSX-T starting from ver 2.4 NSX-T appliance got decoupled from vCenter where now its not mandatory to run NSX-T on vCenter platform only. Now NSX-T can be managed through standalone ESXi host, KVM or through container platform. As in version 2.4 there is still an option available to connect vCenter to NSX-T using Compute Manager. Here in this blog we will learn how we can unregister and register NSX-T extenstion from vCenter in case of any sync or vCenter connectivity issue with NSX-T. Lets get started.. 1) Login to NSX-T UI Go to -> System ->Compute Manager Here, vCenter is showing in Down status where the status is showing as "Not Registered" 2) When we click on "Not Registered" option its states below error. 3) When try to click on Resolve option its states below. At this stage if the Resolve option doesn't work then its require the remove the NSX-T extenstion from vCenter. To remove the NSX-T e