Windows Server 2012 DirectAccess includes a number of enhanced features and improvements as below:
⦁ Direct Access and RRAS coexistence
⦁ Simplified Direct Access management/setup for small and medium organization administrators
⦁ Built-in NAT64 and DNS64 support for accessing IPv4-only resources
⦁ Support for Direct Access server behind a NAT device
⦁ Load balancing support
⦁ Support for multiple domains
⦁ Support for OTP (token based authentication)
⦁ Automated support for force tunneling
⦁ Multisite support
⦁ Windows PowerShell support
⦁ User and server health monitoring
I’ve now done a couple of DirectAccess implementations (both small scale and large scale) and I must say that most things works very well and straightforward.
There are however a couple of hotfixes that you may have to apply, if you for example are enabling external load balancing in your implementation.
Below is a summary of the hotfixes that have been useful in my different implementations of DirectAccess
Windows Server 2012 and Windows 8 – DirectAccess Related Hotfixes:
KB2782560: DNS64 does not resolve computer names when you use DirectAccess and external load balancing in Windows Server 2012.
KB2788525: You cannot enable external load balancing on a Windows Server 2012-based DirectAccess server.
KB2769240: You cannot connect a DirectAccess client to a corporate network in Windows 8 or Windows Server 2012.
KB2748603: The process may fail when you try to enable Network Load Balancing in DirectAccess in Window Server 2012.
Since this post was written Microsoft has published a KB article covering this subject where they list these, and some additional hotfixes. https://support.microsoft.com/en-us/kb/2883952