Export (0) Print
Expand All

Manage Remote Access

Published: August 10, 2012

Updated: August 10, 2012

Applies To: Windows Server 2012, Windows Server 2012 R2



The DirectAccess Remote Client Management deployment scenario uses DirectAccess to maintain clients over the Internet. This section explains the scenario, including its phases, roles, features, and links to additional resources.

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

noteNote
In addition to this topic, the following Remote Access management topics are available.

DirectAccess client computers are connected to the intranet whenever they are connected to the Internet, regardless of whether the user has signed in to the computer. They can be managed as intranet resources and kept current with Group Policy changes, operating system updates, antimalware updates, and other organizational changes.

In some cases, intranet servers or computers must initiate connections to DirectAccess clients. For example, Help Dtechnicians can use remote desktop connections to connect to and troubleshoot remote DirectAccess clients. This scenario lets you keep your existing remote access solution in place for user connectivity, while using DirectAccess for remote management.

DirectAccess in Windows Server 2012 provides a configuration that supports remote management of DirectAccess clients. You can use a deployment wizard option that limits the creation of policies to only those needed for remote management of client computers.

noteNote
In this deployment, user-level configuration options such as force tunneling, Network Access Protection (NAP) integration, and two-factor authentication are not available.

The DirectAccess Remote Client Management deployment scenario includes the following steps for planning and configuring.

There are only a few computer and network requirements for planning this scenario. They include:

  • Network and server topology: With DirectAccess, you can place your Remote Access server at the edge of your intranet or behind a network address translation (NAT) device or a firewall.

  • DirectAccess network location server: The network location server is used by DirectAccess clients to determine whether they are located on the internal network. The network location server can be installed on the DirectAccess server or on another server.

  • DirectAccess clients: Decide which managed computers will be configured as DirectAccess clients.

Configuring your deployment consists of a number of steps. These include:

  1. Configure the infrastructure: Configure DNS settings, join the server and client computers to a domain if required, and configure Active Directory security groups.

    In this deployment scenario, Group Policy Objects (GPOs) are created automatically by Remote Access. For advanced certificate GPO options, see Deploy a Single DirectAccess Server with Advanced Settings.

  2. Configure Remote Access server and network settings: Configure network adapters, IP addresses, and routing.

  3. Configure certificate settings: In this deployment scenario, the Getting Started Wizard creates self-signed certificates, so there is no need to configure the more advanced certificate infrastructure that is explained in the topic Deploy a Single DirectAccess Server with Advanced Settings.

  4. Configure the network location server: In this scenario, the network location server is installed on the Remote Access server.

  5. Plan DirectAccess management servers: Administrators can remotely manage DirectAccess client computers that are located outside the corporate network by using the Internet. Management servers include computers that are used during remote client management (such as update servers).

  6. Configure the Remote Access server: Install the Remote Access role and run the DirectAccess Getting Started Wizard to configure DirectAccess.

  7. Verify the deployment: Test a client to make sure it is able to connect to the internal network and the Internet by using DirectAccess.

Deploying a single Remote Access server for managing DirectAccess clients provides the following:

  • Ease-of-access: Managed client computers running Windows 8 or Windows 7 can be configured as DirectAccess client computers. These clients can access internal network resources through DirectAccess any time they are connected to the Internet without needing to sign in to a VPN connection. Client computers not running one of these operating systems can connect to the internal network through VPN. DirectAccess and VPN are managed in the same console and with the same set of wizards.

  • Ease-of-management: DirectAccess client computers that are connected to the Internet can be remotely managed by remote access administrators by using 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. One or more Remote Access servers can be managed from a single Remote Access Management console.

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

 

Role or feature How it supports this scenario

Remote Access role

This role is installed and uninstalled by using the Server Manager console or Windows PowerShell. This role encompasses 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 in the Remote Access Management console.

  2. RRAS: Features are managed in the Routing and Remote Access console.

The Remote Access server role is dependent on the following features:

  • Web Server (IIS): Required to configure the network location server and 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:

  • By default on a Remote Access server when the Remote Access role is installed and supports the Remote Management console user interface.

  • As an option on a server that is not running the Remote Access server role. In this case, it is used for remote management of a Remote Access server.

This 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

Hardware requirements for this scenario include the following:

  • A computer that meets the hardware requirements for Windows Server 2012. For more information, see Installing Windows Server 2012.

  • The server must have at least one network adapter installed and enabled. There should be only one adapter connected to the corporate internal network, and only one connected to the external network (Internet).

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

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

  • A certification authority is required on the server 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.

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

  • 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. These servers provide services that include Windows and antivirus updates and Network Access Protection (NAP) client compliance. You should deploy the required servers before you begin the Remote Access deployment.

  • A DNS server running Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, or Windows Server 2008 with SP2 is required.

Software requirements for this scenario include the following:

  • 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.

  • Admins who deploy a Remote Access server require local administrator permissions on the server and domain user permissions. In addition, the administrator requires permissions for the GPOs that are used for DirectAccess deployment. To take advantage of the features that restrict DirectAccess deployment to only mobile computers, Domain Admin permissions are required on the domain controller to create a WMI filter.

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

  • DirectAccess clients must be domain members. Domains that contain clients can belong to the same forest as the Remote Access server, or they can 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. Computers should not be included in more than one security group that includes DirectAccess clients. If clients are included in multiple groups, name resolution for client requests will not work as expected.

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

Community Additions

ADD
Show:
© 2014 Microsoft