As we have previously announced, due to infrastructure changes needed as part of our separation from F-Secure, the use of F-Secure branded clients is deprecated.<\/p>\n
The clients WILL stop working at the end of 2024, and will provide no protection at all.<\/p>\n
Customers using these deprecated clients MUST<\/strong> upgrade them to WithSecure branded versions before this date to ensure continued protection.<\/p>\n IMPORTANT NOTE:<\/strong> There is no need to purchase any new products. Your existing subscription keys continue to work for WithSecure-branded clients!<\/p>\n You may be using an operating system that is no longer supported by WithSecure Elements. Please note that the following versions are supported:<\/p>\n Microsoft Windows<\/strong>: Windows 10 and Windows 11<\/p>\n Microsoft Windows Server<\/strong>: Windows Server 2016, Windows Server 2019, Windows Server 2022<\/p>\n macOS<\/strong>: macOS 14 “Sonoma”, macOS 13 “Ventura”, macOS 12 “Monterey”<\/p>\n iOS<\/strong>: iOS 15 or later<\/p>\n Android<\/strong>: Android 11 and later<\/p>\n For Microsoft Windows, please note that Microsoft have changed the certificate they require security software vendors to use for signing software. The new certificate was added to Windows via software updates 3 years ago so this only affects computers that are at an older patch level. If a device does not support the ACS certificate it will show a critical protection status, and the EPP dashboard issue list contains an entry linking to affected devices. You can find out more details about this in our dedicated article<\/a>.<\/p>\n WithSecure Elements has functionality which will allow some client updates to be deferred. This is not intended to be used to delay the updates indefinitely. The easiest way to verify this is:<\/p>\n Go to the device list<\/p>\n Set a filter for \u201dstatus updated\u201d -> within the last 7 days<\/p>\n Set a filter for \u201cclient version\u201d -> not equals 24.4 or 24.5<\/p>\n Save the view from the view menu with a name such as \u201cunsupported clients\u201d<\/p>\n You can navigate to view profile settings by clicking on the assigned profile, then check the \u201cautomated tasks\u201d section to verify if there is a task delaying updates. If there is, change the schedule to match your next maintenance window<\/p>\n If the client requested a reboot after initial install but it was not done, it is possible that the client is not checking for updates. Using the view created above, open device details, navigate to the \u201cElements Agent update history\u201d section and expand it. Check the status next to \u201cOneclient PSB\u201d if it is requesting a reboot.<\/p>\n Elements clients will check for available disk space before trying to update. If your device has less space than needed for the update, the update is not applied. You can identify devices that have insufficient disk space from the EPP dashboards issue-list. Clear some space on the disk by deleting old content or moving it to another drive, and reboot the device. When the client starts again it will check for space, and if there is enough then the update will proceed.<\/p>\n WithSecure Elements Clients require access to some very important servers that we host. If connections are not possible, in some cases no update is detected, and this will keep the device at an older version. To identify devices that might have problems with connectivity navigate to the device list, click on the 3-bar icon next to device search, filter available columns for \u201cconnectivity\u201d and select the fields \u201cconnectivity status\u201d and \u201cconnections failing always\u201d. This will add these new columns to the device list. If you filter the list to only show devices with \u201cdisconnected\u201d connectivity status it will make it easy to review which domains they have issues connecting to and verify your firewall or proxy configurations to allow them. Please check this community article<\/a> for a list of required connections.<\/p>\n","protected":false},"excerpt":{"rendered":" As we have previously announced, due to infrastructure changes needed as part of our separation from F-Secure, the use of F-Secure branded clients is deprecated. The clients WILL stop working…<\/p>\n","protected":false},"template":"","announcement_category":[142],"class_list":["post-7039","announcement","type-announcement","status-publish","hentry"],"acf":{"source_system":"vanilla-import","import_hash":"0fea7e38bb393fa374f8292887d17d698fab2f32","vanilla_article_id":31410,"legacy_author":"AndyF_WS","vanilla_url":"https:\/\/community.withsecure.com\/announcements-en\/kb\/articles\/31410-withsecure-elements-and-f-secure-branded-clients-end-of-support-2024-12-31","vanilla_category_id":142,"machine_translated":false},"_links":{"self":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/announcement\/7039","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/announcement"}],"about":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/types\/announcement"}],"version-history":[{"count":1,"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/announcement\/7039\/revisions"}],"predecessor-version":[{"id":8448,"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/announcement\/7039\/revisions\/8448"}],"wp:attachment":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/media?parent=7039"}],"wp:term":[{"taxonomy":"announcement_category","embeddable":true,"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/announcement_category?post=7039"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Possible reasons why the clients have not been updated automatically<\/strong><\/h2>\n
Unsupported operating system<\/strong><\/h3>\n
Customer used our functionality to delay when updates happen<\/strong><\/h3>\n
Customer has some clients that requested a reboot after first installation and the reboot was never done<\/strong><\/h3>\n
Disk space is really low<\/strong><\/h3>\n
Firewall prevents connection to an important network endpoint<\/strong><\/h3>\n