Remote Administration of External DirectAccess Clients

I've read conflicting articles about remote administration of external DA clients. One Technet blog here http://blogs.technet.com/b/edgeaccessblog/archive/2010/09/14/how-to-enable-remote-desktop-sharing-rds-rdp-from-corporate-machines-to-directaccess-connected-machines.aspx says:

"Because we use IPv6 in Direct Access, any corporate client that wants to communicate to the DirectAccess clients must have an IPv6 address.  We can set up either a real IPv6 addressing scheme or set up ISATAP, which does not require IPv6 aware routers, switches or hubs".

But then when I read anything about configuring DA anywhere else on Technet it says using ISATAP on the corporate network is not supported.

Confused???



  • Edited by broonster27 Thursday, August 20, 2015 2:55 AM
August 19th, 2015 11:39pm

I have subsequently found an interesting article (http://blogs.technet.com/b/jasonjones/archive/2013/04/19/limiting-isatap-services-to-directaccess-manage-out-clients.aspx) which shows how to enable ISATAP for administrative PCs only. I'm not 100% sure if it's officially supported by MS but it definitely works and no IPv6 infrastructure is required as a Server 2012 R2 DirectAccess server is installed as an ISATAP router by default.

  • Marked as answer by broonster27 2 hours 34 minutes ago
Free Windows Admin Tool Kit Click here and download it now
September 2nd, 2015 12:32am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics