F-Secure client 14.10 push - removing previous version 13.x

hi guys,
I used our FSPM 14.20.88937 to push Client Security Premium 14.10 to our laptops.
The "uninstall previous version if necessary" checkbox was checked.
As a result, we're now seeing two different versions (the new one I pushed and the old 13.x version).
In the systray I can see one F-Secure client icon and when I click this I can see it's the new 14.10.
The management server is correct.
However, some issues:
- the client still keeps connecting to the wrong (old) management server. I presume it's the old 13.x client that's doing this? So after the push, I'm seeing 'installation succesful' on the new FSPM server, but after a while, that client is again in the 'pending' list of the old FSPM server.
- is there a way to uninstall the old 13.x clients from within the PM console for all laptops in bulk?
- I also noticed that the update server is the f-secure cloud server and not our management server. For other sites/locations, I used the same install package and the update server on the clients is correctly pointing to the (new) local FSPM server.
Help would be welcome.
thanks,
Kris
Comments
-
This is a known and expected behavoir.
V14 needs to uninstall V13 and earlier before installing V14.
Other than befor it uses the ID that you defined (SMBIOS, WINS, Random UID).
I guess if you check the porperties of the old and the new entry you will see that the used IDs are different.
In status/centralized Management activate the ID-column and sort by it, then select the OLD IDs, right-click and select "choose from domaintree", finally delete those hosts.
OR simply wait a couple of days and the old ones will go disconnected. Configure to remove disconnected hosts after 40 days.1 1Like -
Hello Kris,
For the future updates, please, always use "upgrade" link under "Installed products summary" on the "Installation" tab of PM console.
This is a recommended way of upgrading product version to a new one.
Push is recommended for clean installations.
Best regards,
Vad
6 1Like -
hi,
sounds good, but I can't see/add an ID-column in 'status'/'centralized Management'?
Any idea why? Our PM is 14.20.
thanks,
Kris
-----------------
"In status/centralized Management activate the ID-column and sort by it, then select the OLD IDs, right-click and select "choose from domaintree", finally delete those hosts."
0 Like -
-
Hello,
The new FSPM 14.41 and FSCS 14.21 product versions include some bugfixes and they are now available for public download. Please make sure to use the latest versions:
https://www.f-secure.com/webclub
(Note: the F-Secure for Windows Servers 14.01 or higher product version isn't yet available, but it should be soon. Thus far the centralized management environment and the Windows workstation side protection has received a version update.)
Best Regards: Tamas Feher, Hungary.
0 Like -
That's why we sell product trainings. Understanding F-Secure's philosophy and why certain thing have been implemented in a specific way is imminent to get the best out of the best product!
Ask for a quote0 Like -
certainly not.
1) your question was not about uninstalling V13 first, but "why do systems now appear twice?".
2) As I wrote the training makes sense to understand the philosophy and techniques so that you less likely run into such a situation.
3) All steps you have to do, have already been explained in the previous posts (set auto removal of disconnected hosts to 40 days and wait).If you still want to remove the outdated hosts prior to those 40 days, you can used different methods
- use a smaller value than 40 days. eg. 10 and it will remove host that have not communicated in the last 10 days (but you might delete some hosts that are just "on vacation").
- in Status/Installed Software sort the hosts by version, mark them, right click and "select hosts in domain tree, then from menu choose edit/
- from host properties sort by unique ID, and you will see all the duplicates already marked with a "red X" (assumuning you have set 7 days for "considered disconnected" as above).
As we have no idea/screenshots about what you see we can only guess, but it should be easy for you to identify and remove the old hosts by any of the above methods.3 3Like