We are happy to announce that Rollup 1 for Forefront UAG 2010 Service Pack 3 has been released.
UAG 2010 Service Pack 3 Rollup 1 is available as a hotfix download from Microsoft Support as an update to UAG 2010 Service Pack 3.
This important update contains 8 new fixes for reported issues as well as enhanced context tracing to more easily filter trace data per session.
For details, please visit KB 2827350: Description of Rollup 1 for Forefront Unified Access Gateway 2010 Service Pack 3
Please download the Forefront Unified Access Gateway (UAG) 2010 Service Pack 3 package now, and learn more about UAG 2010 SP3 by visiting our TechNet Library.
J.C. Hornbeck | Knowledge Engineer | Microsoft GBS Management and Security Division
Get the latest System Center news on Facebook and Twitter:
System Center All Up: http://blogs.technet.com/b/systemcenter/ System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/ System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/ System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/ System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm
Windows Intune: http://blogs.technet.com/b/windowsintune/ WSUS Support Team blog: http://blogs.technet.com/sus/ The AD RMS blog: http://blogs.technet.com/b/rmssupp/
The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
Prior to installing SP3, we could access a Portal with the Public Host Name. After we installed SP3 and subsequently rollup1 the only way to access the Portal is to include the "Path" of the Portal with the Public Host Name. If you log out of the Portal and use the web page displayed to log back into the Portal it will not work because the URL does not include the "Path" for the Portal. Is there a configuration that changed that can be modified to change the behavior so the Portal can be accessed without the path? Or is this a bug?
WHY IS THIS PRODUCT SO COMPLICATED TO CONFIGURE? Why can't you use normal terminology that makes sense? What is the purpose of all the lingo and cryptic documentation? Don't you want people to use your product? Are you purposely trying to make it difficult to use?