Distribution point ordering/intelligence
Make it possible to assign multiple DP's to a boundary group with the ability assign an order in which they are accessed by clients. ATM if there are multiple DP's per boundary group and all are defined as fast (or slow), the DP is chosen randomly. At the very least a DP that resides in the same subnet with the client, should always take precedence,
With the boundaries group rearchitecture completed in 1702, these scenarios should now be solved… with much more granular control on when and how to fail over to different DPs. Also, the client will pick the same DP on the same subnet.
Zeng Yinghua (Sandy) commented
David. I didn't test production 1702, only tested in TP 1702. Cliet picked the same DP on the same subnet only after ConfigMgr client is installed. But during Full OS deployment (winpe), client didn't pick the same DP on the same subnet.
Craig Wilson commented
Just been stung by this resulting in me scratching my head until I realised I had a down DP (lets call it DP1... ). OSD clients would connect to DP2 and apply the OS, but when it rebooted it would then "connect" to DP1 and fail to deploy anything (including the Agent).. Very few errors to say that the DP wasn't there ..
Being able to set preference - or even "disable" a DP in a group would be ideal.
Dustin Hedges commented
Also helps when the assigned MP is also a DP.
Mohanad Zaki commented
This would be nice function.
Zeng Yinghua commented
This would be nice function. Current setting we can only assignment fast or slow, would be good to have also "priority" setting, so that clients machines choose download content frome which fast DP first, if that DP is not available, then automatically choose the second priority fast DP.