I just finished deploying a production DirectAccess environment with Multisite and compatibility for Windows 7 and Windows 8. DA has been awesome and been running rock solid. But we've run into a weird problem and I can't seem to find a reasonable solution for it:
We have an Authenticated Wireless network at the office that uses Windows Session credentials, so you don't actually connect and get issued an IP Address until after you log in to Windows. What we've found is that DirectAccess will obviously connect as soon as there is an active internet connection but the typical Group Policy / Home Folder / Logon Script experience fails to run if you prevent DA from connecting pre-logon.
We've confirmed that it's still functioning correctly by testing it outside the office, for example, if I take my corporate laptop home, it will connect to my wireless network at home pre-logon and once my logon finishes I get my Home Folder and logon scripts executed.
So, our question is basically this: How do you get a DA client to execute the "AD logon experience" if DA connects AFTER the user finishes a logon? (Our execs have already complained that this behavior also happens on airport or hotel wireless where you don't get internet access until you open the browser and sign your life away)