In Windows Server 2016, the Remote Access server role includes three role services – VPN and DirectAccess (also known as Remote Access Service, or RAS), Routing, and Web Application Proxy.
If you work for an Enterprise, you probably want to provide your organization employees with the ability to connect to your network from remote locations. If you deploy Remote Access and the VPN and DirectAccess role service, you can configure a computer or a virtual machine as both a VPN server and a DirectAccess server.
For those who want to use DirectAccess – with or without VPN services enabled on the same Remote Access server – the Windows Server Networking documentation team now has five new DirectAccess documents available on the Web.
The top node document is DirectAccess, which includes links to all five new documents and a brief overview of DirectAccess, including the client and server operating systems that support DirectAccess. The additional five documents are:
DirectAccess Deployment Paths in Windows Server. This topic provides a listing of the documentation for the two main Remote Access deployment paths: Basic and Advanced.
Prerequisites for Deploying DirectAccess. This topic provides the prerequisites necessary for using the configuration wizards to deploy DirectAccess.
DirectAccess Unsupported Configurations. With this topic you can review the list of unsupported DirectAccess configurations before you start your deployment.
Deploy a Single DirectAccess Server Using the Getting Started Wizard [Basic]. This topic provides an introduction to the DirectAccess scenario that uses a single DirectAccess server, and allows you to deploy DirectAccess in a few easy steps.
Deploy a Single DirectAccess Server with Advanced Settings. This topic provides an introduction to the DirectAccess scenario that uses a single DirectAccess server, and allows you to deploy DirectAccess with advanced settings.