Maintaining up-to-date software is critical for security and operational efficiency. HEIMDAL's 3rd Party Patching Management simplifies this process by automating patch deployment across your network. However, in areas with limited bandwidth, such as vessels or remote locations, optimizing bandwidth usage becomes essential. This article explores how Heimdal’s Priority Server Updates feature addresses this challenge and the bandwidth requirements for effective operation by routing patches through a single server. The routing takes patches from the WAN network onto the Priority update server, which then distributes those packages on the LAN network, with Heimdal technology, and limits the bandwidth of the server using NetLimiter.
1. Configuring Priority Update Servers
2. Showcase
3. Configuring 3rd Party Patch Management and QoS Policies in HEIMDAL
4. Conclusion
Priority Server Updates is a feature that allows administrators to designate specific endpoints as central servers for downloading and distributing updates to other devices in the network. This significantly reduces external bandwidth usage, as only the Priority Servers connect to external sources for updates, and other endpoints retrieve updates internally.
CONFIGURING PRIORITY UPDATE SERVERS
1. Access the HEIMDAL Dashboard by logging in with your administrator credentials.
2. Configure Group Policy:
- Go to the Endpoint Settings and select the Group Policy you wish to modify.
- Enable the Use Priority Update Servers option.
-
Assign Priority Servers:
- In the Device Info view, select the endpoints to act as Priority Servers.
- Mark these endpoints as Priority Update Servers.
- Save Changes: Apply the settings to activate the configuration.
For optimal performance of the 3rd Party Patch Management, HEIMDAL recommends the following minimum bandwidth requirements:
- Endpoints: 10 kbps
- Priority Update Servers: 80–100 kbps
These values ensure efficient communication and update distribution without overloading your network. To maintain a balanced network load and ensure timely updates, the interval checks should be configured as follows:
-
Priority Server Update Interval - must be higher than 120 min;
-
Additional check interval - should be set at 720-1440 minutes;
- Endpoints and Priority server updates must run under the same policy.
- Keep cached files indefinitely should be enabled.
- Real-time communication should be OFF.
IMPORTANT
To ensure the endpoint receives all required updates from the machine designated as the Priority Server Update, every application installed in your environment must also be installed on the Priority Server Update machine. If any applications are missing on the Priority Server Update machine, the endpoint will not be able to retrieve the required patches.
SHOWCASE
Using NetLimiter, we monitored and restricted the bandwidth of the Heimdal.ClientHost process. The objective was to identify the lowest bandwidth thresholds that allow the 3rd Party Patch Management to operate successfully on endpoints and servers.
The test results show the following:
- Endpoints - a minimum bandwidth of 10 KB/s is required for the 3rd Party Patch Management to work effectively. Below this threshold, operations fail or are severely impacted. A server receiving updates from the Priority Update Server is also considered an endpoint in this scenario.
- Priority Update Server - the tool functions correctly with a minimum bandwidth of 80 KB/s. Below this threshold, failures are observed.
Operational example at 10 KB/s (Endpoints) and 100 KB/s (Servers)
Here are screenshots from the test, showcasing the bandwidth configurations and results:
Initial setup
Description: NetLimiter shows the active Heimdal.ClientHost process with bandwidth limited to 100 KB/s for endpoints and 80 KB/s for servers.
Operation at 10 KB/s (Endpoints) and 100 KB/s (Servers)
Description: 3rd Party Patch Management is starting to patch CCleaner.
Failure Below Thresholds
Description: 3rd Party Patch Management has patched CCleaner.
The test was performed with 4 applications: 7-Zip, Adobe Acrobat Reader, CCleaner, and Google Chrome.
CONFIGURING 3rd PARTY PATCH MANAGEMENT AND QoS POLICIES IN HEIMDAL
This guide outlines the prerequisites and steps to configure 3rd Party Patch Management using HEIMDAL and implement Quality of Service (QoS) policies for optimal update management.
Prerequisites
Before proceeding, ensure the following conditions are met:
1. Network Configuration:
- All endpoints/machines must be connected to the same network.
- The network profile on each machine must be set to Private:
- Navigate to Network & Internet settings > Properties, and set the network profile to Private.
- ⚠️ Important: The network profile must be Private, especially on the machine designated as the Priority Update Server (PUS).
- In Heimdal Group Policy > General > General Management, activate: Use Priority Update Servers and Keep cached files indefinitely. If the PUS is activated before agent installation, the application catalog zip file will only download on the PUS endpoint. Other VMs will retrieve the file from the PUS endpoint. This may delay app installations on non-PUS endpoints due to the file transfer process.
QoS Policy Rules:
- On endpoints, open PowerShell as Administrator and configure QoS rules:
-
On the PUS endpoint, access PowerShell and run:
New-NetQosPolicy -Name "Heimdal Client" -NetworkProfile All -AppPathNameMatchCondition "Heimdal.ClientHost.exe" -ThrottleRateActionBitsPerSecond 80KB -
On the non-PUS endpoint, access PowerShell and run:
New-NetQosPolicy -Name "Heimdal Client" -NetworkProfile All -AppPathNameMatchCondition "Heimdal.ClientHost.exe" -ThrottleRateActionBitsPerSecond 10KB
-
Recommended Workflow
-
Validate Network Configuration:
- Ensure all machines are connected to the same network.
- Confirm that the network profile on all machines, particularly the PUS, is set to Private.
-
Create QoS Policy Rules:
-
On the Priority Update Server machine, access PowerShell and run:
New-NetQosPolicy -Name "Heimdal Client" -NetworkProfile All -AppPathNameMatchCondition "Heimdal.ClientHost.exe" -ThrottleRateActionBitsPerSecond 80KB
-
On the non-PUS machines, access PowerShell and run:
New-NetQosPolicy -Name "Heimdal Client" -NetworkProfile All -AppPathNameMatchCondition "Heimdal.ClientHost.exe" -ThrottleRateActionBitsPerSecond 10KB
-
-
Activate Heimdal Policy Settings:
- In Heimdal Group Policy > General > General Management, activate:
- Use Priority Update Servers
- Keep cached files indefinitely
- Set Additional check interval for normal computers [min] to its maximum value.
- In Heimdal Group Policy > General > General Management, activate:
-
Sync Group Policies:
- Ensure all machines sync the updated group policies.
-
Add Applications for 3rd Party Patching:
- In Group Policy > Patch & Assets > 3rd Party Patch Management, add the desired application(s) to install.
-
Install Applications on PUS Machine:
- Sync the group policy on the PUS machine and wait for the application installation to complete.
-
Install Applications on Non-PUS Machines:
- Sync the group policy on the non-PUS machines. The application files will transfer from the PUS, and the installation will proceed.
Key Notes
- Ensure proper synchronization of group policies across all machines to avoid delays.
- Monitor the app catalog file transfer on non-PUS machines for any potential delays.
- Review QoS policy configurations periodically to maintain consistent network performance.
By following these steps, you can effectively manage 3rd Party Patching and optimize update delivery using Heimdal Security.
CONCLUSION
HEIMDAL’s Priority Server Updates is a strategic feature designed to optimize bandwidth usage and streamline patch distribution in environments of all sizes. With the proper bandwidth allocation and interval settings, it ensures reliable and secure updates while minimizing the strain on your network. The results of our recent test with NetLimiter confirm that these configurations effectively balance performance and resource utilization. Implementing Priority Server Updates and adhering to the recommended settings will enhance the efficiency of your patch management strategy.