Deploy Remote Access in an Enterprise

Article
08/31/2016

Applies To: Windows Server 2012 R2, Windows Server 2012

This topic provides an introduction to the DirectAccess scenario for the Enterprise.

For information about alternate deployment paths, see DirectAccess Deployment Paths in Windows Server.

Important

To deploy DirectAccess using this guide, you must use a DirectAccess server that is running Windows Server® 2012 R2 or Windows Server® 2012.

Before you begin deploying, see the list of unsupported configurations, known issues, and prerequisites

Scenario description

Remote access includes a number of enterprise features, including deploying multiple Remote Access servers in a cluster load balanced with Windows Network Load Balancing (NLB) or an external load balancer, setting up a multisite deployment with Remote Access servers situated in dispersed geographical locations, and deploying DirectAccess with two-factor client authentication using a one-time password (OTP).

In this scenario

Each enterprise scenario is described in a document that includes planning and deployment instructions. For more information, see:

Practical applications

Remote access enterprise scenarios provide the following:

Increased availability—Deploying multiple Remote Access servers in a cluster provides scalability and increases the capacity for throughput and number of users. Load balancing the cluster provides high availability. If a server in the cluster fails, remote users can continue to access the internal corporate network via a different server in the cluster. Failover is transparent as clients connect to the cluster using a virtual IP (VIP) address.
Ease-of-management—A cluster or multisite deployment can be configured and managed as a single entity using the Remote Access Management console running on one of the cluster servers. In addition, a multisite deployment allows administrators to align Remote Access deployment to Active Directory sites, providing a simplified architecture. Shared settings can easily be set across cluster servers or on all multisite entry point servers. Remote Access settings can be managed from any of the servers in the cluster or deployment, or remotely using Remote Server Administration Tools (RSAT). In addition, the entire cluster or multisite deployment can be monitored from a single Remote Access Management console.
Cost efficiency—A Remote Access multisite deployment allows enterprises to deploy Remote Access servers in multiple sites corresponding to client locations. This provides a predictable access experience for remote clients regardless of location, and reduces costs and intranet bandwidth by routing client traffic over the Internet to the closest Remote Access server.
Security—Deploying strong client authentication with a one-time password (OTP) instead of standard Active Directory password increases security.

Roles and features included in this scenario

The following table lists the roles and features used in the enterprise scenario.

Role/feature	How it supports this scenario
Remote Access server role	The role is installed and uninstalled using the Server Manager console. This role encompasses both DirectAccess, which was previously a feature in Windows Server 2008 R2, and Routing and Remote Access Services which was previously a role service under the Network Policy and Access Services (NPAS) server role. The Remote Access role consists of two components: DirectAccess and Routing and Remote Access Services (RRAS) VPN—DirectAccess and VPN are managed together in the Remote Access Management console. RRAS Routing—RRAS routing features are managed in the legacy Routing and Remote Access console. The Remote Access Server Role is dependent on the following server features: Internet Information Services (IIS) – This feature is required to configure the network location server and default web probe. Group Policy Management Console feature – feature is required by DirectAccess to create and manage the Group Policy Objects (GPOs) in Active Directory and must be installed as a required feature for the server role.
Remote Access Management Tools feature	This feature is installed as follows: It is installed by default on a Remote Access server when the Remote Access role is installed, and supports the Remote Management console user interface. It can be optionally installed on a server not running the Remote Access server role. In this case it is used for remote management of a Remote Access computer running DirectAccess and VPN. The Remote Access Management Tools feature consists of the following: Remote Access GUI and Command Line Tools Remote Access module for Windows PowerShell Dependencies include: Group Policy Management Console RAS Connection Manager Administration Kit (CMAK) Windows PowerShell 3.0 Graphical Management Tools and Infrastructure
Windows NLB	This feature allows the load balancing of multiple Remote Access servers.

Remote Access server role

The role is installed and uninstalled using the Server Manager console. This role encompasses both DirectAccess, which was previously a feature in Windows Server 2008 R2, and Routing and Remote Access Services which was previously a role service under the Network Policy and Access Services (NPAS) server role. The Remote Access role consists of two components:

DirectAccess and Routing and Remote Access Services (RRAS) VPN—DirectAccess and VPN are managed together in the Remote Access Management console.
RRAS Routing—RRAS routing features are managed in the legacy Routing and Remote Access console.

The Remote Access Server Role is dependent on the following server features:

Internet Information Services (IIS) – This feature is required to configure the network location server and default web probe.
Group Policy Management Console feature – feature is required by DirectAccess to create and manage the Group Policy Objects (GPOs) in Active Directory and must be installed as a required feature for the server role.

Remote Access Management Tools feature

This feature is installed as follows:

It is installed by default on a Remote Access server when the Remote Access role is installed, and supports the Remote Management console user interface.
It can be optionally installed on a server not running the Remote Access server role. In this case it is used for remote management of a Remote Access computer running DirectAccess and VPN.

The Remote Access Management Tools feature consists of the following:

Remote Access GUI and Command Line Tools
Remote Access module for Windows PowerShell

Dependencies include:

Group Policy Management Console
RAS Connection Manager Administration Kit (CMAK)
Windows PowerShell 3.0
Graphical Management Tools and Infrastructure

Windows NLB

This feature allows the load balancing of multiple Remote Access servers.

Content type	References
Remote Access on TechNet	Remote Access TechCenter
Product evaluation	Demonstrate DirectAccess in a cluster with NLB Demonstrate a DirectAccess multisite deployment Demonstrate a DirectAccess multisite deployment
Deployment	Deploy a Single DirectAccess Server Using the Getting Started Wizard Deploy a Single DirectAccess Server with Advanced Settings
Tools and settings	Remote Access PowerShell cmdlets
Community resources	RRAS Product Team blog \| Remote Access TechNet Forum DirectAccess Wiki entries
Related technologies	How IPv6 works

Share via