Export (0) Print
Expand All
1 out of 3 rated this helpful - Rate this topic

Deploy a Single Remote Access Server with Advanced Settings

Published: February 29, 2012

Updated: February 19, 2014

Applies To: Windows Server 2012, Windows Server 2012 R2



Note: Windows Server 2012 combines DirectAccess and Routing and Remote Access Service (RRAS) into a single Remote Access role.

This topic provides an introduction for setting up a single Remote Access server with basic and advanced features.

Advanced Remote Access Deployment Map

In this scenario, a single computer running Windows Server 2012 or Windows Server 2012 R2 is configured as a Remote Access server with advanced settings.

  • If you want to configure a basic deployment with simple settings only, see Deploy a Single Remote Access Server using the Getting Started Wizard. In the simple scenario, Remote Access is set up with default settings by using a wizard, without any need to configure infrastructure settings such as a certification authority (CA) or Active Directory security groups.

  • If you want to configure Remote Access with enterprise features such as a load-balanced cluster, multisite deployment, or two-factor client authentication, complete the scenario described in this topic to set up a single server, and then set up the required enterprise scenario as described in Deploy Remote Access in an Enterprise.

To set up a single Remote Access server with advanced settings, a number of planning and deployment steps are required.

Before you begin this deployment scenario, review the following list for important requirements:

  1. Windows firewall must be enabled on all profiles.

  2. ISATAP in the corporate network is not supported. If you are using ISATAP, you should remove it and use native IPv6.

  3. Automatically deploys DirectAccess to all mobile computers in the current domain.

  4. The DirectAccess server is the network location server.

  5. Network Access Protection (NAP) is not supported.

  6. Changing policies outside of the DirectAccess management console or by using Windows PowerShell cmdlets is not supported.

Planning is divided into two phases:

  1. Planning for the Remote Access infrastructure—This phase describes the planning required to set up the network infrastructure before beginning the Remote Access deployment. It includes planning the network and server topology, certificate planning, DNS, Active Directory and Group Policy object (GPO) configuration, and the DirectAccess network location server.

  2. Planning for the Remote Access deployment—This phase describes the planning steps required to prepare for the Remote Access deployment. It includes planning for Remote Access client computers, server and client authentication requirements, VPN settings, infrastructure servers, and management and application servers.

For detailed planning steps, see Plan an Advanced Remote Access Deployment.

Deployment is divided into three phases:

  1. Configuring the Remote Access infrastructure—This phase includes configuring network and routing, configuring firewall settings if required, configuring certificates, DNS servers, Active Directory and GPO settings, and the DirectAccess network location server.

  2. Configuring Remote Access server settings—This phase includes steps for configuring Remote Access client computers, the Remote Access server, infrastructure servers, management and application servers.

  3. Verifying the deployment—This phase includes steps to verify that the deployment is working as required.

For detailed deployment steps, see Install and Configure Advanced Remote Access.

Deploying a single Remote Access server provides the following:

  • Ease-of-access—Managed client computers running Windows 8 and Windows 7 can be configured as DirectAccess client computers. These clients can access internal network resources via DirectAccess any time they are located on the Internet without needing to log in to a VPN connection. Client computers not running one of these operating systems can connect to the internal network via VPN.

  • Ease-of-management—DirectAccess client computers located on the Internet can be remotely managed by Remote Access administrators over DirectAccess, even when the client computers are not located in the internal corporate network. Client computers that do not meet corporate requirements can be remediated automatically by management servers. Both DirectAccess and VPN are managed in the same console and with the same set of wizards. Additionally, one or more Remote Access servers can be managed from a single Remote Access Management console

The following table lists the roles and features that are required for this scenario:

 

Role/feature How it supports this scenario

Remote Access role

The role is installed and uninstalled using the Server Manager console or Windows PowerShell. 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:

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

  2. 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 roles/features:

  • Internet Information Services (IIS) Web Server – This feature is required to configure the network location server on the Remote Access server, and the default web probe.

  • Windows Internal Database—Used for local accounting on the Remote Access server.

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 and Windows PowerShell cmdlets.

  • 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

  • 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

Hardware requirements for this scenario include the following:

  • Server requirements:

    • A computer that meets the hardware requirements for Windows Server 2012.

    • The server must have at least one network adapter installed, enabled, and connected to the internal network. When two adapters are used, there should be one adapter connected to the internal corporate network, and one connected to the external network (Internet, or private network).

    • If Teredo is required as an IPv4 to IPv6 transition protocol, the external adapter of the server requires two consecutive public IPv4 addresses. If a single IP address is available, then only IP-HTTPS can be used as the transition protocol.

    • At least one domain controller. The Remote Access server and DirectAccess clients must be domain members.

    • A certification authority (CA) is required if you do not want to use self-signed certificates for IP-HTTPS or the network location server, or if you want to use client certificates for client IPsec authentication. Alternatively, you can request certificates from a public CA.

    • If the network location server is not located on the Remote Access server, a separate web server is required to run it.

  • Client requirements:

    • A client computer must be running Windows 8 or Windows 7.

      noteNote
      Only the following operating systems can be used as DirectAccess clients: Windows Server 2012, Windows Server 2008 R2, Windows 8 Enterprise, Windows 7 Enterprise, and Windows 7 Ultimate.

  • Infrastructure and management server requirements:

    • During remote management of DirectAccess client computers, clients initiate communications with management servers such as domain controllers, System Center Configuration Servers, and Health Registration Authority (HRA) servers for services that include Windows and antivirus updates and Network Access Protection (NAP) client compliance. The required servers should be deployed before beginning the Remote Access deployment.

    • If Remote Access requires client NAP compliance, NPS and HRS servers should be deployed before beginning remote access deployment

    • If VPN is enabled, a DHCP server is required to allocate IP addresses automatically to VPN clients, if a static address pool is not used.

There are a number of requirements for this scenario:

  • Server requirements:

    • The Remote Access server must be a domain member. The server can be deployed at the edge of the internal network, or behind an edge firewall or other device.

    • If the Remote Access server is located behind an edge firewall or NAT device, the device must be configured to allow traffic to and from the Remote Access server.

    • The person deploying remote access on the server requires local administrator permissions on the server, and domain user permissions. In addition, the administrator requires permissions for the GPOs used in DirectAccess deployment. To take advantage of the features that restricts DirectAccess deployment to mobile computers only, permissions to create a WMI filter on the domain controller are required.

  • Remote Access client requirements:

    • DirectAccess clients must be domain members. Domains containing clients can belong to the same forest as the Remote Access server, or have a two-way trust with the Remote Access server forest or domain.

    • An Active Directory security group is required to contain the computers that will be configured as DirectAccess clients. If a security group is not specified when configuring DirectAccess client settings, by default the client GPO is applied on all laptop computers in the Domain Computers security group. Only the following operating systems can be used as DirectAccess clients: Windows Server 2012, Windows Server 2008 R2, Windows 8 Enterprise, Windows 7 Enterprise, and Windows 7 Ultimate.

      noteNote
      It is recommended that you create a security group for each domain containing computers that will be configured as DirectAccess clients.

      ImportantImportant
      If you have enabled Teredo in your DirectAccess deployment, and you want to provide access to Windows 7 clients, make sure that the clients are upgraded to Windows 7 with SP1. Clients using Windows 7 RTM will not be able to connect over Teredo. However, these clients will still be able to connect to the corporate network over IP-HTTPS.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.