View Single Post
  #4  
Old 07-08-2020, 11:05 AM
hawki32 hawki32 is offline
Member
 
Join Date: Jan 2016
Posts: 7
hawki32 has 11 reputation points
Default AADS tips

I have found similar issues in the past with my deployments as well.
The most common big fixes for me have been:


Make sure there is no variable sharing characters [$ or %] in any of the deployment passwords (keystore, enrollment, ect)


Make sure AADS is on the same subnet as the Session Manager it will sync its database with.


Verify FQDN resolution between AADS and System Manager works (either through proper DNS management or manually via Host file entries on both servers)



Don't typo your front end host names and the like during the app install process.


Choose System Manager v7 even if your System Manager is v8.


*On AADS 8+ you can put in incorrect LDAP info (as long as the format meets requirements) and you will receive a warning about it not being able to connect but you can still proceed and get the services started - if you just want a newer Utility Server running from it for example.
Reply With Quote