ESA components and OS compatibility

The following table displays the supported Windows operating systems for each ESET Secure Authentication component.

See installation requirements for further details.

WS = Windows Server


WS 2008

WS 2008 R2

WS 2012

WS 2012 R2

Windows SBS 2008

Windows SBS 2011

WS 2012 Essentials

WS 2012 R2 Essentials

WS 2016

WS 2016 Essentials

WS 2019

WS 2019 Essentials

Authentication Service

Management Tools

Reporting Engine (Elasticsearch)

 

 

 

 

 

 

 

 

 

RADIUS Server

Web App Plug-in for MS Exchange Server

*

Web App Plug-in for MS SharePoint Server

 

 

 

Web App Plug-in for MS Dynamics CRM

 

 

 

Web App Plug-in for MS Remote Desktop Services Web Access

**

 

Web App Plug-in for MS Remote Web Access

 

 

 

 

 

 

Remote Desktop Protection

 

 

Windows login protection

 

 

ADFS 3.0 or 4.0

 

 

 

 

 

* 64-bit version of operating system is required

** MS Terminal Services on Windows Server 2008


Windows 7

Windows 8

Windows 8.1

Windows 10

Authentication Service

Management Tools

Reporting Engine

RADIUS Server

Web App Plug-in for MS Exchange Server *

 

 

 

 

Web App Plug-in for MS SharePoint Server *

 

 

 

 

Web App Plug-in for MS Dynamics CRM

 

 

 

 

Web App Plug-in for MS Terminal Services Web Access

 

 

 

 

Web App Plug-in for MS Remote Desktop Services Web Access

 

 

 

 

Web App Plug-in for MS Remote Web Access

 

 

 

 

Remote Desktop Protection*

Windows login protection

ADFS 3.0 or 4.0

 

 

 

 

* 64-bit version of operating system is required

 

note

RADIUS Server on Windows Small Business Server

When you install a RADIUS Server on Windows Small Business Server 2008 or 2011, the default NPS port must be changed from 1812 to 1645. Verify that there are no processes listening on port 1812 before installing ESA by running the following command: C:\> netstat -a -p udp | more

note

Note

Installing ESA Core (Authentication Server) and RADIUS Server on a COS in the list of Supported Operating Systems might not be in alignment with Microsoft's licensing policy. Consult Microsoft's licensing policy or your software supplier for details. Moreover, a COS may present other limitations (for instance number of maximum concurrent TCP connections) compared to a SOS.