Skip to main content

Plan for DirectAccess

  • Chapter
  • First Online:
Implementing DirectAccess with Windows Server 2016
  • 790 Accesses

Abstract

Planning is by far the most important aspect of a DirectAccess deployment project. DirectAccess can be deployed in many different configurations to meet a variety of implementation requirements. Many design decisions and deployment options have implications for security, scalability, performance, client support, and general supportability. There are scenarios in which features are mutually exclusive. Some implementation models may limit future deployment flexibility or prevent additional security features from being enabled. A clear understanding of the implementation goals will help the architect design a solution that is reliable, secure, flexible, and supportable.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 59.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 79.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    The Web Application Proxy (WAP) is only supported on the DirectAccess server in single-server deployments. Additional information can be found here: https://technet.microsoft.com/en-us/library/dn451298.aspx

  2. 2.

    Azure Active Directory (AAD) is not supported for use with DirectAccess.

  3. 3.

    https://technet.microsoft.com/en-us/library/ee382257(v=ws.10).aspx

  4. 4.

    Disabling IPv6 via the registry will prevent DirectAccess from working. More information about enabling and disabling IPv6 in Windows can be found here: https://support.microsoft.com/en-us/kb/929852

  5. 5.

    https://tools.ietf.org/html/rfc1918

  6. 6.

    https://technet.microsoft.com/en-us/library/dn464274.aspx#bkmk_frs

  7. 7.

    https://technet.microsoft.com/en-us/library/dn464274.aspx#bkmk_frs

  8. 8.

    https://technet.microsoft.com/en-us/library/dn464274.aspx#bkmk_rodc

  9. 9.

    https://directaccess.richardhicks.com/2016/03/28/directaccess-and-multi-san-ssl-certificates-for-ip-https/

  10. 10.

    More information about NLS considerations for large enterprises read http://directaccess.richardhicks.com/2015/04/06/directaccess-nls-deployment-considerations-for-large-enterprises/.

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2016 Richard M. Hicks

About this chapter

Cite this chapter

Hicks, R.M. (2016). Plan for DirectAccess. In: Implementing DirectAccess with Windows Server 2016. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-2059-7_2

Download citation

Publish with us

Policies and ethics