Differences between on-premises and cloud management console
ESET PROTECT includes all of the key features and capabilities you know from ESET PROTECT On-Prem but has been adjusted to fit the needs of a cloud-based management. You can migrate from ESET PROTECT On-Prem to ESET PROTECT.
The table below includes descriptions of the major differences between ESET PROTECT and ESET PROTECT On-Prem.
General difference |
ESET PROTECT |
ESET PROTECT On-Prem |
|||
|---|---|---|---|---|---|
Hosting |
Runs in the ESET-maintained cloud environment. |
Runs on your physical or virtualized environment. |
|||
Manageable devices limitation |
50,000 client devices. |
Limitation depends on server hardware limitations. |
|||
Supported product versions |
•Business products version 6 and later. |
•Business products version 4 and later. |
|||
Components |
•ESET Management Agent •RD Sensor •Deployment Tool •CloudMDM |
•ESET Management Agent •RD Sensor •Deployment Tool •MDM |
|||
Active Directory |
Active Directory synchronization is available with the use of ESET Active Directory Scanner. |
Active Directory synchronization is available. |
|||
Mobile Device Management |
•Mobile device management is available by default via CloudMDM. •Limited input enrollment for Android devices is available as an enrollment option. |
•Mobile device management is available via ESET PROTECT On-Prem MDM.
|
|||
Certificates |
Certificate management is handled by ESET. |
User can create, edit or import/export Certificates and Certification Authorities. |
|||
Access rights |
Access Rights Management was moved to ESET Business Account but you can specify access to specific ESET PROTECT features for a user with custom permissions. |
Advanced multi-tenant access rights security model that is manageable from the ESET PROTECT On-Prem interface. |
|||
License management |
License management was fully moved to ESET Business Account. |
License management is partially in ESET PROTECT On-Prem and partially in ESET Business Account. |
|||
How to add computers |
Computers can be added via Active Directory synchronization, from an RD sensor report and using GPO and SCCM installer scripts, or by installing Agent locally. |
Computers can be added via Active Directory synchronization, from an RD sensor report, using GPO and SCCM installer scripts, manually by adding a new device with the addition of an Agent Deployment task, or by installing Agent locally. |
|||
Additional protection layers |
•ESET Vulnerability & Patch Management
|
