To stay updated on your favorite discussions, please create an account or log in. Then, click the Bookmark icon to subscribe and receive notifications.

How to download Policy Manager 16.02?

Michalb1
Michalb1 Member Posts: 2 Security Scout

Hello. We got instructions to upgrade F-Secure Policy Manger 15.11 to WithSecure 16.03 which is the one available version on the WithSecure page. However upgrading to policy manager console we cannot connect to the server.
Want to try with older version but can't download it.
Thanks, Michal

Answers

  • Sethu Laks
    Sethu Laks Staff, Moderator Posts: 288 W/ Moderator
    edited November 7

    Hi @Michalb1

    Thank you for reaching out the WithSecure Community,

    You can download PM 16.02 from the following link:https://download.withsecure.com/corpro/pm/pm16.02/wspm-windows-msi-16.02.98349.msi

    However, we recommend upgrading to version 16.03. This update will help our R&D team investigate any issues more efficiently and deploy fixes if necessary.

    Troubleshooting Policy Manager Console 16.x Connection Issues:

    Several factors can prevent the Policy Manager Console from connecting to the Policy Manager Server. Below are steps to resolve two common issues.

    Issue 1: Port Conflict

    If the Policy Manager Console 16 won't start, check if any required ports are in use:

    1. Verify that the listening ports configured for Policy Manager Server are open and available.
    2. Look for errors in the log file located at: C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Console\log\Administrator.error
      • Example error:Could not connect to HTTP invoker remote service at [https://localhost:8080/fspms/remoting/…..]
    3. If you confirm a port conflict, you can update via registry:
      • Stop the Policy Manager Server service with the command:net stop wspms
      • Open regedit and navigate to:[HKEY_LOCAL_MACHINE\SOFTWARE\WithSecure\Policy Manager\Policy Manager Server]
      • Check that ports are set correctly for AdminPort.. (8080), HttpPortNum (80), HttpsPortNum (443), and WRPortNum (8081).
      • Start the service again:net start wspms

    Note: If using custom ports, ensure they are open in the firewall.

    Issue 2: Server Process Crash during Re-indexing

    1. Check for crash logs in:
      • C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\log\fspms-service.log.
      • C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\log\fspms-stderrout.log
      • If you see "Re-indexing software updates..." in fspms-stderrout.log, it indicates the server is re-indexing, which may take up to an hour. Let the server run to complete this process.

    Following these steps should help resolve the connection issues.

    Best regards,
    Sethu
    Community Moderator | Technical Support Engineer
    WithSecure™ https://www.withsecure.com/en/home

  • Michalb1
    Michalb1 Member Posts: 2 Security Scout

    Hello Sethu,

    Thanks for your feedback but let me add few comments since I can't do all tests you mentioned.

    Our configuration contains:
    - 5 F-Secure servers where we have Policy Manager (Console + Server) installed in version 15.11
    - 3 remote JumpBozes where Policy Manager Console (only) is installed (version 15.11) to mange remotely those 5 F-Secure server over 8080 port.

    Our company has 3rd party support for F-Secure and they advised all steps for upgrade to v16.x.

    So first I upgraded Policy Manager Console on one of the jumpboxes using this command - "msiexec /i
    policy-manager.msi NOSERVER=true".
    After that I was not able to connect to any server in version 15.11 remotely.
    I did the same upgrade on one of the F-SEcure server upgrading only console and have the same result. Policy manager server was not upgraded yet.

    I just received information from them that probably WithSecure Policy Manager Console 16.03 cannot manage server in version 15.11.
    Could you please confirm that?

    Thank you,

    Michal

  • Sethu Laks
    Sethu Laks Staff, Moderator Posts: 288 W/ Moderator

    Hi @Michalb1

    Thanks for providing us the additional information,

    Yes, you need to use both Policy Manager Server and Policy Manager Console version 16.x for them to connect and work correctly.

Categories