I have been working with AX just a short time and have encountered an issue with the client not using the FQDN provided in the client configuration to connect to the AOS. On my laptop it will connect because I have the correct DNS suffix set at the top so my laptop generates the correct FQDN to connect. On our Virtual Desktop systems and computer lab systems the network settings don't have any DNS suffixes set. So the client tries to pass an invalid FQDN (AOShost.desktopdomainname.edu instead of AOShost.serverdomainname.edu) and can't connect to the AOS.
So is there a way to ensure that the client uses the correct FQDN to connect to the AOS server? I've tried using the command line but the Ax32.exe -aos2=host.FQDN doesn't connect either. The registry setting has the correct host.FQDN set. So I'm not sure what else to check.
I'm not sure how open the campus desktop support group will be to modifying their standard installs for a large number of computers for the AX client. So I'm hoping a forum member has some insight to help.
Thanks.