Migrate from Forefront UAG SP1 DirectAccess to Windows Server 2012
Updated: February 29, 2012
Applies To: Windows Server 2012 R2, Windows Server 2012
This document describes the migration of an existing Forefront UAG SP1 DirectAccess deployment to DirectAccess in Windows Server® 2012. It illustrates migration of a simple scenario that includes either a single Forefront UAG server, or an array of Forefront UAG servers configured in a single domain and a single site using NAT64, and not set up as an ISATAP router. Note that this upgrade is only supported for computers running Forefront UAG SP1.
Following is a listing of the documentation for the three main Remote Access deployment paths: Basic, Advanced and Enterprise. Also listed are the Managing and Migrating documents available for this release.
Supported migration scenarios for Forefront UAG SP1 are as follows:
Supported client operating systems
Supported domain controllers
Supported application servers
Windows® 7Windows 7
Windows Server 2012
Windows 2003 Server
Windows Server® 2008
Windows Server® 2008 R2
Windows Server 2012
Windows 2003 Server
Windows Server 2008
Windows Server 2008 R2
Windows Server 2012
Two migration scenarios are described:
Side-by-side migration— Use this type of migration to keep the Forefront UAG DirectAccess server running while you deploy DirectAccess in Windows Server 2012. After the deployment is complete, DirectAccess clients use DirectAccess configured on the Windows Server 2012 computer, and the Forefront UAG server is removed from service. This type of migration requires duplication of some settings because FQDN, IP addresses, and certificate settings must be unique on each server.
Offline migration— Use this type of migration to copy the DirectAccess configuration with identical settings from the Forefront UAG DirectAccess server to the Windows Server 2012 computer running as a Remote Access server. Then shut down the Forefront UAG server. Service for DirectAccess clients will not be available until the Windows Server 2012 Remote Access server is up and running.
Before you begin deploying this scenario, review this list for important requirements:
ISATAP in the corporate network is not supported. If you are using ISATAP, you should remove it and use native IPv6.
If NAP is used inbox in UAG, NAP is now going to require a separate NPS server.
NAP was deprecated in Windows Server 2012 R2. This means that NAP may not be supported in future versions of Windows. New deployments with NAP are not recommended.
This scenario describes how to continue running an existing DirectAccess deployment using Windows Server 2012 instead of Forefront UAG.
Hardware requirements include the following:
One or more Forefront UAG servers successfully running a DirectAccess deployment.
Windows Server 2012 Remote Access server requirements:
A computer that meets the hardware requirements for Windows Server 2012.
Client requirements for DirectAccess in Windows Server 2012:
A client computer must be running Windows® 8 or Windows 7.
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
A certification authority (CA) server is required if certificates will be issued for authentication of IP-HTTPS and the network location server. Note that DirectAccess in Windows Server 2012 supports the use of self-signed certificates created automatically during DirectAccess deployment.
A DNS server running Windows Server 2003, Windows Server 2008 SP2; Windows Server 2008 R2; or Windows Server 2012 is required.
There are a number of requirements for this scenario:
DirectAccess server requirements in Windows Server 2012:
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.
The person deploying remote access on the server requires local administrator permissions on the server, and have a domain user account. To prepare the GPOs domain administrator permissions 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.
ISATAP is not recommended for use as the IPv6 to IPv4 transition technology in DirectAccess in Windows Server 2012. If Forefront UAG is configured to use ISATAP, it is recommended to disable it, and use NAT64 instead.
With ISATAP disabled DirectAccess clients can initiate connections to computers on the internal network, and the computers on the internal network are able to respond. However, computers on the internal network will not be able to initiate connections to DirectAccess for purposes of remote client management. If you want to be able to remote client management, consider deploying native IPv6 for management servers that will connect to DirectAccess client computers.
Forefront UAG provides complex Network Access Policy (NAP) configuration settings, and the Network Policy Server (NPS) and Health Registration Authority (HRA) roles can be installed on the Forefront UAG server. These settings are not supported for DirectAccess in Windows Server 2012. In Windows Server 2012, you can only specify whether or not client compliance is enforced using NAP during IPsec authentication. NPS and HRA roles are installed on remote servers in the internal network. The HRA server must be accessible over the first DirectAccess tunnel, or over the Internet.