Forefront Unified Access Gateway (UAG) Service Pack 3 (SP3) is released! #sysctr


Today (February 20th, 2013) SP3 for Forefront UAG 2010 has been released. Besides bug fixes Forefront Unified Access Gateway (UAG) Service Pack 3 (SP3) provides a number of new features, including support for Windows 8 devices with Internet Explorer 10, and support for publishing Exchange Server 2013 and SharePoint Server 2013.

  • Windows 8 as a client as a client platform
  • Windows 8 RT (Surface) as a client platform
  • Windows 8 Enterprise as a client for DirectAccess
  • Support for IE10 as a client using both the Modern UI version and the desktop version
  • Support for Windows Mail (on Windows 8) as a client for Exchange Mail (“Outlook Anywhere” or RPC-Over-HTTP)
  • Support for RDC 8, the new protocol for Remote Desktop Connections, which is part of Windows 8. This also enables older clients which installed Update KB2592687 to connect to RDG-based applications published by UAG.
  • Support for Windows Phone 8 as a client platform (*this support level is comparable to other mobile platforms support)
  • Support for Office 2013 clients as client platforms for access to SharePoint (Word, Excel, PowerPoint)
  • Support for Outlook 2013 as a client for Exchange Mail (Outlook Anywhere or RPC-Over-HTTP)
  • Support for publishing Exchange 2013 for OWA, ActiveSync and Outlook-Anywhere
  • Support for publishing SharePoint 2013
  • Improvements to KCD that allows the administrator to enable ticket caching for improved performance
  • Improvements to the Relaying-party configuration mechanism (FedUtil) to improve stabilityService Pack 3 for Forefront UAG 2010 can be download here: http://www.microsoft.com/en-us/download/details.aspx?id=36788 This service pack will update UAG to build 4.0.3123.10000.Please note that installing SP3 is not cumulative, so it requires that UAG is running SP2 first. If you’re building a new server, you’ll need to get it to UAG SP2 before installing this Service Pack. If you’ve been running UAG SP2 with any private fixes, be sure to UNINSTALL them before installing SP3.For a complete overview of all Forefront UAG 2010 versions are available here at the Microsoft ISA/TMG/UAG Wiki site.

    In addition to the above, the Service Pack includes fixes for several bugs:

    • Some SharePoint application settings are lost after an application is published in Forefront Unified Access Gateway (UAG) 2010 Service Pack 2
    • HTTP error 500 received when an application that is published to a nonstandard HTTPS port is accessed the first time in Forefront Unified Access Gateway 2010 Service Pack 2
    • Service pack installation for Forefront Unified Access Gateway 2010 is unsuccessful when you log on by using a username that contains Unicode characters
    • Client requests may periodically stop being served as the number of client connections increase in Forefront Unified Access Gateway (UAG) 2010 Service Pack 2
    • Editing the WhlFiltSSO.ini and Sso.inc sample files to enable users to access additional UAG sites without having to reauthenticate does not work in Forefront Unified Access Gateway (UAG) 2010
    • Many Event ID 108 messages are logged in the Application event log after Forefront Unified Access Gateway (UAG) 2010 Service Pack 2 is applied: “Invalid DN Syntax”
    • Autodiscover requests are unsuccessful and you receive a 500 Internal Server error in Forefront Unified Access Gateway (UAG) 2010 Service Pack 2
    • The memory consumption of the Forefront UAG User Manager Service (Usermgrcom.exe) instance continually increases in Forefront Unified Access Gateway (UAG) 2010
    • Installation of a service pack for Forefront Unified Access Gateway (UAG) 2010 fails because of a time out being exceeded
    • High CPU usage and increasing memory consumption in the w3wp.exe process occurs in Forefront Unified Access Gateway 2010
    • Some published web applications see reduced network throughput between the client and published web servers when published through Forefront Unified Access Gateway 2010
    • HTTP cookie headers are not forwarded to the published server in Forefront Unified Access Gateway 2010 when the total cookie header size in the client request exceeds 5,120 bytes
    • A preauthenticated user may be permitted access to additional sites even if the user session has exceeded the defined portal trunk session time-out period in Forefront Unified Access Gateway 2010
    • You receive a .NET Framework error or a 500 error when you access an application that was published by using Forefront Unified Access Gateway 2010 Service Pack 2

    Sources:

    http://blogs.technet.com/b/ben/archive/2013/02/20/uag-sp3-is-now-available.aspx

    http://www.microsoft.com/en-us/download/details.aspx?id=36788

    http://technet.microsoft.com/en-us/library/jj906332.aspx

    http://social.technet.microsoft.com/wiki/contents/articles/6458.microsoft-isatmguag-version-history-en-us.aspx

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s