$theTitle=wp_title(" - ", false); if($theTitle != "") { ?>
About Virtualization, VDI, SBC, Application Compatibility and anything else I feel like
14 Oct // php the_time('Y') ?>
Recently support for NPAPI has been removed from Google Chrome. While understandable from a security point of view it does mean that some plugins no longer work.
A good example is VMware’s Client Integration Plugin where we’ve lost the ability to upload an ovf template. While VMware has published a fix for vCenter (see this kb), it has not been fixed for vCloud Director:
To upload the ovf you need ovf tool (as the warning indicates), this comes with the integration plugin, on my machine it’s located in c:\Program Files (x86)\VMware\Client Integration Plug-in 6.0\ovftool.exe
.
William Lam’s blog article describes the procedure with ovftool with the following example commandline:
1 | ovftool --acceptAllEulas /Users/lamw/Desktop/vCO_VA-5.1.1.0-1070383_OVF10.ova "vcloud://username:password@vcloud-director-ip-or-hostname:443?org=TechMarketing&vappTemplate=vCO-5.1u1&catalog=WorkInProgress&vdc=TM-Allocation1-ovDC" |
It’s a bit troublesome to form the vcloud locator as we need to escape special characters such as spaces and combine all the arguments with & characters.
So I created a PowerShell script that wraps ovftool and makes this all nice and easy for you. Let’s see how it works!
If you don’t specify parameters, the script will ask you for Catalog, Computername, Organization and Credentials:
The script has a hardcoded path to ovftool but if it cannot find it will popup a browse dialog:
Leave a reply