Hi! I'd like to know if this is (or will be) compatible with vCenter 7.0, thank you!
There is little point considering that these already have a full H5 client now. It would probaby be better to look at the beta program
Deployed a brand new one. booted up, connected to my SSO, and nothing. days the client is running, but no matter what, nothing comes up when I hit https://<IP Address>/ui/ tried to stop start, tried to reboot, just nothing at all. Just times out. What am i missing?
I had to do it all from the CLI, the web interface was just not getting things setup and working. SSH in and then followed the directions and that got it mostly working. Now I getthis when trying to log in. [400] An error occurred while sending an authentication request to the vCenter Single Sign-On server - An error occurred when processing the metadata during vCenter Single Sign-On setup - Failed to connect to VMware Lookup Service
Hi,
There we several people with similar problems. Please search for the solutions in this forum and if the problem still persists we will try to help.
Best regards,
Kaloyan Iliev
h5ngcVA-5.0.0 -15670023_OVF supproted the vsphere 6.0 u3, the windows VC with embedded PSC?
HI jgdy,
It should work. Check the documentation.
If you have your old H5 fling appliance and if it was version 4+ you can directly copy the configuration files from it.
Copy the /etc/vmware/vsphere-ui/webclient.properties, /etc/vmware/vsphere-ui/store.jks and /etc/vmware/vsphere-ui/config/ds.properties to the same folders on the new appliance.
Make sure they are owned by the user vsphere-ui and have 770 permissions.
Just a quick tip for your current configuration files. Can you check if they had Windows EOF?
$> hexdump -c /etc/vmware/vsphere-ui/webclient.properties
$> hexdump -c /etc/vmware/vsphere-ui/config/ds.properties
If you see in any of the dumps \r\n then you should remove all the \r from the file.
To remove the \r you can use the 'tr' command.
cat webclient.properties | tr -d '\r' > webclient.properties
Best regards,
Kaloyan Iliev
Is it possible to install an Update Manager plugin that will work with a Windows vCenter 6.7? I've tried putting a VCSA 6.7 package on the appliance and whitelisting it but no luck.