F-Secure Policy Manager 15.30 upgrade to WithSecurity Policy Manager 16.00

AkkuAnkkka313 · 2023-10-02T09:58:40+00:00

There was an error rendering this rich post.

I didn't find any guides for the upgrade process so is it even possible? Do I need to install new Policy Manager from scratch? The installer doesn't provide any upgrade possibilities and wiped off the F-Secure Policy Manager from the server without even asking me. I reverted back to a snapshot which I took before the upgrade attempt and was quite baffled by the installers actions.

Find more posts tagged with

Accepted answers

All comments

AleksandrG

Most probably fixed version will be published next week.

BTW, you can follow the status page, which has the up-to-date information: https://status.withsecure.com/

jussis

@AleksandrG Do you have any estimation when the fixed installation package is going to be released?

AkkuAnkkka313

Thank you for your answers. We'll wait until fixed installation package is released and then will upgrade the Policy Manager.

AleksandrG

Hi @AkkuAnkkka313, there is an option to override installation directory with the 'TARGETDIR' MSI argument:

msiexec /i policy-manager.msi TARGETDIR=E:\CustomDirectory

This option won't help with the mentioned issue and you still need to follow proposed workaround to migrate data from the non-default installation path manually.

Regards,
Aleksandr

JamesC

Hi @AkkuAnkkka313 our sincere apologies that you are not able to upgrade Policy Manager 16.00 on D:\ drive.

We are are aware of the issue and is currently investigating at high priority. You can subscribe and monitor the incident status on https://status.withsecure.com/

As a current workaround, we suggest to use the resolution from the article you shared.

AkkuAnkkka313

Okay so there is a bug in the upgrade installation if the old Policy Manager is installed anywhere else than c:\program files…

https://community.withsecure.com/en/kb/articles/31216-policy-manager-server-upgrade-to-16-00-fails-if-previous-15-version-installation-is-not-on-default-c-drive

But we need to be able to install the Policy Manager to D-drive because C-drive is dedicated only to Windows installation and nothing else. Is this going to be fixed too that we can choose where to install the new Policy Manager?