We are trying to understand how the 2 hour deployment randomization works in SCCM 2012 r2 and if there is a limit to the amount of installs that can happen at once.
Example of what I'm looking for:
Lets say there is an Office of 800 PC's and one DP on Server 2008r2. Out of the 800, 500 are online and a deployment kicks off.
1. Will it take that 500 PC's and evenly spread the deployment out over 2 hours or is this totally at random?
2. if a PC comes online 10 minutes after the deployment has started, will it have to wait until the end of that 2 hours for the software to install or will it also pick a time within that 2 hours?
3. After the 2 hours is up will the rest of the installs kickoff no mater how many are left?
4. Is there a concurrent install limit set, meaning will it only install that Application on X amount of pc's at a given time?
Thanks for any help you can give.
Mike.