
- #Kaspersky endpoint 10 for windows how to#
- #Kaspersky endpoint 10 for windows install#
- #Kaspersky endpoint 10 for windows update#
- #Kaspersky endpoint 10 for windows software#
- #Kaspersky endpoint 10 for windows windows#
#Kaspersky endpoint 10 for windows windows#
I’ve also checked other vendors solutions and, for example, ESET has such modules available on Windows Server installation as well.įor the record: I know about the existence of Kaspersky Security for Windows Server product, we use it on servers, but it is not appropriate for cases when Windows Server is used as a Workstation, so we are not considering it. Web protection, Mail protection and others) are all present. To check if availability of workstation-related modules is not limited by technical reasons, I’ve installed the Kaspersky Small Office Security and saw, that all of the modules absent in KES (i.e. such installations will be more and more common, not only in sensitive environments. I’m sure that nowadays - with the arise of short maintenance period, bloatware, forced updates, telemetry etc. In those days it was especially for those who wanted to use the NT Kernel v5.2.
#Kaspersky endpoint 10 for windows how to#
We are not the first case where Windows Server is used as a Workstation - there are guides on the web dating back to the Server 2003 days, which explain how to “convert” the server edition to workstation variant.

I don’t know what was the motivation for such move at the time of committing to such decision, but I would like to point, that such behaviour is no longer valid. I believe that same is happening now, with version 11.6. I remember, that older version of KES, when they detected that were installed on Windows Server, changed their branding to Kaspersky Endpoint Security for File Server and workstation-related modules were missing.
#Kaspersky endpoint 10 for windows install#
When we install it on Windows Server, then some modules are missing - namely: Web protection, Mail protection and some others. The problem we face is related to the Kaspersky Endpoint Security for Windows. We are very happy with those programs and don’t want to change them. Almost all of our clients have Kaspersky Endpoint Security Select/Advanced/Total - depending on the size of infrastructure and individual specificity. We are using Kaspersky products since year 2007. The only thing which stops us now is Kaspersky software, Our tests are practically completed, almost every problem we’ve encountered was solved, so we are almost ready to go. There are some tweaks that have to be done to make Windows Server workstation friendly, but this is not a problem. It has 10 years of support, no crapware installed an probably is better tested than client version (as it was even back in the days of XP and Server 2003).
#Kaspersky endpoint 10 for windows software#
The entire thing is non-sense - in our opinion, today’s software should be supported for more, not less time than it was in the past - due to much greater dependency on it.īut, as we need to support Windows based machines, we’ve decided, that all of the workstations will be migrated to recently released Windows Sever 2022. For such sensitive environments we would have to have a separate team dedicated only to test insider builds, operate separate machines to validate it’s workings in production environments etc. Even the Enterprise LTSC version has too short period of maintenance for us (which will have only 5 years of support).
#Kaspersky endpoint 10 for windows update#
Those who maintain those systems know, that almost every update breaks something - from broken printing, across driver crashing, till data loss (which shifted the premiere of Windows Server 2019).Īfter having a lot of such issues we’ve concluded, that Windows 10 is a no-go for our applications.

However, everything changed with the advent of Windows 10, where the support period was drastically shortened and the disaster of forced updates began.

As any mission-critical system, it must operate uninterrupted as much as possible, must also be patched on a regular basics and generally be well maintained and documented.īack in the days of Windows versions 2000 till 8.1, there was an 10 year support period from Microsoft and that was fine for us, as we were able to configure, tweak and deeply customize both the Operating System and the production software to make them both run as required and expected. Our company is providing services related to integrating, maintaining and securing mission-critical systems in organizations like factories, financial institutions and defence contractors.

I would like to suggest and talk about specific change to Kaspersky Endpoint Security for Windows, but first it will be useful to lay some background explaining why such change is needed, so it’s necessity and my motivation for writing this post will be better understood.
