Is there any way to set a concurrent deployment limit for a specific package? Or maybe some other way to stagger a deploy?
I have a package that tells all our servers to go check for updates and to download them. This can overload our ASA and WSUS server if 100+ machines all try to download at the exact same time. Is there any way to avoid this?
I thought of either:
1) Set the concurrent limit to 10 servers at a time and let them fire off more as they complete. However, I only see a global setting and nothing anything that can be customized per package or per schedule
2) Set some sort of random offset for each job. This wouldn't be quite as good as we could still end up with a whole bunch going near the same time, but I guess might at least help a bit.
Any other ways to do this?
Please sign in to leave a comment.