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

Unattended Install of PSBESS 12.10

Rec_OlliE
Rec_OlliE W/ Alumni Posts: 14 Security Scout

Greetings!

 

I'm installing PSBESS 12.10.280(to be exact) from our Pre-Installation script.

 

The problem seems to be that the installation actually never returns when I call from powershell: "Start-Process ....psbess1210.exe -Wait"

 

Older versions worked fine and returned after the installation.

 

I can fix this by stopping all F-Secure services and then killing FSLAUNCH.exe.

 

Installation continues fine after that.

 

Is this a bug or is there some new parameter that I missed?

 

EDIT: Tested this a bit and found out that killing process FSM32.EXE (Settings and Statistics) actually returns the installation Setup.exe and my installation script continues.

 

Sincerely,

Olli - Receptum Oy

Comments

  • Laksh
    Laksh W/ Alumni Posts: 237 Cybercrime Crusader

    Hi Olli,

     

    Just to understand better, is it considered working as expected if you stop the process FSM32.EXE? Was it the same behaviour with the before version?

     

    Or would you still like this to be checked with the product team so I can check further?

  • Rec_OlliE
    Rec_OlliE W/ Alumni Posts: 14 Security Scout

    Hey Laksh, thanks for replying.

     

    In the previous version the installation returned without doing anything special.

    With this new version it does for some reason hang the execution process id or something that "-Wait" parameters waits to return (some exit code I guess)

     

    And to actually answer your question: Yes, if I stop the FSM32.EXE it returns something back to powershell and the installation continues.

     

    -Olli

  • Laksh
    Laksh W/ Alumni Posts: 237 Cybercrime Crusader

    Hi Olli,

     

    Thanks for the quick response. If you are having any further issues with this, keep us updated in this thread and I will check that for you.

This discussion has been closed.