ak01

From my experience, this disappears when you restart the endpoint. However I only have such problems on a very few amount of computers (one or two computers during a long time). Maybe it also helps to close KES and start it. You should check if you have the latest KES version or to update it (current version is KES 12.2).

please try kavremover

habe ich auch schon umgesetzt, ohne Probleme für Exchange etc.

ich nutze auch gerne Richtlinienprofile, denn diese machen es sehr flexibel, spezifische Einstellungen (mit einer globalen Richtlinie) zu setzen. Man benötigt keine unterschiedl. Richtlinien mehr, eine pro Gerätetyp (Clients/Server) genügt (wenngleich man aber keine Einstellungen pro KSC Gruppe setzen kann, aber pro Tag/AD Gruppe/OU usw.). Danke für die ausführliche Beschreibung.

you should check the quarantine part of kes or on KSC (https://support.kaspersky.com/KSC/12/en-US/12430.htm)

man muss URLs angeben bzw. mit * Platzhalter arbeiten (siehe Beispiel):

Does the KES Adaptive Anomaly Control Module help to block that CVE? https://support.kaspersky.com/KESWin/11.9.0/en-US/173855.htm

Theoretically (I have not done this before) you can download the Updates with the update tool https://support.kaspersky.com/updater4 to a folder an point the KSC update task to that (shared) folder.

Ich schätzte die KSWS immer, weil man bei Updates (z.B. KSWS10 → 11), Deinstallation(KSWS10)/Installation(KSWS11) oder Patchinstallation (CFxxxx) keinen Neustart brauchte. Bei der KES11.8 schätze ich, ist das nun auch beim Server (aufgrund der NDIS Treiber Entfernung usw.) notwendig, oder? bez. Verschlüsselungsausnahmen habe ich mal ein Topic erstellt, wenn das gemeint ist: Link

You can exclude ost file from real time scanning...

Maybe the affected computers are not managed anymore? Are they located under “managed devices” and showing as online? Can you turn off the module (bad usb) on the local KES gui?

I would use setup_kes.exe the official documentation: https://support.kaspersky.com/KESWin/11.1.1/en-US/123468.htm

You can allow overwriting a specific setting section on the slave server policy by opening the lock in the appropriate section on the master policy, but you should close that lock on each slave server (policy) in order to not allow users on the endpoint to change it.

it depends on the sql database and version (with mssql express it could be 10gb).

To be honest I have not updated to ksc13 yet (a lot of other work, I read about troubles at the beginning with ksc 13 but they seem to be fixed now and ksc12 works fine for me till now) and in ksc12, I do not have such an issue.