 | Controlled migration between management platforms. Continue to use either/both platforms for as long as needed - keeping your migration options open. | | Using the same Operations Manager tools as are used for the Windows domain to manage alerts, rules, performance and deliver reports minimizes complexity and reliance on disparate information from redundant tools . |
| Advanced object oriented features found in Operations Manager 2007 have been extended to allow Distributed Application modeling/definition and Health Explorer views and reporting – just like in the Windows domain. | | Inheritance by creating an object within Operations Manager for each system/device/application managed by a connected alternative management system, enables the modeling of relationships between the various components of your infrastructure, including any inheritance of an alert within any parent-child relationship. |
| Two licensing modes flexibility to license per connector, for each connected 3rd party management system or per node, at the same rate as our Quest Management Xtensions (QMX) – Operations Manager 2007 and 2005 offerings. | | Integration with Quest Management Xtensions leverage Quest Management Xtensions (QMX), which extends Operations Manager to more than 250 non-Windows systems,devices and clients, to aide in migration strategies to Operations Manager, or to fill gaps of coverage not provided by 3rd party management systems. |