Is it possible to limit number of concurrent deployments?

[jprateragg]

I see in Server Options there's a setting to limit the deployment threads. But, what I would like to do is limit the actual number active deployments currently being performed. For example, if I deploy something right now, Lansweeper will reach out to 10-15 computers. I would like to limit this to say like 5. Is this possible? I've changed the value of the "Deployment Threads" in Server Options and it has no affect.

[Daniel_B]

In case your issue is the network traffic between the package share and target computers, consider setting up local package share folders in your subnets and configuring these under Deployment\Security options. This prevents installer files to be transferred over small WAN lines during deployment.

The topic was discussed here as well.

[Bert_D · Accepted solution]

The amount of threads it uses, is not equal to the amount of simultaneous deployments.
With your settings it will use up to max 3 threads to process the started deployments.
The more threads you have, the faster it will go.

For example: lets say, for the sake of argument, starting a deployment takes 1 second.
You configured Lansweeper to only use 3 threads.
Deploying on a group with 3 assets will take 1 second.
(3 assets, 3 threads => each thread runs 1 time)
Deploying on a group of 30 assets will take 10 seconds
(30 assets, 3 threads => each thread runs 10 times)

You configured Lansweeper to use 15 threads.
Deploying on a group with 3 assets will still take 1 second.
(3 assets, 15 threads => only 3 threads run 1 time)
Deploying on a group of 30 assets will take 2 seconds
(30 assets, 15 threads => each thread runs 2 times)

Hope this answers your question.

[jprateragg]

I have it set to 3, and it's been set to 3 for a while. And the server has been rebooted several times for standard Microsoft updates. But it will deploy like 15 at a time.

[Michael_V]

Changing the deployment threads only works after restarting the Lansweeper service.