Can you tell us a little more about your DNS configuration?
What did you specify as the FQDN during the CLI based setup? Is this different than the host name of your gateway?
Can you please check the logs in:
HHHmmmmm, this 1.0 release is certainly frustrating.
Third time lucky, everything worked perfectly ... except ..... the admin password set during the wizard.
So now users can log in no problem, but no admin from AD or 'admin'. GGGrrrrrrr
Does anyone know how to reset the 'admin' user password from the VA's themselves, I am able to root into those no problem.
Or will I be going for a 4th deployment ?
Are you saying you don't have a AD admin user to login to horizon workspace?
The BindDN user is automatically the first admin user in horizon workspace. You can login to https://<horizon fqdn>/admin and use that user's username and password.
OK ! ... better luck this time. I can get in using the 'admin' user.
However, if I try to log in using as domain account I get the following erro:
Yes, have now tried both our private cert, and I registered a new cert from GeoTrust. Both result in the same error.
Have added the root CA's for both as per the documentation but the same error occurs.
I see there is another discussion on exactly the same issue, I'll watch with interest, but for now I've gone back to the self signed versions.