Offline Files and VPN

Windows offline files over VPN depends on IPv6.

See this guys post for evidence:
http://thommck.wordpress.com/2011/02/08/offline-files-versus-vpn-a-k-a-the-case-of-the-missing-work-online-button/

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

Exchange 2007 Transport Service Not Starting

I found the following error in the Application Event Log

Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC)

The fix was to reenable IPv6 on the server's NIC.

Other fixes, some of which are NOT best practice so are used at your own discretion, are available here:
http://blogs.msdn.com/b/keithmg/archive/2009/01/06/exchange-topology-discovery-failed-error-0x80040a02-dsc-e-no-suitable-cdc.aspx

References:
http://blogs.msdn.com/b/keithmg/archive/2009/01/06/exchange-topology-discovery-failed-error-0x80040a02-dsc-e-no-suitable-cdc.aspx