cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
jprateragg
Champion Sweeper
We have 20 branch offices all connected via VPN. Some of these connections are very slow, only 1.5 mbps (T1). What is the order in which packages are deployed to computers across different subnets? Is it random? Does it complete one subnet at a time? Does it do it by asset name?

I'm only asking because it seems whenever we deploy a package, it seems to deploy it by each subnet. It will deploy to one subnet, and when it's finished, move to the next subnet. This wreaks havoc on our offices with slow VPN connections. Thanks.
1 ACCEPTED SOLUTION
Daniel_B
Lansweeper Alumni
Deployment won't be grouped by subnets normally. As mentioned by Michael.V, under Deployment\Security options you can set up one package share for each IP range location (IP locations need to be set up under Configuration\Asset groups). In this way, Lansweeper will dynamically assign a local package share based on the IP address of the target computer at the time of deployment. The network traffic between your Lansweeper server and target computers will be minimal.

You could still reduce the number of concurrent deployment threads under Configuration\Server options, section Service options.

View solution in original post

2 REPLIES 2
Daniel_B
Lansweeper Alumni
Deployment won't be grouped by subnets normally. As mentioned by Michael.V, under Deployment\Security options you can set up one package share for each IP range location (IP locations need to be set up under Configuration\Asset groups). In this way, Lansweeper will dynamically assign a local package share based on the IP address of the target computer at the time of deployment. The network traffic between your Lansweeper server and target computers will be minimal.

You could still reduce the number of concurrent deployment threads under Configuration\Server options, section Service options.
Michael_V
Champion Sweeper III
Not really answering your question but:

You can setup a packageshare in each subnet, the deployer will automatically download from the local packageshare to save bandwidth.