So there is a way. But if this value is set to 61, then why does the help page for LANDesk 9.6 talk about the how the "default push distribution task type builds target lists of up to 241 devices and processes these devices one target list at a time, waiting until jobs complete before moving on to devices in the next target list"? If the "Distribute to xx computers simultaneously" setting is 61, then how could or why would the server build target lists of 241 devices for pushes?
If I leave this value at 61 computers, and I push a LANDesk software distribution scheduled task over a WAN link to 300 computers running the LANDesk 9.6 agent, and I do not select accelerated push, then what is the maximum number of computers that will execute the task simultaneously?
Under 9.5, with the push delivery method set to 61 simultaneous devices, I see a maximum of 61 computers active at any one time. Now is that because of the delivery method setting or the "Custom Jobs" setting? Under 9.6 pushing to a LANDesk 9.6 agent, would I still see a maximum of 61 computers active at any one time? Does the "Custom Jobs" setting override the 9.6 Agent settings (and the delivery method settings for pre-9.6 agents)?
This is a good questions. I assume that, though LD9.6 processes 1 target list at a time (which can contain up to 241 devices) the number specified under custom jobs determines how many of the 241 devices can have jobs distributing to at a given time. It will distribute simultaneously to the number of devices specified in the custom jobs settings until it has completed all 241 devices in the first target list, then begin the same process on the next.
Perhaps some can verify this?
This is where you set this:
This controls the accelerated push. if not accelerated then it works one machine at a time but moves quickly onto the next one to start it checking for policies (even if it is a Push). If you tell it to '•Wait for each machine to finish processing the task' then you really do just get one machine at a time! There is also no obvious way to limit the download to one machine on a subnet at a time.
You need to be careful with your distribution agent settings.regarding whether preferred servers or source can be used. The changes mean you can get stuff launched VERY quickly, but without adequate planning of where they can get files from then you need to be mindful of the bandwidth throttling options.
MarXtar Ltd/MarXtar Corporation
LANDESK One Development Partner
The One-Stop Shop for LANDESK Enhancements