Installation Requirements

Secure installation requires outbound connectivity to esa.eset.com on TCP port 443. If installing in an Active Directory environment, the installer must be run by a member of the "Domain Administrators" security group, otherwise a user with administrator privileges is required. Another requirement for running the installer is .NET Framework Version 4.5 (Full Install). The installer will automatically attempt to install .NET 4.5 if it is not already installed.

ESA supports the installation of components in a distributed environment, with all components installed on computers that are joined to the same Windows domain.

Windows Firewall exceptions essential for the proper function of ESET Secure Authentication will be added automatically as part of installation. If you use a different firewall solution, see Firewall exceptions for information about important exceptions that you will need to create.

The prerequisites for the installation of each component are:

Authentication Service:

oWindows Server 2008 or later SOS in the list of Supported Operating Systems

oIf installing in an Active Directory environment, the installer must be run as a user who is a member of the "Schema Admins" security group the first time an Authentication Service is installed on the domain.

Management Tools:

oWindows7 or later COS in the list of Supported Operating Systems, Windows Server 2008 or later SOS in the list of Supported Operating Systems

o.NET Framework version 3.5

oWindows Remote Server Administration Tools, Active Directory Domain Services component (RSAT AD DS)

note

RSAT was previously known as the Remote Administration Pack (adminpack) and is downloadable from Microsoft. In Windows Server 2008 and later, this component may be installed from the “Add Feature” wizard in the Server Manager. All Domain Controllers already have these components installed.

RADIUS Server:

oWindows Server 2008 or later SOS in the list of Supported Operating Systems

Web App Plug-in for Microsoft Exchange Server:

oMicrosoft Exchange Server 2007 or later (64-bit only), with the Client Access role (Outlook Web App / Outlook Web Access) installed

o.NET Framework version 3.5

oInternet Information Services 7 (IIS7) or later

Web App Plug-in for Microsoft SharePoint Server:

oMicrosoft SharePoint Server 2010 or 2013 (64-bit only)

o.NET Framework version 4.5

Web App Plug-in for Microsoft Dynamics CRM:

oMicrosoft Dynamics CRM 2011, 2013 or 2015

o.NET Framework version 4.5

Web App Plug-in for Microsoft Terminal Services Web Access:

oThe Terminal Services role with the Terminal Services role service installed on Windows Server 2008

o.NET Framework version 4.5

Web App Plug-in for Microsoft Remote Desktop Services Web Access:

oThe Remote Desktop Services role with the Remote Desktop Web Access role service installed on Windows Server 2008 R2 and later SOS in the list of Supported Operating Systems

o.NET Framework version 4.5

Web App Plug-in for Microsoft Remote Web Access:

oThe Remote Web Access role service installed on Windows SBS 2008 where it is called Remote Web Access, Windows SBS 2011, Windows Server 2012 Essentials and Windows Server 2012 Essentials R2  

o.NET Framework version 4.5

Remote Desktop Protection:

oWindows Server 2008 R2 or later SOS in the list of Supported Operating Systems

oMicrosoft Windows 7 or later COS in the list of Supported Operating Systems

oOnly 64-bit operating systems are supported

Windows login protection:

oWindows Server 2008 R2 or later SOS in the list of Supported Operating Systems

oWindows 7 or later COS in the list of Supported Operating Systems

ADFS 3.0 or 4.0 protection:

oWindows Server 2012 R2

 

.NET Requirements:

All components: .NET 4.5 Full Install

Core Server: .NET 4.5 Full Install

RADIUS Server: .NET 4.5 Full Install

Management Tools: .NET 3.5 (4 on Windows Server 2012)

Web App Plugin: .NET 4.5, however, IIS Filters require .Net version 3.5

 

note

Installing ESA Core (Authentication Server) and RADIUS Server on a COS in the list of Supported Operating Systems might not be aligned 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.