DirectAccess, also known as Unified Remote Access, is a VPN-like technology that provides intranet connectivity to client computers when they are connected to the Internet. Unlike many traditional VPN connections, which must be initiated and terminated by explicit user action, DirectAccess connections are designed to connect automatically as soon as the computer connects to the Internet. DirectAccess was introduced in Windows Server 2008 R2, providing this service to Windows 7 and Windows 8 "Enterprise" edition clients. In 2010, Microsoft Forefront Unified Access Gateway (UAG) was released, which simplifies[1] the deployment of DirectAccess for Windows 2008 R2, and includes additional components that make it easier to integrate without the need to deploy IPv6 on the network, and with a dedicated user interface for the configuration and monitoring. Some requirements and limitations that were part of the design of DirectAccess with Windows Server 2008 R2 and UAG have been changed (see requirements below). While DirectAccess is based on Microsoft technology, third-party solutions exist for accessing internal UNIX and Linux servers through DirectAccess. With Windows Server 2012, DirectAccess is fully integrated into the operating system, providing a user interface to configure and native IPv6 and IPv4 support.[2]


DirectAccess establishes IPsec tunnels from the client to the DirectAccess server, and uses IPv6 to reach intranet resources or other DirectAccess clients. This technology encapsulates the IPv6 traffic over IPv4 to be able to reach the intranet over the Internet, which still (mostly) relies on IPv4 traffic. All traffic to the intranet is encrypted using IPsec and encapsulated in IPv4 packets, which means that in most cases, no configuration of firewalls or proxies should be required.[3] A DirectAccess client can use one of several tunneling technologies, depending on the configuration of the network the client is connected to. The client can use 6to4, Teredo tunneling, or IP-HTTPS, provided the server is configured correctly to be able to use them. For example, a client that is connected to the Internet directly will use 6to4, but if it is inside a NATed network, it will use Teredo instead. In addition, Windows Server 2012 provides two backward compatibility services DNS64 and NAT64, which allows DirectAccess clients to communicate with servers inside the corporate network even if those servers are only capable of IPv4 networking. Due to the globally routable nature of IPv6, computers on the corporate network can also initiate a connection to DirectAccess clients, which allows them to remotely manage (Manage Out) these clients at any time.[4]


DirectAccess can be deployed for multiple sites. It allows for a secure encrypted VPN. This is controlled through Group Policies which allows the administrator to maintain a secure network.


DirectAccess With Windows Server 2008 R2 or UAG requires:

  • One or more DirectAccess servers running Windows Server 2008 R2 with two network adapters: one that is connected directly to the Internet, and a second that is connected to the intranet.
  • On the DirectAccess server, at least two consecutive, public IPv4 addresses assigned to the network adapter that is connected to the Internet.
  • DirectAccess clients running Windows 7 "Ultimate" or "Enterprise" editions or Windows 8 "Enterprise" edition clients
  • At least one domain controller and Domain Name System (DNS) server running Windows Server 2008 SP2 or Windows Server 2008 R2.
  • Public key infrastructure (PKI) to issue computer certificates.

DirectAccess With Windows Server 2012 requires:

  • One or more DirectAccess servers running Windows Server 2012 with one or more network adapters.
  • At least one domain controller and Domain Name System (DNS) server running Windows Server 2008 SP2 or Windows Server 2008 R2.
  • DirectAccess clients running Windows 7 "Ultimate" or "Enterprise" editions or Windows 8 "Enterprise" edition clients
  • A Public Key Infrastructure is not required for Windows 8 Clients.[5]

Smart card certificates, and health certificates for Network Access Protection may be used along with PKI.

Outdated Information

None noted at this time. Windows Server 2008 R2 is already reaching extended support end-of-life. Windows Server 2012 R2 and Windows Server 2016 face none of these problems.

Windows Server 2008 R2 end-of-life mainstream support for the system has already ceased as of January 13, 2015

Windows 2008 R2 version of DirectAccess (not UAG version) forces one to use IPv6 end-to-end. This was due to Microsoft not including the NAT64 (IPv6 to IPv4) component in the basic version of DirectAccess included in Windows 2008 R2. NAT64 was included with Microsoft Unified Access Gateway (UAG) allowing IPv6 to IPv4 connectivity. Windows Server 2012 versions of DirectAccess have rectified this issue and are fully IPv4 supported.[citation needed]


  1. ^ "Got DirectAccess? Get UAG!". Archived from the original on 2009-07-21. Retrieved 2017-03-23.
  2. ^ "What's New in DirectAccess in Windows Server". Retrieved 2017-03-23.
  3. ^ "DirectAccess: Microsoft's Newest VPN Solution - Part 1: Overview of Current Remote Access Solutions - TechGenix". Retrieved 2017-03-23.
  4. ^ "Configuring Manage Out to DirectAccess Clients | PACKT Books". Retrieved 2017-03-23.
  5. ^ "What's New in DirectAccess in Windows Server". Retrieved 2017-03-23.

External links

This page was last updated at 2019-11-10 19:06 UTC. Update now. View original page.

All our content comes from Wikipedia and under the Creative Commons Attribution-ShareAlike License.


If mathematical, chemical, physical and other formulas are not displayed correctly on this page, please useFirefox or Safari