Ben Ari's UAG and IAG Blog

Plenty of useful and fun info on UAG, Microsoft's remote access and reverse-proxy product.

UAG SP3 is now available!

UAG SP3 is now available!

  • Comments 17
  • Likes

This morning, Feb 20th 2013, Service Pack 3 for UAG has been released, and is available to 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. It’s release notes are at http://support.microsoft.com/kb/2744025. The changes and news in this release are:

  1. Windows 8 as a client as a client platform
  2. Windows 8 RT (Surface) as a client platform
  3. Windows 8 Enterprise as a client for DirectAccess
  4. Support for IE10 as a client using both the Modern UI version and the desktop version on both Windows 7 and Windows 8
  5. Support for Windows Mail (on Windows 8) as a client for Exchange Mail (“Outlook Anywhere” or RPC-Over-HTTP)
  6. 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.
  7. Support for Windows Phone 8 as a client platform (*this support level is comparable to other mobile platforms support)
  8. Support for Office 2013 clients as client platforms for access to SharePoint (Word, Excel, PowerPoint)
  9. Support for Outlook 2013 as a client for Exchange Mail (Outlook Anywhere or RPC-Over-HTTP)
  10. Support for publishing Exchange 2013 for OWA, ActiveSync and Outlook-Anywhere
  11. Support for publishing SharePoint 2013
  12. Improvements to KCD that allows the administrator to enable ticket caching for improved performance
  13. Improvements to the Relaying-party configuration mechanism (FedUtil) to improve stability

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

  1. Some SharePoint application settings are lost after an application is published in Forefront Unified Access Gateway (UAG) 2010 Service Pack 2
  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
  3. Service pack installation for Forefront Unified Access Gateway 2010 is unsuccessful when you log on by using a username that contains Unicode characters
  4. Client requests may periodically stop being served as the number of client connections increase in Forefront Unified Access Gateway (UAG) 2010 Service Pack 2
  5. 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
  6. 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"
  7. Autodiscover requests are unsuccessful and you receive a 500 Internal Server error in Forefront Unified Access Gateway (UAG) 2010 Service Pack 2
  8. The memory consumption of the Forefront UAG User Manager Service (Usermgrcom.exe) instance continually increases in Forefront Unified Access Gateway (UAG) 2010
  9. Installation of a service pack for Forefront Unified Access Gateway (UAG) 2010 fails because of a time out being exceeded
  10. High CPU usage and increasing memory consumption in the w3wp.exe process occurs in Forefront Unified Access Gateway 2010
  11. Some published web applications see reduced network throughput between the client and published web servers when published through Forefront Unified Access Gateway 2010
  12. 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
  13. 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
  14. 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

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.

Since this release, I’ve been asked by many about support for Lync 2013. I’m afraid SP3 does *not* add support for Lync 2013 to UAG. At this time, I don’t have any news or predictions to share about this.

Congratulations to the UAG Product Group for this incredible milestone!

Comments
  • After trying to install it I had to call Microsoft. In an administrator cmd prompt, you need to run msiexec /p "C:\UAG-KB2744025-v4.0.3123.10000-ENU.msp" /L*V to get it to install.

  • The method you have specified, Jon, is for a regular installation, but with extended logging (verbose logging). Using that way wouldn't affect the outcome - just give us more info if it failed. This means that if it was successful this way, it would have been successful even doing a regular double-click install. I can only guess something random went wrong in the original attempt. You can have a look at my guide for troubleshooting installation issues (posted a week ago or so).

  • Hi Ben, have you seen any detailed info on what has changed in DirectAccess to provide Windows 8 support?

  • There were no changes to UAG's code for Win8 support for DA. To have full support, it needed to go through a certain level of testing to have it certified.

  • One of the most useful features File Access now broken and on the depreciated list.  >:(

  • Ben, that was the issue. Double click would not work but running that command did minus the logging I forgot to remove.

  • Has anyone been having issues with the Socket forwarding components on XP clients since upgrading to Sp3?

    Thanks

  • Again a post VERY useful! :-) Great Work!

  • I get Script error in FileAccess when selecting SERVERS node.

    Line = 13

    Char = 3

    "object doesn't support property or method SHOW SERVERS"

    http://localhost:6001/FileSharingAdmin/Helper.asp

    Tried this:

    ver = lowerAgent.substr(lowerAgent.indexOf("msie")+5,2)

    ... and this:

    itcalls.blogspot.co.uk/.../uag-2010-file-access-application-fails.html

    Neither worked.  Any suggestions, anyone?

  • Ian: We have identified a problem with SP3 that leads to this issue. Please contact Microsoft support to obtain a workaround.

  • Hi Ben, I too have an issue with File access post SP3, selecting file access comes up with a http 500 error.

    I've tried some suggestions I've found on modifying the default.asp;

    Changing

    ver = CInt(lowerAgent.substr(lowerAgent.indexOf("msie")+5,2))

    to

    ver = lowerAgent.substr(lowerAgent.indexOf("msie")+5,2)

    or

    ver = ParseInt(lowerAgent.substr(lowerAgent.indexOf("msie")+5,2))

    Is this the same issue as Ian's? And if so, when you say contact Microsft support, you mean to log a call with them?

    Thanks

  • Himesh: no, this is a different issue. For that, the following blog post may help (its not in English, but you can probably get a translation):

    itsäkerhetsguiden.se/.../file-access-i-uag-efter-service-pack-3

  • Hi Ben,

    Thanks for the reply.

    Simon

  • Am also having problems with Socket Forwarding with SP3 says "install disabled" in client information next to socket forwarding. is enabled as basic on the app on the UAG

  • With regard to the HTTP 500 error MS have just released an update for SP3 with various fixes :)

    support.microsoft.com/.../2827350*2_*1_*1_*1_*1_*1%2Egmp_3727281%2Egde_3727281_member_230463482

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment