Manual Install of UAG 2010/Remote App and RDS Portal Components

Posted by Ahmed Nabil In | 0 comments»
Microsoft UAG 2010 main functions are Application Publishing and Enhanced DirectAccess deployment. The Application publishing allows you to publish several applications on either HTTP or HTTPS trunk. Application publishing includes Web applications, Non-Web applications, Remote Desktop Services (RDS), RemoteApps and VPN services.

When accessing the UAG portal for the first time from your computer using one of the supported browsers (Please check the Client requirements and Supported browsers in the user will be prompted to download and install the UAG endpoint components, these components are used in many things among them checking device (Endpoint detection), SSL tunneling……………etc. This installation is done once per computer.

Some clients have restricted Internet Explorer settings (Using Group Policies) that prevent them from installing MSI or EXE files from the Internet and they need to install the Endpoint components manually.

There are two types of clients that you need to install manually to fully utilize the UAG portal.

1.    UAG Client Components, these are available on the UAG server under

 C:\Program Files\Microsoft Forefront Unified Access Gateway\von\PortalHomePage
Several files are available under this location for each component or you can just take the WhlClientSetup-all.msi from this location and have your users install it manually (Of course they need to have admin rights on their computer). Make sure you are running the latest UAG version on your server. The current latest version is 4.0.1773.10110

When manually installing the WhlClientSetup-all.msi, the users will be given the choice for Typical installation or Custom Installation to pick specific components as per the below screenshot.
Forefront UAG 2010 client components installation options

2.    Remote Desktop Services (RDS) and RemoteApp need the latest Remote Desktop Connection 7.0 client update for Remote Desktop Services (RDS) for Windows XP SP3, Windows Vista SP1/SP2 which can be downloaded from the following site  

This RDC 7.0 client is already installed by default on Windows 7 systems. If you using Network Level Authentication (NLA) on the RDS servers then you need to check this article since the NLA is disabled on XP service pack 3.

Once both components (UAG and RDS) are installed manually, the user will be prompted to approve running the ActiveX and adding the portal site to the browser trusted sites.

DNS64 Not Healthy after Applying UAG SP1 Update 1 Rollup 1

Posted by Ahmed Nabil In | 5 comments»
After applying the latest Rollup 1 for UAG SP1 Update 1 released on Jan 12, 2012 I noticed that the DNS64 is unhealthy under the Direct Access Monitor/Current status as shown in the below figure.

DNS64 not healthy

I did a reboot to the UAG/Direct Access server (although it’s not required by the fix) however the DNS64 component still showed unhealthy. I disabled/enabled direct access as follows:
1.     Disabled Direct Access
2.     Saved/Activated the configuration
3.     Enabled Direct Access
4.     GPupdate /force on the UAG Server
5.     Applied the policy
6.     Activated the configuration
After that it all worked fine. I am not sure about the reason (Will try to check with Microsoft Team) however that workaround fixed my problem.

Publishing Direct Access Web Monitor on UAG Portal

Posted by Ahmed Nabil In , | 0 comments»
Recently I tried publishing the UAG Web Monitor on my External HTTPS Web Portal, the UAG web monitor is very useful monitoring and reporting web application which gives you the ability to view different UAG sessions, applications, Direct Access and the UAG event viewer.

When the UAG Web Monitor is published on the UAG Portal Trunk everything works fine except the Direct Access section (Current Status and Active Sessions). When you try to open the Current Status or Active Sessions you get the below error screen.

UAG web monitor

This issue looks like a bug with the UAG and I opened a support case with Microsoft and they are considering a permanent fix. Currently to fix this issue you need to add 5 rules as follows:

  1. Go to the Trunk Configuration - Configure Trunk Settings - Configure - URL set.
  2. Copy any Web Monitor default rule and paste it 5 times
  3. Modify/Add the URL in the 5 rules as follows:
    1. /damonitor\.asp
    2. /damonitorcurrentstatus\.asp
    3. /damonitorcurrentstatusrefresh\.asp
    4. /damonitoractivesessions\.asp
    5. /damonitoractivesessionsrefresh\.asp
  4. Save- Activate and this should fix the issue.

Here is a Screen shot of how these rules should be added and modified.

UAG advanced Trunk configuration