Login as root and run the following commands hostname in certificate didn’t matchįIX: Access the configurator-va console. Error Creating Admin User – This occurs because in the original configurator setup the gateway was changed to a more familiar FQDN, now the certificates are wrong and the gateway has two hostnames (DNS entries for the gateway-va and the alternate FQDN)Įrror Message: Error creating admin user. If it can’t find it, you’ll get yelled at with a “Bad Gateway!” message and then: Shut. The configurator-va will try and resolve it via DNS. Choose an external FQDN for external access, assign it an IP in DNS. If not, the configurator-va will give you the virtual finger and, yep, shut down. Have the static IPs for all 5 VAs in DNS and ensure you have a reverse lookup zone in place. Reverse DNS must be in place for all 5 VAs. If you list more than one, the configurator-va appliance will tell you to fix it and then shut down. This will bite you in the ass if you put multiple DNS servers in the assigned IP Pool. I didn’t enable the pool it just needs to be available.
Create an IP Pool at the Datacenter level in vSphere and assign it to the dVS port group that will connect the vApp.
Hopefully these notes will help someone down the road, namely me, since I will probably have to do it again in two months. Installing and configuring the 5 Virtual Appliance vApp Horizon-Workspace was no walk in the park. Sometimes it seemed like there was no hope on the Horizon.
0 kommentar(er)
