This article will only show the required steps to prepare Forefront TMG as a DirectAccess Server. The DirectAccess configuration is out of scope in this article as it is well covered in many articles on the Net. You will find some helpful links at the end of this article.
The first important step you have to understand is that Forefront TMG doesn’t accept any IPv6 traffic or allow it to pass through it, so we must first modify this behavior BEFORE Forefront TMG gets installed to allow the following traffic:
Inbound authenticated IPv6 traffic (using IPSec). This also includes the IPSec initiation traffic.
Inbound and outbound IPv6 transition technologies (6to4, Teredo, IP-HTTPS and ISATAP).
Native IPv6 from the Forefront TMG machine.
In addition, Forefront TMG integrates with the IPSec Denial of Service Protection (DoSP) component of Windows DirectAccess to ensure that only IPSec traffic is allowed through it.
For this reason, it is really important to install and configure Windows Server 2008 R2 DirectAccess before installing Forefront TMG.
First, we have to install the Windows Server 2008 R2 DirectAccess Management console as shown in the following screenshot.
Figure 1: Installing the Windows Server 2008 R2 DirectAccess feature
After the Windows Server 2008 R2 DirectAccess Management console has been installed, start the console and configure DirectAcces and test the entire functionality before you install Forefront TMG.
Figure 2: DirectAccess Management console
After you verified the successful DirectAccess installation and configuration, we have to modify the Registry with a new Registry key before installing Forefront TMG. This Registry key prevents Forefront TMG to disable the IPv6 protocol support during the Forefront TMG installation.
Figure 3: Script to activate IPv6 protocol support for Forefront TMG
After the Registry has been modified successful install Forefront TMG in the way you install every Forefront TMG Server. After Forefront TMG has been installed, we have to modify the Forefront TMG configuration storage with a script which enables IPv6 support for Forefront TMG. Copy the following lines into an empty Notepad file and save it with the .VBS extension.
set o = createobject(“fpc.root”)
setarr = o.Arrays.Item(1)
set policy = arr.ArrayPolicy
set IPV6Settings = policy.IPv6Settings
IPV6Settings.DirectAccessEnabled = vbTrue
Figure 4: Save the script with the .VBS extension
Save the script with the .VBS extension and run it from an elevated command line with the following command:
Due to the Forefront TMG configuration change it takes some time until the configuration has been successfully synchronized. You can see the configuration state in the Forefront TMG Management console as shown in the following screenshot.
Figure 5: Wait for Forefront TMG Storage synchronization
The script creates four new System Policy rules to allow IPv6 traffic for DirectAccess.
Figure 6: Some new Forefront TMG System Policies
Where is the “Act as a Direct Access server” button in Forefront TMG?
Forefront TMG Beta and RC had an IPv6 tab in the IP preferences section in the Forefront TMG console to configure Forefront TMG as a DirectAccess Server as shown in the following screenshot.
Figure 7: Act as a Direct Access Server button
After Forefront TMG has been RTM, I’ve never seen this IPv6 tab again, so my assumption is, that it was removed from the Forefront TMG Management console, and DirectAccess works without this DirectAccess button 🙂
Figure 8: Where is the DirectAccess button seen in Beta and RC versions of Forefront TMG
Hide IPv6 Log entries
Forefront TMG has the option to Hide IPv6 traffic from the Real-time monitoring tab. Because Forefront TMG has no full support for IPv6 it might be an option for you as a Forefront TMG administrator to hide the entries to have a clearer view in the TMG logging.
Figure 9: Hide IPv6 log entries
If you want to have more functionality and flexibility you can use Forefront UAG for your DirectAccess scenario. Using Forefront UAG has the following advantages:
Scalability (up to 8 Forefront UAG Server joined into an Array)
High availability (with Windows Server 2008 R2 NLB)
Access to corporate legacy servers over IPv4
Easier configuration, deployment, and management
Forefront UAG installs Forefront TMG on each node during Setup
Alternative remote access solution for non-domain joined machines
In this article we went through some information about how to configure Forefront TMG as a DirectAccess Server. In my opinion using Forefront TMG as a DirectAccess Server is good choice when you don’t want to have High Availability and you don’t need the advanced features of Forefront UAG like Portal access and advanced Endpoint Security Policies.