There used to be a DPPriority setting that worked before R2... -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Stephen Leuthold Sent: Friday, May 08, 2015 6:39 PM To: [email protected] Subject: [mssms] TEST DP Priority
Howdy Folks, Our packagers and OSD engineers share the same DP that is scoped to them for testing their stuff. The challenge is when we are distributing content to other DP's, for example new ones it may take up all the threads, preventing them from testing in a timely manner. I could significantly increase the threads but would rather not. I'm exploring options to expedite or ensure that content being transferred to a testing DP gets bumped to the highest priority over everything else or better yet start transferring. I understand that the DP with the most bandwidth or highest priority set via WMI will get content first. However, in this scenario it may not necessary be the same package being distributed. Therefore I'm assuming the request from the testers will just be queued if all the other threads are taken up transferring other stuff. I was thinking about putting in a solution that would watch for content queued for the test DP and use a similar method to the DP Job Manager tool to start transferring the content. Or maybe I'm getting confused with the Distmgr and pkgxfer components as it seems the DP Job Manager tool manages the pkgxfer component. I could be overcomplicating this too. Has anyone else overcome this scenario what solutions have some of you implemented to overcome challenges like this? Thank you. -Stephen
