How can I upgrade the F-Secure Scanning and Reputation Server (SRS) to the latest version?
The F-Secure Scanning and Reputation Server (SRS) updates the virus definitions automatically but does not update the server itself. Since the SRS is self contained, an upgrade is not possible. A new installation is required. If you wish to install the the latest version of the F-Secure Scanning and Reputation Server, follow these steps:
Install and configure the new Scanning and Reputation Server (SRS) instances (refer to the Deployment guide Virtual Security ) with different IP addresses than the existing instances. This is to ensure both the current and new instances can work simultaneously during the transitional period Once installed and configured, log into F-Secure Policy Manager Console, go to the settings tab and choose advanced view. Navigate to F-Secure > F-Secure Offload Scanning Agent > Settings > Connection > Primary servers and replace the IP addresses to the new addresses that you have set for the new instances, and distribute policies (CTRL + D) Allow all hosts to update to the new configuration. To verify, go to the Status tab in the Policy Manager Console and check whether the hosts are connected and having the latest policy in use (Centralized management) Once all hosts are updated and the new servers appear to work as should, you may shut down the old SRS instances and remove them from the Policy Manager Console
Article no: 000014810
Server Security has scanning errors and causing performance and hanging issues on virtual servers. Application event log shows error: "The description for Event ID 301 from source FSecure-FSecure Application-F-Secure Anti-Virus cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer." Issue has started on one or more virtual servers at the same time. Lynx.log shows following error: W: ComTransaction::GetResult: Exception: Type: fs::BaseException, Reason: invalid status code 500, Function: fs::rs::AbstractTransaction<class fs::rs::Icap>::getResult, File: "c:\\workspace\\workspace\\spt_lynx\\src\\fsciapi\\svce_common\\transaction.h", Line: 235 F: ComTransaction::GetResult: Creating a new transaction failed.
On virtual servers the scanning is often offloaded to a Scanning and Reputation Server (SRS) to minimize the performance impact. If you have an Scanning and Reputation Server in use, the Event ID 301 error on the client side can be caused by an Scanning and Reputation Server that is having issues. Restart the Scanning and Reputation Server to see if it helps:
Open the virtual machine console Log in to go to the Admin menu Select 6 to reboot or shut down the appliance The Power management menu opens Choose: Select 1 to restart the server
If a restart of the Scanning and Reputation Server does not fix the issue, follow these steps to install a new one: https://help.f-secure.com/product.html#business/fsvs/latest/en/concept_FAA8187341EF42DA8264EAF45CF42B6B-fsvs-latest-en If a new installation of the Scanning and Reputation Server does not fix the issue, troubleshoot issues on the server where you have installed the Scanning and Reputation Server.
Article no: 000017702
F-Secure scan modules for Server Security Premium 12.11 Build 103 are not loaded on the terminal servers. The FSAUA reset tool has already been already executed without success. The server is running on Windows Server 2012 R2. When performing a manual scan the error "No scan modules loaded" appears.
First make sure you are able to ping your F-Secure Scanning and Reputation Server. If the ping results are ok, then the Agent is most likely down "Reason: Transport is down, Function: fs::rs::Library::newTransaction, File: "library.cpp", Line: 222, Error Code : 34" due to some changes made possibly in Policy Manager Server, like new installation, migration, settings removed. To make sure your clients are connecting to F-Secure Scanning and Reputation Server, open Policy Manager Console and check the settings bellow: For Clients 12.xx and 13.xx
Open Policy Manager Server/ Console in advanced view and navigate to Offload Scanning Agent: Specifies the primary F-Secure Scanning and Reputation Server(s) that are used for remote content inspection and reputation services. The server is defined as <host>[:<port>], where <host> is IP address or FQDN of the server and <port> is the port number the server accepts incoming connections from the client. If the port is not defined, then the default one is used. Use the comma separated list if multiple servers are used. For example, "192.168.1.10, 192.168.1.12:4344". Object identifier: 220.127.116.11.4.1.218.104.22.168.10
For Clients 14.xx
Open Policy Manager Server/ Console in Standard view and navigate to Real-time scanning and make sure your F-Secure Scanning and Reputation Server addresses are correct configured and the check box is selected.
Article no: 000014714
How many virtual Windows workstations could be managed by one F-Secure Scanning and Reputation Server? What is the maximum amount of connections per F-Secure Scanning and Reputation Server (SRS)?
A maximum of 130 virtual Windows workstations should be managed by one F-Secure Scanning and Reputation Server. Two instances of F-Secure Scanning and Reputation Server should be configured as primary in the F-Secure Client Security policy.
Article no: 000004854