Business Suite

Sort by:
Issue: Does Policy Manager Proxy also proxy Software Update installation packages? Resolution: Yes, Policy Manager Proxy also proxies Software Updater installation packages. You can find more information, here.  Article no: 000017850
View full article
Issue: How to setup the silent installation for Policy Manager Proxy 14.20 User is creating a policy-based upgrade and needs to export installer msi for rollout via group policies Resolution: Clean installations: For Windows Open Policy Manager Console and create temporary user with full access permissions for the root domain Download Policy Manager Proxy installer: fspm-14.10.88509.exe as an example Extract Policy Manager Proxy setup executable content. For 14.00 and older - via any archive manager, for 14.10 start the executable and grab all the content from temporary directory at root level of system drive Transfer admin.pub from Policy Manager to the extracted content Edit prodsett.ini in the same directory: uncomment and specify values for all properties in the section "F-Secure PM Proxy" Use user credentials created at first step for UpstreamPmUserName and UpstreamPmUserPwd properties Run "setup.exe /silent" at target host for 14.00 and older, starting from 14.10 executable is called like fspmp-14.10.88509-rtm.exe, so have to run "fspmp-14.10.88509-rtm.exe /silent" Remove user created at first step For Linux Open Policy Manager Console and create temporary user with full access permissions for the root domain Download installer: fspmp-14.10.88509-1.x86_64.rpm as an example Put admin.pub from PM to the dir with installer Create shell script with name like pmp.sh and following content: yum -y update libstdc++ yum -y install libstdc++.i686 rpm -i fspmp-14.10.88509-1.x86_64.rpm /opt/f-secure/fspms/bin/fspms-config << PMPCONFIG PM address PM port (usually 443) ./admin.pub PMP http port to be used (usually 80) PMP httpS port to be used (usually 443) PM admin username (created at first step) PM admin password (created at first step) PMPCONFIG Run the script: “./pmp.sh”. Remove user created at first step. Same things with Debian/Ubuntu, but use apt and dpkg instead, so sh script will look like: apt -y upgrade libstdc++6: apt -y install libstdc++6:i386 dpkg -i fspmp_14.10.88509_amd64.deb /opt/f-secure/fspms/bin/fspms-config << PMPCONFIG PM address PM port (usually 443) ./admin.pub PMP http port to be used (usually 80) PMP httpS port to be used (usually 443) PM admin username (created at first step) PM admin password (created at first step) PMPCONFIG After the script run, if everything is ok, PMP host should appear in PMC.   Policy Manager Proxy upgrades: For upgrades, as there is not need to configure PMP and generate certificates enough to just upgrade the build. For Windows: Extract PMP executable content via any archive manager Run "setup.exe /silent" For Linux: rpm -U fspmp-14.10.88509-1.x86_64.rpm dpkg -i fspmp_14.10.88509_amd64.deb Article no: 000016979
View full article
Issue: When using image files to distribute product installations, how can I reset the host UID for Policy Manager Proxy to prevent duplicate hosts appearing in Policy Manager? Resolution: If you use image files to distribute product installations, you need to make sure that there are no unique ID conflicts. For Policy Manager Proxy this can be prevented by following the steps below: Stop F-Secure Policy Manager Server service:  Linux: [/etc/init.d/fspms stop] Windows: [net stop fsms] Remove following two files: Linux: /var/opt/f-secure/fspms/data/h2db/fspms.h2.db /var/opt/f-secure/fspms/data/fspms.jks Windows: <F-Secure Installation Folder>\Management Server 5\data\h2db\fspms.h2.db <F-Secure Installation Folder>\Management Server 5\data\fspms.jks Use fspmp-enroll-tls-certificate script to generate proxy node certificate. Run the script and authenticate yourself as root administrator of the Master Policy Manager: Linux: /opt/f-secure/fspms/bin/fspmp-enroll-tls-certificate Windows: <F-Secure Installation Folder>/Management Server 5/bin/fspmp-enroll-tls-certificate.bat Start F-Secure Policy Manager Server service: Linux: [/etc/init.d/fspms start] Windows: [net start fsms]   Article no: 000016987
View full article
The following steps describe Policy Manager Proxy node installation for both Windows and Linux.
View full article
F-Secure has released a new generation engine for one of our core scanning engines, which, at F-Secure, we call Capricorn. The engine change brings...
View full article
Issue: Clients are not able to get updates from the Policy Manager server Virus definitions shows later than the Policy Manager is Serving Update server is shown as wait.pmp-selector.local Policy Manager shows that Client Security is still in the old version even though on the client it is the newer version Resolution: The update server is shown as wait.pmp-selector.local until the client has successfully connected to the Policy Manager Server for the first time after the upgrade or installation. This is an indication that there is a connectivity issue between the clients and the Policy Manager server. First, check that you have set the correct Policy Manager Server address when exporting the installation file. You can check if the address is correct and if the HTTP connection works by opening a web browser on a client and then entering the Policy Manager Server address and the HTTP port in the address field.  Example: 10.132.2.19:80  Client Security 13 and earlier versions supported fallback to using HTTP connection if HTTPS did not work. Please check that both the HTTP and HTTPS ports are open in the firewall on the Policy Manager Server. By default Policy Manager listens to HTTP port 80 and HTTPS port 443, but these can be changed during installation.  Check that you have entered the correct Policy Manager Server address, HTTP port and HTTPS port when creating the installation file. If you have used the wrong address or ports when creating the installation file, you will need to reinstall the product with a new installation file with the correct settings.    If you are using Policy Manager Proxy in your environment, try these steps: Make sure that Policy Manager proxy servers are updated to 14 versions For Client Security 14 clients HTTPS connection support is required and for versions 13 and earlier it was not "Allow fallback" is not mandatory if everything is configured properly If you are not sure if it is configured properly, allow the option Fall back to Policy Manager Proxy which can be found under Automatic Update Agent in Policy Manager Console. If you cannot find an issue with your configuration, open a support request and submit an FSDiag diagnostic file from the Policy Manager Server and one of the affected client for further analysis and troubleshooting. Article no: 000009396
View full article
Issue: I am unable to have connectivity for my computer running a Business Suite product. We are using WPAD (Web Proxy Auto-Discovery protocol) to deploy http proxy server settings. Does Business Suite support WPAD for http proxy setting deployment? Resolution: WPAD is not officially tested nor supported by the Business Suite products, including Policy Manager. Article no: 000010593
View full article