1. Health does not have to roll-up to the state of a computer! So just because something on the computer is red that doesn't mean the whole computer is red (depending on the Health Model, of course).
2. Multiple user accounts can be used by the same agent to run different functions on the same machine - versus the monolithic agent Action account - by using the Run as Execution feature. This way you can have different credentials running SQL tasks and Exchange tasks on the same box.
3. You can create user roles to have granular control of access to view objects and perform tasks.
4. Run Setup from the splash screen - as it detects x32/x64 and enables logging during the installation.
5. No more DTS to move data from the Operations database to the Reporting database! Data is sent to the Reporting database directly from the management server.
6. New role of the Root Management Server which can be clustered for high availability.
7. Self-tuning thresholds are available which can learn what are appropriate thresholds for specific counters.
8. Management packs can be deleted. (Yeah!)
9. Easy functionality available to monitor items such as TCP port checks on "black-box" systems.
10. Data in the reporting database is not based on raw data but rather uses aggregated data.
11. Maintenance mode can be used to put a component into maintenance rather than the entire computer.
12. The Exchange 2007 MP will include rules for the Exchange Best Practices Analyzer. 

1. Installed FCS on its own server; this installs a MOM 2005 instance that is tuned and dedicated to managing FCS alerts.
2. Deployed the FCS Client on five target servers in an OpsMgr 2007 management group using the /NOMOM switch to not install the MOM 2005 agent component along with the FCS client.
3. Located the FCS managemnet pack (in the MOM 2005 binary AKM format) on the FCS server.
4. Copied the MP2XMP.exe "Convert Management Packs to XML" utility from the MOM 2005 SP1 Resource Kit to the FCS server.
5. Ran the MP2XML utility and created a MOM 2005 XML-formatted management pack (i.e. MOM 2005 AKM format to MOM 2005 XML format).
6. Copied the newly created MOM 2005 XML management pack to the OpsMgr 2007 management server.
7. Ran the MPConvert.exe utility on the OpsMgr 2007 server and created a "converted" XML management pack.
8. Used the OpsMgr 2007 console Administration space to import the converted management pack.

Importing the converted MP was a success and created a "Microsoft Forefront Client Security" folder in the OpsMgr 2007 console Monitoring space that included Alerts, State, and Task Status views. Within minutes the State view was correctly populated with the five target computers managed by OpsMgr 2007 where the FCS Client had been installed. While using OpsMgr 2007 to monitor FCS Clients provides only limited functionality compared to the original MOM 2005-based FCS solution now in beta, we were impressed with the error-free performance of the conversion and importing utilities and features.

As background, there is a great document contained within the connector software package called the “MOM to HP OVOW Product Connector Setup Guide.doc” which provides the vast majority of the information required. The document is included as part of the download available at http://www.microsoft.com/downloads/momprodconnectors.mspx, HP Openview 1.0 Connector. There is also an Engryo MOM to HP OpenView connector, but this particular document focuses on the HP OpenView 1.0 Connector. 

1. Install and configure a MOM 2005 environment. It is assumed you have MOM 2005 SP1 installed and working.
2. Install and configure HP OpenView. A downloadable 60-day trial version is available at http://www.openview.hp.com/products/ovowin/download.html. You will need to create a HP Passport to download the software.
3. On an OpenView server, install Internet Information Services (control panel, add/remove programs, add/remove windows components).
4. Install the trial version of HP OpenView. Click Next to continue, check "Console, Server and Agents" on the second screen. If the prerequisites check Ok, click Next to continue. Click Ok on the note about WMI and WWW services restarting. Take the default option to "Create the local database server automatically" (MSDE). Take the default to "Create database files" and click Next to continue. Enter a SA password, click Next to continue. Accept the license agreements and click Next. Take the default destination folder locations and click Next to continue. Enter passwords for the groups and users defined and click Next. Click Ok to accept the account screen. Finally click Install on the Ready to Install screen. Click Next when the installation is completed.
5. Install the MCF on the MOM Management Server and verify its functiionality by accessing the URL: http://[ComputerName]:[port] I
6. Download and install Windows Script 5.6 from Microsoft on the HP OpenView server, available at http://download.microsoft.com - search on "Windows Script 5.6".
7. Download and install the Java Runtime environment on the HP OpenView server available at http://java.sun.com/j2se/1.4.2/download.html.
8. Now, install the HP OpenView Interconnect on the HP OpenView server. We could not get this to install - it failed when trying to run the program and would continue to ask for a location to extract the files from. This actually was a sign that the data file was corrupt. HP provided an alternate location to download the file from. The valid version of the file (ovi_34_install.exe) ran correctly.
   • Good reference material on this: http://devresource.hp.com/drc/tutorials/ovi/OVI_basics_123.tutorial.asp. If your intallation fails with "you must have administrator privileges to isntall OVI on a Windows System!" even though you are logged on as an administrator, reboot and re-try (this occurred during testing).
   • Select custom installation with all items including the OVI Pluglets (we initially ran with only specific components installed, but the next step failed as a result).
9. Install the MOM_to_HPOVOW_EC_setup.msi with defaults on the HP OpenView server / tracked down prerequisites (Windows Script 5.6, Java Runtime 1.4+). A success condition on this installation is validated by seeing two new services called "OVI to MOM" and "MOM to HP OVOW Event Consumer." Confirm that these services will start.
10. Install the MOM_to_HPOVO_PC_Setup.msi with defaults on the HP OpenView server.
11. On the MOM server, import the management pack within the Administrator console. As we had installed the MOM_to_HPOVO_PC_Setup.msi on the HO OpenView server, the akm file had to be copied from that server (%programfiles%\MOM to HO OVO Product Connector) to the management server.
12. On the HP OpenView server, open the nodes and locate the MOM Management Server. right-click and choose to mange the MOM server. If it is unable to identify the OS, define it on the properties of the MOM server.
13. Create DNS secondary zones on each of the two servers for the server in the other domain.
14. Install the MOM agent on the HP OpenView server so it can be discovered by the "MOM to HP OVO Product Connector" group.
15. Reference Http://support.microsoft.com/kb/885720 to change the registry configuration on the HP OpenView server (regedit, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft subkey, and then click ProductConnector, MOMservers=http://mom-server:1271/Connectorservice.asmx).  
16. Restart the MOM to HP OVO Connector Product Service and validate that you can browse to the URL which you put into the MOMServers registry value.
17. Before you forward your first alert make sure that you do not already have an alert resolution state of 203 defined. If you do, change any active alerts that are in that state to another state (such as new or acknowledged), and then change your alert resolution state of 203 to a different number. As part of the process of using the connector it will create its own alert resolution state of 203 which will be called "HP OpenView Operations."
18. On the MOM server, copy the "Forward Alets to HP OVO" alerts from the management pack to the management pack that you want to alert from. In this case, it was copied to the Microsoft Windows Servers Base Operating System\Windows 2003\Core Systems Components and Services area. On the alert criteria tab, change the "only match alerts" option to restruct to this area (Microsoft Windows Server Base Operating System\Windows 2003\Core System Components and Services). Enable the alert and commit your changes.
19. Stop a service to fail to activate an alert and it appeared on both the HP OpenView console and the MOM console.

We have included two screenshots. The first is a screenshot of the HP OpenView console with an alert that was sent via the MOM Server over the connector (Monarch). The second is a screenshot of the MOM Operator console alert details for the alert sent to HP OpenView.