Hello,

in relation to:

https://eap.kaspersky.com/topic/3887/not-all-modules-are-available-on-windows-server-installation

https://eap.kaspersky.com/topic/3784/what-s-new

I would like to report, that KES versions 11.8 - 11.10 installed on Windows Server says, that those modules are not covered by license. I'm not sure if they are fully enabled or not, but the UI says as stated.

To see what I mean, just go to Security tab in the main window and notice, that those modules don't have an green circle near them and after clicking three dots* you will see, that those modules "are not covered by license" - at least this is what UI says.

* God how I hate today's UI's! Especially we, Russians, should use only Win32 native windows and controls - it is part of our culture and global trademark.

By the way, thank you for thanking me in the about window of KES - I really appreciate it.

If it would be possible, I would like to change my nick there to be more descriptive. PM me if you can do that for me.

Thank you very much for your engagement!

I'll watch this case.

(I'm duplicating myself with https://eap.kaspersky.com/topic/3784/what-s-new because I'm not sure if this has been viewed).

Background

Version 11.8 huge improvement:

Enhanced Kaspersky Endpoint Security capabilities for servers. Added support for the Web Threat Protection, Mail Threat Protection, Web Control and Device Control components for computers running the Windows Server operating system.

Reproduction steps:

Check the available modules list while installing KES. Not all modules are available while installing on Windows Server.

Actual result:

The following modules are not available under Windows Server installation:

1. Advanced Threat Protection -> Host Intrusion Prevention
2. Security Controls -> Adaptive Anomaly Control
3. Data Encryption -> File Level Encryption
4. Data Encryption -> Full Disk Encryption

Expected Result:

All of the above listed modules should be available.

It is also worth considering the inclusion of modules from Kaspersky Internet Security suite - like web camera protection, safe money or screen keyboard. There is no so much difference in PC vs. Workstation in terms of the general Internet usage nowadays.

Hello,

thank you very much for enhancing protection capabilities for servers. It is really important in such scenarios where Windows Server is used as a workstation or Terminal Server for remote users - as I wrote here.

Please keep in mind, that at this moment the following components are still not available under Windows Server installation:

1. Advanced Threat Protection -> Host Intrusion Prevention
2. Security Controls -> Adaptive Anomaly Control
3. Data Encryption -> File Level Encryption
4. Data Encryption -> Full Disk Encryption

Greetings

MarkNN

It's not an actual bug, but a change request.

The interface introduced in version 11.7 & 11.8 is TERRIBLE. Black window with white elements makes it really hard to control. It's is REALLY easy to make a mistake or miss something. There should be an option to change the theme.

I also think that such "fancy-candy-hipster" theme is a no-go for enterprise products, where we have admins who really have more important things to do than messing around sick current trends. In my opinion the best interface was in version 11.4 - clear, simple, based on classic Windows dialog controls. We really don't need anything fancy here, we know that new version of system-level programs is all about internal news and improvements.

Problem

After system boot and user logon, the GUI of KES versions 11.6, 11.7 and 11.8 is not loaded.Version 11.4 and earlier are not affected.

Reproduction steps:

Boot the system and logon. You will see, that GUI is loaded only after user clicks the tray icon or initiate an file virus scan. It is really annoying that user must wait so much time to access program interface, and especially in the second case, it is irritating that there is no progress window after initiating the scan (from file/folder context menu) and to see it user must lunch the scan for the second time.

Actual result:

I understand that such behaviour is motivated probably to limit the usage of system resources, but GUI loading should be user-controlled option in program settings.

Expected Result:

If we are talking about a workstation user, then GUI load at boot/logon is expected to be able to quickly access program interface and get view of the progress of file scans.

If there is another case where GUI isn't accessed so often, then user should be able to disable it's loading by an option in program settings.