ConfigMgr : Managing DirectAccess Clients

We’re currently testing a Windows 2012 R2 DirectAccess deployment, part of this is includes a swathe of application testing. During this testing we found that SCCM clients were unable to download content from any DPs, meaning Software Deployment was failing when connected via DirectAccess. The solution is not suprising – you need to modify the SCCM Boundaries and ensure you have defined a boundary for your IPv6 Prefix, assigned to your DirectAccess clients.

To find the prefix, view the properties of a DirectAccess-enabled device in SCCM – you’ll see the detected IPv6 prefixes within the captured properties. Simply add the correct prefix to your SCCM boundary configuration.