Direct Access is an excellent vpn-solution from Microsoft. With Server 2012 R2 it got even better.
There is alot of pages telling how to install it right, but in real life you have to combine some of them.
So here goes 🙂
Installing Direct Access Server with two nics.
I want to point out couple of tips.
If you dont have CRL-list available externally. Use external publishers wildcard or named certificate. You will avoid revocation list problems.
For Windows 7 support.
Network Location Server.
You must use some other server for nls to support Windows 7. Windows 8 works when NLS is on Direct Access server, but Windows 7 wont !!
If you get error when you validate nls. Install this hotfix and reboot.
And a must install for Windows 8 and 8.1 computers.
Windows 7 client certificates required to get Direct Access online:
And remember that you will also have to get the same computer certificates for Windows 8 machines or otherwise they wont work !!
Add Group Policy for Auto-Enrollment and add the same Computer Security Group as security filtering for it. It’s the easiest way to get computers certificates for both operating systems.
Get IP-HTTPS state: netsh int httpstunnel show int
If you get this error with IP-HTTPS 0x8009030e (SEC_E_NO_CREDENTIALS) install the following hotfix:
If you still have problems with Windows 7 direct access. See this link.
With these you can get both of them work with a single gpo. You dont need to copy the default and add DTE Addresses and Corporate Resources in it !!
And as a last tip for today. Direct Access Connectivity Assistant is only for diagnostics use with Windows 7. You dont need to install it.
Thanks for Jack Stromberg and SysComLab for the help!