What migrates from NIMS to OMS
Nearly every NIMS setting will successfully migrate to OMS. The details of these migrated settings are provided.
 
Authentication
Authentication settings for RADIUS, TACACS+, Active Directory, and the local NIMS list, are migrated. Active Directory settings currently experience a glitch after migration, and it must be fixed manually. The settings migrated for all authentication settings include, but are not limited to, IP addresses and ports, authentication choices, shared secrets, and bindings. RADIUS only migrates one primary and one secondary server—not the optional primary and secondary accounting servers. Cache timers for authentication will not be migrated for any authentication scheme.
Auto-upgrade
Auto-upgrade settings used in NIMS are migrated. The settings include transfer and installation schedules, maximum concurrent transfers, speed limit for transfers, and if auto-upgrade is enabled or disabled. These settings will migrate to the Global Upgrade Policy in OMS.
Auto-upgrade (per entity)
Any unique auto-upgrade settings on entities and entity groups are migrated. The settings include transfer and installation schedules, maximum concurrent transfers, speed limit for transfers, and if auto-upgrade is enabled or disabled per entity. Any unique auto-upgrade settings for an entity or entity groups will be given an automatically generated upgrade policy named ConversionGeneratedPolicy with a number appended to the name. The generated name can be manually renamed.
Email Notification Settings
Configuration details for forwarding log events and alarms as emails will be migrated. This includes the mail server and port, any authentication credentials, encryption choice, and email display name. If you actively use email for sending log events and alarm notification in NIMS, this will continue in OMS uninterrupted.
Entities
The following entities migrate: Observer, Probe, GigaStor, OI, Observer Reporting Server. The data migrated is primarily, but not limited to, each entity’s IP address, probe name (if known), and probe ID (if known). If the probe name and ID are not currently known in NIMS, they will later be resolved by OMS when connected.
Entity Groups
If you used entity groups in NIMS, an optional feature, these migrate to OMS. The relationships between your entities and their entity groups will remain. Entity group names will remain the same after migration.
Failover / Redundancy
The primary-secondary configuration of NIMS will migrate. This includes the choice to use failover functionality (for example, enabled versus disabled), the IP address of the other NIMS server, and the designation if a NIMS system is the primary or not.
Licenses
Licenses for versions 15 and 16 products will be migrated. This includes the relationship between the license and the entity it currently belongs to. Any unassigned licenses in NIMS will remain available in OMS.
Permissions
Access permissions given to user groups in NIMS are migrated to OMS. These settings include the type of interactions user groups can make on entities. Any unique permission settings for user groups will be given an automatically generated authorization policy named ConversionGeneratedPolicy with a number appended to the name. The generated name can be manually renamed.
Shared Filters
Any shared filters that NIMS was aware of will migrate to OMS. This includes the logic of each filter, the name of each filter, and the “available” or “deleted” status of each filter.
Syslog Event Export
Configuration details for exporting log events to a Syslog server will be migrated. This includes the RFC format of the Syslog messages, the target IP address of one Syslog server, and your selection if log events are forwarded to the Syslog server (for example: enabled versus disabled). The facility number is not migrated. If you actively use the Syslog event export feature in NIMS, this will continue in OMS uninterrupted.
Users
All users set in NIMS are migrated to OMS. This includes each user’s authentication management type (local or remote authentication), email address if one exists, the user names, and finally the password if it is a locally managed user. Password fields remain masked in OMS.
User Groups
All user groups are migrated from NIMS to OMS. This includes any relationship between users and user groups, access permissions of user groups to entities and entity groups, and permissions the user group has for interacting with entities.