Export (0) Print
Expand All

Understanding the DirectAccess Design Process

Updated: October 1, 2009

Applies To: Windows 7, Windows Server 2008 R2

ImportantImportant
This topic describes design considerations for DirectAccess in Windows Server 2008 R2. For the design considerations of DirectAccess in Microsoft Forefront Unified Access Gateway (UAG), see the Forefront UAG DirectAccess Design Guide (http://go.microsoft.com/fwlink/?LinkId=179988).

To begin the DirectAccess design process, you must first identify your DirectAccess deployment goals. This guide contains some predefined deployment goals so that you can understand the ways in which DirectAccess can benefit your organization. After evaluating these goals, you can select a DirectAccess design that meets your DirectAccess deployment objectives. Each design includes examples to help you understand fundamental DirectAccess processes such as client access or remote management.

The following topics explain how to identify and evaluate a DirectAccess deployment design for your organization:

After you identify your deployment goals and map them to a DirectAccess design, you can begin documenting your design, based on the processes that are described in the following topics:

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft