Bind network access account with a boundary group
With the 1610 update to the boundary groups it seem to be easier to control the content location for a client.
Why not make it even better and move the network access account configuration to the boundary group configuration, or make it possible to bind a network access account with a boundary group.
In this way we can define exactly what network access account that should be used accessing content.
Thomas Forsmark commented
This would be useful in scenarios where there are DP’s in untrusted domains. As it is now the ConfigMgr client will just try all NAA’s until it finds one that is working in the actual domain. This causes the OSD TS to hang for one or more minutes while the different NAA’s are tried.. waiting for it to timeout, try again and then going to the next NAA.