DirectAccess in Windows Server 2016 at Microsoft Ignite 2016

I’m pleased to announce that I will be delivering a community theater session at this year’s Microsoft ignite conference in Atlanta, GA. The session, THR2136 in the session catalog, is scheduled for Thursday, September 29 at 12:40PM. This is a level 200 talk where I’ll be providing a high-level overview of all remote access technologies in Windows Server 2016, including DirectAccess, client-based VPN, and Web Application Proxy (WAP). I’ll be focusing on what’s new in each of these technologies and demonstrating how each solution applies in different use cases.

DirectAccess in Windows Server 2016 at Microsoft Ignite 2016

In addition to the session, I’ll be spending time with the folks from PointSharp and Pluralsight in their respective booths too, answering questions and providing demonstrations. I hope to have copies of my new DirectAccess book to sign as well. Be sure to follow me on Twitter for up-do-date details. Hope to see you at the conference!

Leave a comment


  1. Hi Sir Richard Hicks that’s AWESOME!!! God bless and more power Sir i hope you would also plan to visit Angeles, Philippines so I could attend your sessions…somehow Im a dying hard fan of yours Direct Access WOW!!!

  2. Martin mayrhofer

     /  September 1, 2016

    Cool – see you there – greetings from Austria

  3. Hi Richard,

    At your theater session, you mentioned that Server 2016 VPN with Windows 10 can provide an experience similar to Direct Access, but without the complexity. You explained that in Windows 10, the VPN can be configured to be always-on, auto-triggered and/or per-application.

    Can you provide a link to more information about the “always-on” option? Direct Access has been a struggle for my organization, especially when it comes to manage-out functionality. We are looking for something simpler and what you explained sounded much more attractive.

    Thank you,

    Matt Gustke

    • Windows 10 VPN can be configured to provide a “DirectAccess-like’ experience, yes. It have reduced infrastructure requirements over DirectAccess, but it does bring with it its own unique set of complexities. First, auto-trigger and always-on VPN in Windows 10 must be configured using a Mobile Device Management (MDM) platform. It cannot be managed using AD and group policy as DirectAccess supports. This means an investment in Microsoft InTune (or third-party equivalent). You can find all the details about Windows 10 VPN here.

      With regard to DirectAccess, I’ve helped many customers implement the technology successfully, including seamless outbound management. I have a custom solution that enables manage out for DirectAccess clients even in scenarios where load balancing and/or multisite are configured, all without requiring any IPv6 on the internal network.

      Perhaps I can help you iron out your current DirectAccess issues? Let me know if you’d like to explore that further. I’d be happy to jump on a call with you sometime and go over your requirements in more detail.



Leave a Reply

%d bloggers like this: