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

F-Secure Policy Manager 14 Console Cannot Export Package Error

mas2
mas2 Posts: 11 Security Scout
in Business Suite

Hello!

Be grateful for some help with this error. Have tried repeatedly to export the installation package on two separate machines running Windows 10 Pro 64 bit but ends up with the same error message consistently. There are no other issues with FSPM 14 apart from this.

 

Machines are fully patched and secured.

Many thanks in advance!

 

cannotexportpackage.jpg

Comments

  • GeminiMDZ
    GeminiMDZ Posts: 7 Security Scout

    I've stumbled across the same problem. I managed to export package only on machine that have Policy Manager Server installed.

  • JensB
    JensB Posts: 5 Security Scout

    Same problem here, even on the management server itself :-(

     

     

  • JensB
    JensB Posts: 5 Security Scout

    The problem at our site is only seen, when exporting fscs-14.00.4586.jar.

    Exporting the fscspr-13.11.110.jar works fine, maybe 14.00 pakage is the problem?

  • Johnny_M
    Johnny_M Posts: 5 Security Scout

    Same problem here.

  • mas2
    mas2 Posts: 11 Security Scout

    Thanks for the replies. Yes, the Policy Manager Server is also installed but no luck. The same machines had no problems with FSPM 13 and exporting FSCS 13 jar files. 

  • MJ-perComp
    MJ-perComp Posts: 669 Firewall Master

    Hi all,

    as PMC tries to write to ProgramData
    could you confirm if the account running the PMC has / has not local AdminRights?

    M.

  • JensB
    JensB Posts: 5 Security Scout

    Hi

     

    The user I'm using, is domain admins on the server running Policy Manager Console/Server, and I have no trouble creating files i the ProgramData folder.

     

  • sebar25
    sebar25 Posts: 1 Security Scout

    Run as administrator works for me.

  • MJ-perComp
    MJ-perComp Posts: 669 Firewall Master

    Thanks for confirmation.
    so the workaround is "run as Administrator"

    As managing F-Secure should NOT require local admin rights this needs a change in future, but installing on remote hosts does require local admin rights on the target system, so most F-Secure Administrators are domain admins anyway.

     

    Is that a problem for someone?

     

  • JensB
    JensB Posts: 5 Security Scout

    It also works for me Smiley Happy

     

  • mas2
    mas2 Posts: 11 Security Scout

    The solution elegant and worked like a charm for me too. Thank you all very much!

  • Johnny_M
    Johnny_M Posts: 5 Security Scout

    All working for me too. Thanks

     

  • aimutch
    aimutch Member Posts: 28 Junior Protector

    Selecting "Run as Administrator" worked for me as well. 

  • MBeck
    MBeck Posts: 1 Security Scout
    works
This discussion has been closed.

Categories