Most of the errors you might encounter while using UAG give a clear indication of what the problem is, assuming the concepts of how UAG works and what it does are clear. For example, a common error happens during activation, if the UAG server is unable to resolve the hostname of a server you have defined in an application. This error is quite verbose and usually makes sense and points you in the right direction. Troubleshooting it would involve basic networking skills—check if UAG can contact its DNS server, and if that DNS server responds to queries properly.
When thinking about administrative issues, one must understand the way UAG works and the intricate relationship it has with other components. The administrator configures settings in the UAG management console, and these are saved as an EGF file on the local hard drive. Only upon activation do these changes get applied to the actual configuration. When an activation is performed, UAG configures IIS by creating...
