Partager via


Checklist: Implementing a Redundant DirectAccess Design

Updated: October 7, 2009

Applies To: Windows Server 2008 R2

Important

This topic describes deployment of DirectAccess in Windows Server 2008 R2. For deployment of DirectAccess in Microsoft Forefront Unified Access Gateway (UAG), see the Forefront UAG DirectAccess Deployment Guide (https://go.microsoft.com/fwlink/?LinkId=179989).

This checklist includes cross-reference links to important concepts about deploying a redundant design DirectAccess with Hyper-V. It also contains links to procedures and other checklists that will help you complete the tasks that are required to implement this design.

Note

Complete the tasks in this checklist in order. When a reference link takes you to a conceptual topic, a procedure, or to another checklist, return to this topic so that you can proceed with the remaining tasks in this checklist.

Checklist: Implementing a redundant DirectAccess design

  Task Reference

Review important concepts for using Hyper-V to provide redundancy for DirectAccess.

Planning Redundancy for a DirectAccess Server

As needed by your design plan, configure DirectAccess for the full intranet, selected server, or end-to-end access model.

Checklist: Implementing a DirectAccess Design for Full Intranet Access

Checklist: Implementing a DirectAccess Design for Selected Server Access

Checklist: Implementing a DirectAccess Design for End-to-End Access

Configure two Hyper-V hosts with failover clustering supporting a single shared DirectAccess server in a virtual machine and modify the Hyper-V configuration for DirectAccess.

Planning Redundancy for a DirectAccess Server