Things to consider before the migration

Policy assignments and client task assignments

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

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

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

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

•The migrated static group may receive some additional policy configuration or client task assignment, if this configuration is inherited from any groups between the new position of the migrated static group and the All 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 the monitored static group All will function as before.

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

Installers

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

•Installers created for the static group outside of Companies or its sub-tree and 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 that in some cases, company administrators may lose visibility over incidents that happened before the migration.

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

AD synchronization

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

 

˄˅