Implementing DirectAccess with Windows Server 2016 Pre-Order

Update: My new DirectAccess book is now available for purchase. Details here.

I am pleased to announce that my new book, Implementing DirectAccess with Windows Server 2016 from Apress Media, is now available for pre-order on!

Implementing DirectAccess with Windows Server 2016

This book contains detailed and prescriptive guidance for the planning, design, implementation, and support of a DirectAccess remote access solution on Windows Server 2016. It also includes valuable insight, tips, tricks, and best practice recommendations gained from my many years of deploying DirectAccess for some of the largest organizations in the world.

Current DirectAccess administrators will also find this book helpful, as the majority of content is still applicable to DirectAccess in Windows Server 2012 and Windows Server 2012 R2. In addition, the book also includes essential information on the design and deployment of highly available and geographically redundant DirectAccess deployments.

Troubleshooting DirectAccess can be a daunting task, so I’ve dedicated an entire chapter in the book to this topic. For those responsible for the maintenance and support of DirectAccess in their organization, this chapter alone will be worth the investment.

Be sure to reserve your copy today!

Leave a comment


  1. Bry

     /  August 1, 2016

    Hi Richard,

    Looking forward to reading it. I think the chapters on HA and troubleshooting will be very useful.

    Are there any fundamental changes to DirectAccess in Server 2016? Any new features or options that would warrant a change from Server 2012 R2 to Server 2016?

    • I’ve already had more than a few folks express interest in the book solely for the troubleshooting chapter. 😉 There are no new features or functionality included in DirectAccess with Windows Server 2016, so the majority of the content in the book will still be applicable to Windows Server 2012 R2. At some point you’d want to upgrade from Windows Server 2012 R2 to Windows Server 2016 for security and performance reasons, but there’s no need to delay a planned implementation or to upgrade an existing one as soon as it is released.


Leave a Reply

Discover more from Richard M. Hicks Consulting, Inc.

Subscribe now to keep reading and get access to the full archive.

Continue reading