Does anyone know how task throughput affects managed installs?
Im in the process of deploying Office 2013 and I have the MI configured with Alert user before run. Its set to timeout after 15 minutes and set to install later if it times out. That gives the user the option to delay the install if they choose to. We have our task throughput set to 4.
Im seeing a very low number of installs after a few days so Im wondering how this process is actually working. Im thinking with a task throughput of 4, it would alert 4 people its available and if they choose to install now, it would start downloading and then install. I have the script Im running in the MI logging elsewhere and I am typically see 4 in progress at 1 time. What Im not seeing is the next 4 start after the first 4 complete. I cant tell if its ever alerting more than the first 4 people. Im also wondering what happens if those 4 people all delay the install, does it move on and do more people or wait until they are done? Does it only do 4 per each scripting update interval or inventory interval, Im cant tell at this point.
If it really is prompting everyone that I force a refresh on and then just throttling 4 at a time then I appear to have more then 95% either ignoring the message or delaying it and never installing it. I intentionally left max attempts blanks because I want it to attempt to install indefinitely rather than have it quit trying after they ignore it 3 times.