cancel
Showing results for 
Search instead for 
Did you mean: 

Computer Protection change log

F-Secure

Release 18.17 - availability starting 7.11.2018

A new version of the endpoint clients is made available. The release of clients makes available these products to install with an appropriate subscription key:

  •     Computer Protection 18.17 (4.00.5640)
  •     Computer Protection Premium 18.17 (4.00.5640)
  •     Computer Protection & Rapid Detection and Response 18.17 (4.00.5640)
  •     Computer Protection Premium & Rapid Detection and Response 18.17 (4.00.5640)

These are available on all environments, and we have started growing the availability from EU-SMI reaching all environments tomorrow. The clients get automatically upgraded for clients in the 18.1x series of Computer Protection clients, without a reboot.

 

We continue upgrading clients with old versions to the latest through channel on all environments except PSB3. PSB3 upgrades will start the channel upgrade availability on November 21st as per current plans. Computer Protection 18.5 will soon be fully replaced and any customers migrating from WKS12 to Computer Protection get into our latest version automatically.  

This release introduces:

  • Under the hood change into latest generation of Software Updater Engine. We expect small improvements in performance, with functionality remaining on the existing level.
  • Improved safety mechanisms on Firewall, preventing locking administrators out from computers especially in cases where the Network Isolation functionality is used in different network topologies.
  • Fixes to installation flows, in particular to a case where Windows account names include spaces and where firewall defined in AD changes due to installation of Computer Protection.

Should you notice anything worth a mention or question, we always welcome your feedback.
 

On behalf of the R&D team working on the endpoint Windows clients,

    Maaret

Highlighted
Superuser

Re: Release 18.17 - availability starting 7.11.2018

Dear F-Secure,

A hungarian educational customer reports that F-Secure endpoint protection (at least the PSB CP 18.x versions) have a problem on computers with Virtualbox installed. That hypervisor software creates a virtual network card, which allegedly has the exact same MAC address on every computer.

F-Secure PSB CP 18 apparently prioritizes that "virtual" MAC address for its identifier, instead of the physical network card. Because of that choice non-unique identifier related problems may emerge, e.g. "rotation of endpoints" in the PSB admin webportal view.

Sysadmin must manually configure the generation and use of "random computer identifiers" for F-Secure endpoints to work around that problem. Please investigate this report and if necessary, implement the corresponding fixes! (E.g. the known wrong MAC addresses belonging to various hyper-virtualization software could be black-listed for unique ID use by factory defult or something like that.)

 

Thanks in advance, Yours Sincerely: Tamas Feher, Hungary.

F-Secure

Re: Release 18.17 - availability starting 7.11.2018

Hi Tamas,

 

with the new generation of clients, we are not using the MAC address in communication as was the case in the WKS12 generation. However, if your customers are installing on the image and then creating distribution copies, you could check our instructions on how to install on a clone image.

 

We'd be happy to look into your customer's problem in more detail if this does not help solve it.

 

    Maaret

 

 

F-Secure

Release 18.18 - availability starting 14.12.2018

A new version of the endpoint clients is made available. The release of clients makes available these products to install with an appropriate subscription key:

 

  • Computer Protection 18.18 (4.00.6253)
  • Computer Protection Premium 18.18 (4.00.6253)
  • Computer Protection & Rapid Detection and Response 18.18 (4.00.6253)
  • Computer Protection Premium & Rapid Detection and Response 18.18 (4.00.6253)

The clients get automatically upgraded for clients in the 18.1x series of Computer Protection clients, without a reboot.

 

This release introduces:

  • Fixes and improvements. Installation flows, sending status information, online scanning, Firewall status showing in the user interface, Software Updater
  • Under the hood improvements (preparing to enable customizing and localizing) to new user interfaces: Isolation, RDR standalone user interface

Should you notice anything worth a mention or question, we always welcome your feedback.
 
On behalf of the R&D team working on the endpoint Windows clients,

    Maaret

 

F-Secure

Release 19.1 - availability starting 23.1.2019

A new version of the endpoint clients is made available. The release of clients makes available these products to install with an appropriate subscription key:

 

  • Computer Protection 19.1 (4.01.168)
  • Computer Protection Premium 19.1 (4.01.168)
  • Computer Protection & Rapid Detection and Response 19.1 (4.01.168)
  • Computer Protection Premium & Rapid Detection and Response 19.1 (4.01.168)

The clients get automatically upgraded for clients in the 18.1x series of Computer Protection clients, without a reboot.

 

This release introduces:

  • Fixes. Showing unnecessary reboot dialog, Running Windows Defender
  • Improvements. Software Updater flyer on reboot, starting scheduled scan if computer is off on the timer
  • Ability to sidegrade Workstation 12 and other F-Secure products in MSI installations

 

Should you notice anything worth a mention or question, we always welcome your feedback.
 
On behalf of the R&D team working on the endpoint Windows clients,

    Maaret

F-Secure

Release 19.2 - availability starting 5.3.2019

A new version of the endpoint clients is made available. The release of clients makes available these products to install with an appropriate subscription key:

 

  • Computer Protection 19.2 (4.02.1067)
  • Computer Protection Premium 19.2 (4.02.1067)
  • Computer Protection & Rapid Detection and Response 19.2 (4.02.1067)
  • Computer Protection Premium & Rapid Detection and Response 19.2 (4.02.1067)

The clients get automatically upgraded, generally without a reboot.

 

NOTE: For this release you will see a need of reboot in a special case. If at time of installing there is an application running that uses .NET that we are upgrading to version 4.7.2, a reboot is needed. This reboot is not asked visibly, but only through the downloads list with the PSB module status "Reboot needed". The version 19.1 will continue to be fully operational while the reboot is pending.

 

Also, a fraction percentage of our installed base will see PSB module status "Will try again". This means that something blocked us from upgrading .NET to version 4.7.2, usually the reason being that the computer is running an older version of e.g. Windows 10 where Microsoft is not supporting this version. In this case, check that .NET 4.7.2 is supported on the Windows version the computer is running and if the status remains, please reach out to us. Also in this case, the version 19.1 will continue to be fully operational.

 

This release introduces:

  • New user interface using .NET - first changed is the About box.
  • PSB managed remote F-Secure diagnostics. Admins can now request a diagnostic tool run from the portal to initiate asking permission for it on the endpoint. With permission, the file is made directly available for F-Secure with an identifier the admins can use in their support contacts.
  • First-level properties for WMI. To support RMM tool integration, we added WMI properties and simplified the interface for more straighforward integration. We now support RMM with Kasaya and will add documentation on it to  make it more widely accessible.
  • Fixes. Many enhancements on installation scenarios, software updater, browsing protection and remotely managed firewall. Crashes in components that happen silently.
  • Improvements. List of IP addresses for autoswitch rules so that you can define single rule for multiple addresses. WINS support for autoswitch rules.
  • Separate sidegrade package to run in MSI remote installations.

 

Should you notice anything worth a mention or question, we always welcome your feedback.
 
On behalf of the R&D team working on the endpoint Windows clients,

    Maaret