The Infrastructure Planning and Design (IPD) Guide for DirectAccess is now publically available. In a previous blog post, I reported on the beta version.

This new IPD guide provides actionable guidance for designing a DirectAccess infrastructure using Windows Server 2008 R2. The guide’s easy-to-follow, four-step process gives a straightforward explanation of the infrastructure required for DirectAccess clients to be connected from the Internet to resources on the corporate network, whether or not the organization has begun deploying IPv6. 

The guide covers four key steps in the design process for DirectAccess:

1. Aligning the project scope with the business requirements.
2. Determining whether IPv6, Teredo, 6to4, and IP-HTTPS connectivity will be supported for Internet-based clients.
3. Assessing the need for IPv6/IPv4 translators and IPv6/IPv4 DNS gateways and ISATAP for internal communication.
4. Determining the number and placement of servers, the certificate services requirements, and location of certificate revocation list (CRL) distribution points.