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 (https://kb.vmware.com/kb/2150215)

Happy Sharing …J

Comments

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...

VCF 9 Networking : Centralized vs Distributed Connectivity

VCF 9 Networking : Centralized vs Distributed Connectivity With the release of VMware Cloud Foundation 9 (VCF 9.0) , VMware has redefined the private cloud networking model by introducing both centralized and distributed connectivity. This dual approach provides flexibility for organizations to choose between traditional edge-based routing and modern, host-level distributed networking. Why New Networking in VCF 9? Prior to VCF 9, NSX networking was largely edge-centric—requiring dedicated Edge clusters to handle north-south traffic. This created scaling and operational overheads. VCF 9 introduces a cloud-like networking abstraction with: Native VPCs (Virtual Private Clouds) for tenant isolation. Transit Gateways (TGW) to interconnect VPCs and external networks. Simplified bootstrapping – NSX VIBs are embedded in ESXi for easier enablement. Improved lifecycle and visibility via integrated VCF Operations. These enhancements align with VMware’s goal of offer...

High-Speed Networking for VMs: VMXNET3 Now Supports Up to 65 Gbps

The VMXNET3 adapter is VMware's high-performance virtual network adapter, designed for optimized performance in vSphere environments. It is the default and recommended adapter for most modern workloads on ESXi , delivering high throughput, low latency, and support for advanced networking features. With the release of vSphere ESXi 8.0 Update 2 , VMXNET3 introduces new capabilities that significantly enhance virtual network performance. What’s New in ESXi 8.0 Update 2 for VMXNET3? Traditionally, VMXNET3 reports a default link speed of 10 Gbps to the guest operating system. However, the actual achievable throughput often exceeds this value—thanks to technologies such as multi-queue support , Receive Side Scaling (RSS) , and Large Packet Offload . Starting with ESXi 8.0 Update 2 , this limitation can now be overridden , and VMXNET3 can be configured to support custom link speeds of up to 65 Gbps . This enhancement enables improved flexibility and throughput for high-performance w...

Search This Blog