Enable Manage-Out via DirectAccess when Internal LAN is IPv4 Only

Normally manage-out functionality is not available using DirectAccess if your internal LAN is IPv4-only. E.g. your remote devices will be able to access resources on your network, but you won't be able to connect to those devices from your management servers etc to check status, roll out updates, etc - unless your internal LAN is running IPv6.

However, the following link provides a potential way to get around this:

http://blogs.technet.com/b/jasonjones/archive/2013/04/19/limiting-isatap-services-to-directaccess-manage-out-clients.aspx

NOTE: This may not work in multi-site deployments. I haven't looked deeply enough into it to know why not.

References:

http://blogs.technet.com/b/jasonjones/archive/2013/04/19/limiting-isatap-services-to-directaccess-manage-out-clients.aspx