Header Header Header English Suomi Svenska Deutsch Français Italiano Japanese

  
 
home
support issues.gif
 virus-probs.gif
documentation
downloads
Online Services
contact us
home users

Frequently Asked Questions

Q: Come è possibile eseguire il backup di file Policy Manager Server critici?
A:

Per eseguire il backup di Policy Manager Server, procedere come descritto di seguito:

  1. Fare clic su Start, quindi selezionare Esegui.
  2. Digitare 'cmd' nella casella Apri, quindi fare clic su OK. Viene visualizzata una finestra che richiede l'immissione del comando.
  3. Digitare 'net stop fsma' e premere Invio, quindi digitare 'net stop fspm' e premere nuovamente Invio. Questa operazione consente di interrompere tutti i processi F-Secure in esecuzione sul server.
  4. Eseguire il backup dell'intera directory di comunicazione e delle chiavi amministratore, quindi salvarle in una cartella protetta da cui è possibile riutilizzarle, se necessario:
    • la directory di comunicazione (CommDir contiene le impostazioni del Policy Manager Server) si trova generalmente in C:\Program Files\F-Secure\Management Server5\CommDir\
    • le chiavi amministratore (admin.pub e admin.prv), utilizzate per confermare che i client che comunicano con il server sono affidabili, si trovano generalmente in C:\Program Files\F-Secure\Administrator\
  5. Riavviare i processi F-Secure sul server digitando 'net start fsma' e 'net start fspm' nella finestra di immissione dei comandi.
Q: What is F-Secure's statement on F-Secure Policy Manager Server "fsmsh.dll" path disclosure issue reported as 'minor' or 'not-critical' by some security advisories?
A: F-Secure Corporation is aware of a path disclosure issue "fsmsh.dll" that affects F-Secure Policy Manager Server 5.61 (Windows and Linux) and earlier versions. This issue makes it possible for a remote user to find out the installation path of the product.

F-Secure Corporation is not aware of any scenarios where disclosure of this info would lower the security of the system. This info is also in most cases the default installation directory that can be guessed easily by any user even without this issue. As the path disclosure issue does not give attackers any significant benefit, F-Secure will fix the issue in the next standard release rather than in a hotfix unless there are indications that this issue can be useful for an attacker.

Q: Where are the log files, configuration files and Communication Directory located for F-Secure Policy Manager Server 5.60?
A:

The log files are located in: "F-Secure\Management Server 5\logs"

The configuration files are in: "F-Secure\Management Server 5\conf"

And the F-Secure Policy Manager Server Communication Directory is located at: "F-Secure\Management Server 5\commdir"

Q: What are the supported OS for using PM 5.60
A:

PM Console 5.60 runs on

  • Windows NT/2000/XP/2003

    PM Server 5.60 runs on

  • Windows NT/2000/2003
  • RedHat Enterprise Linux ES 3.0
  • SuSE Linux 9.0

    F-Secure Anti-Virus Proxy runs on

  • Windows NT/2000/XP/2003
  • Q: What is the Web Reporting Tool in Policy Manager 5.60?
    A:

    It is a component of the recently released Policy Manager 5.60 which makes possible to

  • Show graphically the Top 10 infections / infected hosts / attacks
  • Show graphics about OS used / F-Secure softwares in use
  • Report about Virus definition versions
  • Show the trend report of alerts per month
  • Show Virus outbreaks
  • Create long term trend reports based on historical data

    Web Reporting is integrated with the Policy Manager Server. It is used through web browser. The reports can viewed locally and remotely, easily with your normal web browser.

  • Q: What's new in Policy Manager 5.60?
    A: Policy Manager 5.60 features
  • a Web Reporting Tool
  • Automatic rule based host importing
  • Automatic domain refresh in read only mode
  • Full Windows Server 2003 Automatic Update Agent support
  • German and French localizations
  • Q: I have lost the management keys, what should I do?
    A:

    If you lose the private key of the Policy Manager Console(admin.prv), you have to generate a new management keypair (admin.pub and admin.prv) and re-install the centrally managed applications to all hosts using the new public key.

    If you lose the public key (admin.pub), you can recover it either from the Policy Manager Server (\commdir\fsa directory) or from a centrally managed host (\F-Secure\Common directory).

    Q: I need to change the address of the Policy Manager Server, how should I do it?
    A: You need to be careful when doing this. You must specify the new address to all managed hosts, distribute the policy and make sure that all hosts have received the new setting. Then you can change the address of the Policy Manager Server. If a host has not received the new address before you change it, the host will not be able to communicate with the Policy Manager Server.
    Q: SuSE Linux segmentation fault problems with Policy Manager Server
    A: These Policy Manager Server segmentation faults are cause by the combatibility problems with glibc library and with libraries that are used by glibc library itself. Policy Manager Server is statically linked to minimize the combatibility problems, but there are still some left inside glibc. Dynamic linking of Policy Manager Server could solve some of these problems, but then we could not use same binaries on several different Linux distributions like RedHat, SuSE, Debian, Mandrake, TurboLinux and so on (most of these are neither officially supported).

    There are 2 different segmentation faults related to Policy Manager Server:

  • Policy Manager Server segfaults immediately when it is started. You do not even get any error log at this case. This is caused by full incombatibility with Policy Manager Server and glibc version.

  • Policy Manager Server child processes segfault when they are started (forked). You get "Segmentation fault (11)" lines to error log. This is caused always by problem with some other library that glibc is using. See e.g. the LDAP case.

    SuSE 8.0 (fully supported platform):
  • Policy Manager Server 5.50 is fully tested with original SuSE 8.0 and glibc 2.2.5-38.
  • Policy Manager Server 5.50 is tried out succesfully with SuSE 8.0 and glibc 2.2.5-177 (currently latest patch for SuSE 8.0).
  • We have not received complains about Policy Manager Server 5.50 not working on SuSE 8.0.

    SuSE 8.1 (not officially supported):
  • Policy Manager Server 5.50 does notwork with original SuSE 8.1 release.
  • Policy Manager Server 5.50 is tried out succesfully with SuSE 8.1 and glibc 2.2.5-177 (currently latest glibc patch for SuSE 8.1 for i586).
  • Policy Manager Server 5.50 is tried out succesfully with SuSE 8.1 and glibc 2.2.5-184 (currently latest glibc patch for SuSE 8.1 for i686).

    We have received several complains from customers using exact same glibc version, but we cannot reproduce them in our lab. As we cannot easily reproduce these in our lab and this is not our officially supported platform, we are not actively searching for a solution. What you can do is to try out different glibc versions and see if it works or then you could downgrade to SuSE 8.0 or upgrade to SuSE 8.2.

    SuSE 8.2 (not officially supported):
  • Policy Manager Server 5.50 is tried out succesfully with original SuSE 8.2 and glibc 2.3.2-9 (there aren't any patch available to SuSE 8.2 glibc).
  • We have not received complains about Policy Manager Server 5.50 not working on SuSE 8.2.

    Policy Manager Server 5.11 is tried out succesfully with original SuSE 8.1. Policy Manager Server 5.11 does not work with SuSE 8.2.
  • Q: Can I install F-Secure Anti-Virus Proxy on Windows 2003 Server?
    A: F-Secure Anti-Virus Proxy 1.0 is not supported on Windows 2003 Server platform. The official support will be available in second half of 2003.

    Although the current version is not supported on Windows 2003 Server, the product can be installed on Windows 2003 Server by following these steps:

    • Right-click FSAV Proxy Setup.exe icon in explorer and select Properties.
    • Go to Compatibility page.
    • Check 'Run this program in compatibility mode for'.
    • In the list below, select 'Windows 2000'.
    • Start Setup.exe and install the product.
    Q: Can I install Policy Manager Server and Console to same computer?
    A: Yes, you can.
    Q: Can I install more than one Policy Manager Console for one Policy Manager Server?
    A: Yes. You just have to make sure that after installation of the new Policy Manager Console, you have to copy ADMIN.PUB and ADMIN.PRV files from the original Console before you launch the new console for the first time.
    Q: Do I have to use a Microsoft operating system for Policy Manager Server?
    A: No, it is not required as Policy Manager Server is available for the following platforms: Windows NT 4.0 with Service Pack 6, Windows 2000, Windows Server 2003 and Linux.
    Q: Do I really have to use Server operating system? Isn't the workstation version enough?
    A: You have to use Server operating system for Policy Manager Server because as it says in the Microsoft operating system license, it is not legal to use the Workstation version for server use.
    Q: Can I install Policy Manager Console to Win95, Win98 or WinME operating systems?
    A: Yes you can, but the push installation features are not available on Windows 95/98/ME. Push installations are supported only on Windows NT4/2000/XP. Policy based remote installation features work on all Windows platforms.