Start at the lowest you can go with it (for percentage - it's 1%), adjust as needed if that proves to be a burden on the network you can move to a 'kb' static setting for the clients.
Take into account the number of clients connecting as well, if all the clients are connecting at relatively the same bandwidth... 100 clients @ 1% is still, 1 client wide open (zero throttle) and if 1 client wide open is straining the VPN network then adjust to static 'kb' settings. So, it really depends on what your network can handle for VPN.
Relatively speaking throttling should resolve most bandwidth issue(s) but, bear in mind that even with throttling there is dropped packets, re-requests, etc (normal network traffic issues) to take into account as well and this includes software/patch deployment sizes. There are plenty of network bandwidth calculators to use on the internet, you can run the calculations based on patch size to bandwidth to come up with ETA for a complete download, etc.
A blockout is your friend as well, you can enable the blockout for downloads during the day and open in the evening if that helps. CEM is also another option.
Hope this helps.
Original Message:
Sent: 03-30-2020 06:50 AM
From: Andrew Brain
Subject: Throtling Settings
Hi All,
Can someone recommend some throttling setting for these times when every VPN is being hammered. We are seeing massive issues when the agents are communicating and this is destroying our network. Id still like to be able to send out patches and software but cannot have it kill the connections.
Any advice would be greatly appreciated.
Thanks
Andrew
------------------------------
Andrew Brain
Team - Manager Vale of Glamorgan Council
------------------------------