Back to ConfigMgr main menu
Many of us have seen the problem. We have configured our laptops to use Direct Access and we never see them again. The ConfigMgr 2012 client is installed but has never received it's policy or reported correctly.
This is the dreaded ConfigMgr client that has never received policy.
Only two actions.
What is the problem? The problem is that ConfigMgr is not allowed to send a policy to these devices as they do not belong to any of the known boundaries. The good news it that this is easy to fix. We have to configure an IPv6 boundary.
It's easy to get the information we need. Open the properties of one of your Direct Access clients.
See the IPv6 Prefixes.
Create a boundary for each IPv6 prefix.
Restart the SMS Agent Host on the client to speed things up. Now examine the PolicyAgent.log file.
We see activity.
The policy is now being downloaded to the client.
Success - healthy client
See here for additional tip for finding your IPv6 Prefix.