Migrate devices into the Companies tree

By migrating your devices into the Companies static group, you will receive following benefits:

Automatically synchronized group structure in ESET PROTECT

•When a new site is added through a management portal (ESET Business Account or ESET PROTECT Hub), this site will automatically appear within minutes in ESET PROTECT under the Companies static group.

Automatically synchronized access rights in ESET PROTECT

•The setup of granular permission sets per site is currently too complex—partially, they need to be set in the license management portal (ESET Business Account) and partially in ESET PROTECT.

•In ESET PROTECT Hub, you can set up access rights, and they they will automatically propagate into ESET PROTECT, assigned to synchronized static groups. Administrator will not have to perform the permission setup twice (in ESET Business Account and in ESET PROTECT).

•When the divergence between ESET PROTECT Hub and ESET PROTECT access rights is needed, you can set up a custom permission set for ESET PROTECT.

Improved deployment capabilities in ESET PROTECT

•After the migration, ESET PROTECT can decide to which company and/or site a device belongs to, which may result in an improved experience when using the Platform modules screen.

•ESET PROTECT can always select correct device licenses, depending on their location in the static group tree.

Incident management

•After the migration, ESET PROTECT can correlate devices to incidents correctly according to hierarchy.

Non-MSPs, currently managing devices outside of the Companies synchronized static group or its sub-tree.

•Computers and groups

•Policy assignments

•Client task assignments

•Server tasks

•Notifications

•Installers

•Permission sets

•Users

Different non-MSPs manage their environments in different ways; there are two common use cases identified:

•Company devices are managed directly under the All static group.

•Site devices are divided into static groups, each containing devices of a single site.

Policy assignments and client task assignments

•All policy and client task assignments assigned to the All static group will function as before.

•All policy and client task assignments assigned to dynamic groups located directly under the All static group will function as before.

•All policy and client task assignments assigned to the migrated static group, or to any of its subgroups or computers, will function as before.

•The migrated static group may lose some policy configurations or client task assignments, if this configuration is inherited from any static groups between the old position of the migrated static group and the All static group.

•The migrated static group may receive some additional policy configurations or client task assignments, if this configuration is inherited from any static groups between the new position of the migrated static group and the All static group.

Server tasks (rename computers and delete not connecting computers)

•The same rules apply as to policy and client task assignments.

Notifications

•All notifications with monitored static group All will function correctly as before.

•All notifications with the monitored static group to be migrated will function correctly as before.

Installers

•All installers created for the static group to be migrated or for any of its subgroups will function correctly as before.

•Installers created for the static group outside of Companies or its sub-tree that are not created for groups that will be migrated should eventually be replaced.

Incidents

•After devices are migrated into the correct subgroups, incidents created before the migration related to these devices will not be migrated. This means company administrators may occasionally lose visibility over incidents that occurred before the migration.

•Incidents created after the migration will be correctly assigned to company static group.

AD synchronization

•If there is AD synchronization directly into the All static group, it must be revoked before the migration.

•AD synchronization tokens for static groups that will be migrated will function correctly as before.