Release notes for Forefront UAG SP3

Applies To: Unified Access Gateway

These release notes address late-breaking issues for Forefront Unified Access Gateway (UAG) Service Pack Three (SP3).

If you are reading this help from the Forefront UAG Management console, the latest version of this topic is available in the Forefront UAG TechNet library.

  • Installation, upgrade, and administration issues

  • Client issues

  • Remote Desktop Services

Installation, upgrade, and administration issues

  1. We recommend that you add a restore point on the Forefront UAG server before running SP3 installation.

  2. You must install SP3 on a server running Forefront UAG SP2 as follows:

    1. Install Forefront UAG SP2. See Installing SP2 for Forefront UAG 2010.

    2. Install Forefront UAG SP3.

  3. We recommend that you do not have installations of other applications in progress when you install SP3 on an existing Forefront UAG server. Otherwise you might receive the following message during SP3 installation: “Setup failed during Forefront UAG prerequisites installation”. If you do receive this error, do the following:

    1. Restart the computer.

    2. Wait several minutes for any installations that are in progress to complete.

    3. Reinstall SP3.

  4. After installing SP3 on a Forefront UAG server acting as a Forefront UAG DirectAccess server, the DNS64 service will be set to Manual. Following the installation, set the DNS64 service to Automatic and start the service.

  5. For a summary of known globalization issues in Forefront UAG, see Compliance notes.

Client issues

  • When using Internet Explorer 10 on Windows 8 devices, ASP.Net on the Forefront UAG server does not correctly identify the browser. To resolve this issue, install the following hotfix on the Forefront UAG server:

  • Windows 8 DirectAccess clients cannot use one-time password authentication using RADIUS.

  • Client computers using Office 2013 and MSOFBA require the February 2013 cumulative update. See KB 953878.

Remote Desktop Services

You cannot use a server running Windows Server 2012 as a Remote Desktop Session Host to publish RemoteApps.