With the recent release of Service Pack 3 (SP3) for Microsoft Forefront Unified Access Gateway (UAG) 2010, Microsoft has published a list of features in UAG SP3 that have been deprecated. To be clear, this does not mean these features cease to function after you install SP3 on UAG! It is simply meant to give network engineers and security administrators an idea about what features are likely to be removed from future releases of Forefront UAG. Some of the deprecated features should come as no surprise. For example, DirectAccess support in Forefront UAG is now deprecated in favor of DirectAccess in Windows Server 2012. Also, features such as Secure Sockets Tunneling Protocol (SSTP) for client-based remote access are better handled using the remote access role in Windows Server 2012. Other deprecated features may present more of a challenge if you’ve been relying on them to provide secure remote access to applications, such as the deprecation of support for some authentication repositories (e.g. Novell Directory, Notes Directory, TACACS) or the Java-based Session Cleanup tool. For a complete list of deprecated features in Forefront UAG SP3, click here.
Microsoft MVP
Consulting
Pluralsight
Newsletter
All posts tagged Important Links
Features Deprecated in Forefront UAG Service Pack 3
Posted by Richard M. Hicks on February 26, 2013
https://directaccess.richardhicks.com/2013/02/26/features-deprecated-in-forefront-uag-service-pack-3/
Installing Windows 8 Enterprise on the Microsoft Surface Pro for DirectAccess
Recently I wrote about the fact that the Microsoft Surface Pro is not supported as a DirectAccess client, because it ships with Windows 8 Professional pre-installed. Only Windows 8 Enterprise (and Windows 7 Enterprise and Ultimate) are supported for DirectAccess. However, that doesn’t mean that the Surface Pro will never support DirectAccess. I simply meant to state that the Surface Pro didn’t support DirectAccess out-of-the-box. That said, using your Surface Pro with DirectAccess will require installing Windows 8 Enterprise edition. Thankfully my good friend Kurt Shintaku documented in detail the steps required to accomplish this. Once you’ve completed these steps you should be able to join your Surface Pro to a domain and enable it as a DirectAccess client just like any other Windows 8 Enterprise device. Have fun!
Update: Read my post on how to install Windows 8 Enterprise and configure DirectAccess on the Microsoft Surface Pro here.
Posted by Richard M. Hicks on February 25, 2013
https://directaccess.richardhicks.com/2013/02/25/installing-windows-8-enterprise-on-the-microsoft-surface-pro-for-directaccess/
Hotfix for Windows 7 DirectAccess Clients
This month Microsoft released an important hotfix to address a DirectAccess connectivity issue for Windows 7 clients connecting to a Windows Server 2012 DirectAccess Server. The hotfix specifically resolves an issue where Windows 7 clients face a very long delay reestablishing a DirectAccess session using the IP-HTTPS IPv6 transition protocol after recently disconnecting from a VPN session. In this scenario, Windows 7 DirectAccess clients may take as long as 15 minutes to automatically reestablish a DirectAccess session using IP-HTTPS. During this time the IP-HTTPS adapter state is displayed as disconnected. Refer to Microsoft KB 2796313 more information and to download the hotfix.
Posted by Richard M. Hicks on February 17, 2013
https://directaccess.richardhicks.com/2013/02/17/hotfix-for-windows-7-directaccess-clients/
Always On VPN Book
DirectAccess Book
