Monitoring settings

The monitoring settings available in Agent profiles in nVision 9 were moved to users and groups in the new version of nVision 10.

The default settings are settings that were migrated from nVision 9 and assigned to the Atlas.

Determination of the default monitoring settings in nVision 10 comes down to the aggregation of all settings in the Agent profile from nVision 9 that were used by at least one user account, whereas:

•if the selected option was monitored in at least one Agent profile in nVision 9, it is monitored in the default settings after data migration to nVision 10,

•if activity over time was being sent in at least one profile, it is sent in the default settings after migration,

•if breaks in activity were detected in at least one profile, they are also detected after migration,

•the migrated break time in the default settings is the minimum time selected from all existing Agent profiles,

•the monitoring time range in the default settings is the sum of all the time ranges in existing Agent profiles:

oif time ranges do not overlap, a new range is determined during data migration, starting at the earliest and ending at the latest time from all existing profiles (e.g. the ranges of 8:00 - 12:00 and 15:00 - 18:00 will be migrated to the range of 8:00 - 18:00),

ospecial case: if the continuous monitoring time was set for at least one profile, the default setting after migration will also be continuous monitoring,

•if any profile in nVision 9 allowed desktop preview, remote access or bypassing the user’s approval for remote access, they will also be allowed in the migrated default settings,

•if any profile in nVision 9 allowed the Agent icon to be displayed, it will also be allowed in the default settings.

In the migration process, user groups are created, and they are the carrier of monitoring settings from the existing Agent profiles. Each group contains monitoring settings such that the user belonging to this group is covered by the same monitoring settings as those in the Agent profile in nVision 9.

During data migration, the parent group “Monitoring” is created and includes 3 built-in subgroups:

•Groups from profiles,

•Groups from maps,

•Groups from devices.

The parent group and the built-in subgroups do not contain any built-in settings.

In the built-in subgroups, the user groups will be created and take the names after:

•monitoring profiles used in nVision 9,

•maps if they used individual settings in nVision 9,

•devices if they used individual settings (i.e. did not use the Agent profile or map settings).

Then, the accounts of users that were working on devices in the relevant profiles in nVision 9 will be added to the groups.

•The monitoring time range at the profile (group) level is not migrated. You may not establish these ranges at the group level in version 10 of the program. All time ranges from all profiles are aggregated into a single global range in the settings.

•As a result of the migration, the effective rights of the user working on more than one computer may be increased. For example, if the user was working on a computer with enabled monitoring and on another one where it was disabled in nVision 9, after migration the user will not be monitored on both computers (because the “Don’t monitor” exception will apply to the user on both computers).

•The monitoring and blocking settings in nVision were connected with the device icon and the map on which the device was located. Thus, it was possible to define different security policies for new users (depending on the computer location). In nVision 10, there is a single set of default rights for each new user, therefore the Administrator has to manually create groups with rights and assign new users to them each time.