When installing various VMware products that link into vCenter (vShield, vCloud Connector, vChargeback, I could go on..), you often have minimal control over what URL is actually used to browse to the plugin and you usually can’t change it later on. This can screw up your SSL certificate plans.
After a little digging, I found these tables in the SQL database:
- VPX_EXT_CLIENT
- VPX_EXT_SERVER
Both have a field called ‘URL’ which has the URL (doh) to the plugin.
Two things; this is not supported by VMware and could break something. I hasn’t on my setup, but it might on yours. Backups are your friend.
You need to stop the vCenter service before you edit the value and start it back up after you’re done.
A love for Apple’s OSX and computing devices brings some side effects. One of them is that you’re stuck with VMware Fusion which is way behind it’s Windows counterpart, VMware Workstation. Fusion cannot import .ovf VMs, just .vmx VMs. In my case, I needed to convert the vSphere Management Appliance to a VM that could run in VMware Fusion.
It took me a while to this neat tool: http://communities.vmware.com/community/vmtn/server/vsphere/automationtools/ovf -Â ovftool is a utility that can convert virtual machines between certain formats.
Once you have it downloaded and installed, you can use the commandline tool to convert the .ovf to a .vmx like this:
ovftool --acceptAllEulas vMA-4.1.0.0-268837.ovf vMA.vmx
Then just double click or import the .vmx into Fusion
@arjancool jup, werkplekje thuis :-) 5 days ago
This is the Popup Widget. Add any widget to the popup widget position, and place anywhere Gantry Popup widget to trigger the RokBox.
You can configure its height and width from the widget settings.
More Information