The knowledgebase is a categorized collection of answers to frequently asked questions (FAQ) and articles. You can read articles in this category or select a subcategory that you are interested in.
To maintain a high protection level, you may notice an increase in bandwidth due to the increased number of updates released per day. Policy Manager Proxy (PMP) installations are especially affected as the additional strain on the likely slower network connection that exists between the remote site hosting the PMP installation(s) and the main corporate site with Policy Manager Server (PMS). The network bandwidth usage can be especially high when computers are turned on Mondays as the update packages accumulate over the weekend.
By default, the Automatic Update Server (AUS) in the PMS calculates byte-level differences for the last five update packages (per update channel). In the event where computers were turned off over the weekend, client machines have missed five updates, and the PMS will then download a full update package (Aquarius Windows updates can be approximately 140MB in size). When this happens, network bandwidth usage can be excessively high.
#/etc/init.d/crond stop, to prevent a new update from starting.
# ps -C fsauasc
The command indicates whether the "fsauasc" application is running. If the process is listed, wait a few minutes and repeat the step.
Only proceed with the next steps when the "fsauasc" process is no longer visible on the list.
The overall disk space requirement for PMS increases. We estimate the disk consumption to increase by 10GB. Make sure the hard disk hosting the Policy Manager Server installation (
Program files\F-Secure\Management Server 5\) has enough disk space.
Use the Advanced mode in Policy Manager Console (View > Advanced mode) to edit the setting.
Verify the setting on all Policy Manager Proxy systems and adjust the settings, if needed. The setting specifies how much disk space is set aside for storing databases on the Policy Manager Proxy.
As Policy Manager Proxy on Linux is not centrally managed, the change involves modifying a configuration file that exists on the Policy Manager Proxy system locally.
These steps for both Windows and Linux ensure that the cache size available on the PMP for file storage is increased.
In case the client is unable to connect to the Policy Manager Proxy, for example due to high network traffic and multiple downloads taking place, the following setting dictates how soon the client attempts to connect directly to the Policy Manager Server to download updates.
To help prevent clients from immediately falling back to downloading updates directly from the PMS:
The default value is zero which means fallback to PMS takes place immediately, in which case the Policy Manager Proxy installation cannot be reached.
These steps should ensure database updates are only downloaded via the PMP.
Article ID: 31
Views : 793
Rating (Votes): (1)