Carbonblack sensor and Server Security causing BSOD during reboot
When both products, Server Security and CarbonBlack sensor, are installed on the same server, BSOD occurs on every reboot. The problem is related to Windows Firewall. Existence of our drivers/services increases the chance of an MS bug to appear. Possibly our services issue some specific network requests, which cause memory corruption in the Windows firewall engine (memory corruption goes very deep into MS code of the firewall). This is an essential bug in the MS engine (possibly even a security vulnerability if such memory corruption could be made on request). This has been already reported to Microsoft. The workaround/solution is to stop MS firewall before reboot or try to relax/change firewall rules on the server. More information about Carbon Black: https://www.carbonblack.com/
Article no: 000016167
The administrator receives the following alert from a server running Server Security and Microsoft SQL Server: "F-Secure Management Agent failed in an internal operation. Setting the policy variable 126.96.36.199.4.1.2188.8.131.52.20 (error=-510)" was not successful."
The server in question was hosting multiple instances for SQL Server 2016.
Due to a limitation in the current software, the internal table for storing "missing updates" cannot accept multiple identical rows and Software Updater was detecting a missing update on both instances for MS SQL Server. Consequently, adding the second missing patch to "missing updates" table failed with error -510: "Set result: your table contains multiple identical rows". A fix for this issue will be released later 2019 in Client Security version 14.20. Server Security will also inherit the fix, once F.Secure releases a new version.
Article no: 000016213
F-Secure Server Security Premium 12.11 and 12.12 display incorrect versions in Policy Manger after being upgraded from F-Secure Server Security Standard Policy Manager is reporting two different versions of Server Security installations on Installed products summary
This issue is a known bug. Contact F-Secure Support here so we can provide you with the hotfix to resolve this issue.
Article no: 000003462