Just a quick blog that these day’s it can be very difficult or very simple in regards of troubleshooting and resolving issues in a deployment. Let me take you on a journey 😉
Journey 1:
UAG deployment fresh as fresh and no working logon page after a valid deployment, at first troubleshooting, troubleshooting, redeployed with the customer and still the same result, validated across versions, vSphere, UAG etc. and to no effect.
Double checking with the customer, checked all the boxes and redeployed again, noted the password…. Asked the question does it adhere to the requirements? It was as simple as that the password was long enough but not complex enough:
Passwords must be at least 8 characters long, contain at least one uppercase and one lowercase
letter, one digit, and one special character, which includes ! @ # $ % * ( ).
Warning: IF YOU LEAVE THE PASSWORD BLANK, AN ADMIN UI USER WILL NOT BE CREATED, AND YOU WILL NOT BE ABLE
TO CONFIGURE ANY SETTINGS ON THE APPLIANCE. YOU WILL HAVE TO REDEPLOY THE UAG APPLIANCE WITH A PASSWORD
TO USE THE ADMIN UI.
So, after changing this in the customer environment it worked just as expected.
Journey 2:
VMware Access connector latest version, needed for the CSP federation of VMware Cloud services which combines from the following: What is enterprise federation and how does it work (vmware.com) straight from the installation/configuration so that the connector will sync with the new broker tenant, error and no installed services. What the… okay troubleshooting again, all pre-requisites are checked, downgraded to an earlier version and no no no, the installation always completes no errors whatsoever and moving on to a completed state. Checked it again and what was different to other deployments or my lab for that matter. Well turns out that the configuration json with the password for registration to VMware Cloud was not valid, the logs eventually showed it in the entries of the access connector installation directory and the directoryservice/userauthservice entries which mentioned an error on configuring service with the mentioned prepopulated password. Resolution new password 14 characters long and complex via trusty old dashlane and presto also working here.
In summary, some problems start small and some problems start big but in the end keep pushing and you’ll get there.
Hope it helps!