Update: The contemporary, unified Microsoft Defender for Endpoint option for Windows Server 2012 R2 and Windows Server 2016 is now usually readily available since April 11 th, 2022.
Customers with makers on the existing Microsoft Defender for Server (now identified P2) offering can either make it possible for the brand-new service with a toggle, or target the MDE.Windows extension for implementation utilizing the Microsoft Defender for Cloud effort “Deploy Microsoft Defender for Endpoint representative on relevant images”.
Today, we are including a broad set of avoidance, detection and reaction abilities, formerly just readily available on Windows Server 2019 and later on, to Microsoft Defender for Endpoint on Windows Server 2012 R2 and 2016 utilizing an up-to-date, totally revamped option stack.
Introducing our improved, merged option for Windows Server 2012 R2 and 2016!
We are happy to present the general public sneak peek of a totally revamped Microsoft Defender for Endpoint option stack for Windows Server 2012 R2 and Windows Server2016 Whilst maintaining to date and supporting security health is perhaps still the very best go-to when it pertains to increasing durability and decreasing attack surface area, our company believe this contemporary, unified service brings the very best of the Microsoft Defender for Endpoint abilities for avoidance, detection, and reaction – in a single plan.
Server onboarding actions.
This brand-new merged option plan decreases intricacy by eliminating reliances and setup actions. It likewise standardizes abilities and performance as it brings a really high level of parity with Microsoft Defender for Endpoint on Windows Server 2019:
Overview of Microsoft Defender for Endpoint abilities per os
Aside from having no particular customer requirements or dependences, the service is functionally comparable to Microsoft Defender for Endpoint on Windows Server 2019; significance, all environment requirements around connection are the very same and you can utilize the very same Group Policy, PowerShell commands and Microsoft Endpoint Configuration Manager to handle setup. The service does not utilize or need the setup of the Microsoft Monitoring Agent (MMA).