Identifying Your DirectAccess Deployment Goals
Updated: October 1, 2009
Applies To: Windows 7, Windows Server 2008 R2
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).
Correctly identifying your DirectAccess deployment goals is essential for the success of your DirectAccess design project. Depending on the size of your organization and the level of involvement you are expecting from the information technology (IT) staff in any partner organizations, form a project team that can clearly articulate real-world deployment issues in a vision statement. Make sure that the members of this team understand the direction in which your deployment project must move in order to reach your DirectAccess deployment goals.
When you write your vision statement, take steps to identify, clarify, and refine your deployment goals. Prioritize and, if necessary, combine your deployment goals so that you can design and deploy DirectAccess by using an iterative approach. You can take advantage of existing, documented, and predefined DirectAccess deployment goals that are relevant to the DirectAccess designs and develop a working solution for your scenarios.
The following table lists the three main tasks for articulating, refining, and documenting your DirectAccess deployment goals.
|Deployment goal tasks||Reference links|
Evaluate predefined DirectAccess deployment goals that are provided in this section of the guide and combine one or more goals to reach your organizational objectives.
Map one goal or a combination of any of the predefined DirectAccess deployment goals to a DirectAccess design.
Document your deployment goals and other important details for your DirectAccess design.