Unfortunately, information in your posts is not enough to figure out why this command doesn't work properly in your case. Please, contact support. We'll need more information for investigation.
Thanks in advance,
You know what? I called F-secure support three times and everytime my call was dropped, so I gave up.
I have a F-secure support contact at ATEA Sweden but he cant help and reffers to F-secure Support.
Sorry to hear that you couldn't reach our support by phone.
Can you confirm the number you use?
This page show the contact number and service hours.
You can always send us a request through our webform here.
Where can I get this CS 12.10 Beta3? Is it a .JAR file that I can build with my policys from Policy Manager and finally export a working MSI from? Trying to download from your site only give me the base CS 12.00.
One thing that odd, my fist question aboute CS 12.00 not installing proppertly... I've found that sometimes if I let my develop VM idle it will start to install all the products on the machine. Before with CS 11 this install was made instantly after running MSI. Notice sometimes... I've left it over the weekend and still just having the one F-secure post in Programs and features.
Is it so that you redesigned the MSI to just drop a policy agent on the machine that later on continue the real installation of all products? (As I only see "F-Secure Client Security 12.00" in Programs and features at a beginning.)
If that's the case, is there a switch to force full install immediately? I'm not so happy with removing our old CS 11, and then let the agent decide when it's time to install CS12 leaving our machines unprotected during that time.
Or am I doing something wrong?
Running on Windows 7 x64.
Regarding MSI installation logic. Since CS 11.61 there was a change. MSI itself only launches the installation and completes, while installation is continuing in the background. In CS 12.10 the behavior by default returned to the same we had in versions 11.60 and earlier, and you can provide additional options in command line.
Note that for MSI installation having a single entry in Programs and features is by design. All the features are installed, and you can check this in Policy Manager Console.
Here are the links for CS 12.10 Beta3 Premium/Standard jar and release notes:
You will also need a new PM version 12.10:
Thank's for the clarification on the installing process. Could be a problem with the uninstall from MSI that makes my installs hang intermittent. I've found another thread (Silent-uninstall-F-Secure-PSP) with a solution to run the uninstallation tool instead. Seams to do the trick as now I can reproduce the same results every time and continue the deploy process with successful results.
If I'm going to try the CS 12.10 Beta3, and run this new PM 12.10 Beta3, the PM wont collide with our current client's running on CS 11.61?
Several customers complain that the F-Secure PSB remote installation tool is so ancient, it is unable to properly support Active Directory domain data read-out, when the server is Win 2012 R2 or newer. They only receive a remote API code 2 127 (2127?) error message.
Yours Sincerely: Tamas Feher, 2F 2000 Kft., Hungary.
This topic has been closed due to inactivity. If you would like to discuss this topic further, please start a new post.
You can reference this topic in your post by adding this link: