As of release 26, Unitrunker has a very effective mechanism for merging two or more systems into one. All groups, users and sites from the redundant system are copied / merged into one system. This mechanism is related to but different from the delegate mechanism.
With the publication of release 26, it is possible for you to manually link two or more systems together (delegate) or manually consolidate them. Two tool buttons were added to the System view to facilitate this; delegate and consolidate. To learn more about the delegate button, look here.
Clicking the consolidate button prompts you to pick a destination system. The groups, users, and sites from the current system window will be moved to the destination system. If there are conflicts in any of the labels, groups and/or user merge window will appear asking you to resolve the differences eg. which to accept and which to discard. This is the same window used to resolve conflicts in data from the RR DB download. Once you're done, the original system is gone! Look to the destination system for merged group, user and site data.
The list of viable destination systems conforms to the following restictions:
Caution: this operation is not reversible. In the interest of data integrity, go to the archive tab and click on the Save button to preserve your existing data before attempting any delegate or consolidate operations. If you end up with a mess, use the Archive tab's "Take Me Back" button to restore your sanity.
Why would you want to do this? Good question. Here are some scenarios.
APCO P25: none. Use the delegate feature.
EDACS: you monitor a large wide-area EDACS system where all site numbers are unique. Use the consolidate button to combine them into one place. If you find the system re-uses site numbers (eg. two or more sites with the same site number), instead use the delegate button to link them together while keeping the sites separate.
Motorola: none. Use the delegate feature.
MPT1327: you have two systems that are part of a larger network. Use consolidate to combine them into one system. Also beware the data model for MPT1327 has changed with release 26.
LTR: none of this is applicable to LTR or Passport (until LTR-Net is supported).
If none of the above scenarios apply, don't touch these buttons! Ask questions on the RR forum or the Google group.