Integrating Orion MP with SCOM2007 on Windows Server 2008

Question

I'm involved in building a network management solution for a fairly complex network.  Our clients requirements dictate that we use Windows 2008 as the server platform.

Our Orion sales rep has confirmed that Orion is roadmapped for 2008 compatibility although the current version is not supported - to this end we have built the following test lab (all OS's are 64 bit)

Windows 2008 Server - Running SQL 2008 and SCOM 2007 (Root Management Server (RMS) and all components)

Windows 2003 R2 Server - Running Orion NPM, Orion NCM and SCOM 2007 (additional Management Server)

We have tried installing the Orion Management Pack on 2008, but the Orion MP Service fails to start on the installer, it just times out.

We have tried installing the Orion Management Pack on 2003 and made the 2003 box a secondary management server, but it fails to find SCOM (Orion MP log indicates this is due to the management server not running the SDK service - this can only be run on the root management server).

The orion logs indicate the Orion MP service is attempting to talk to the SDK service at localhost.

My questions are:

1.  Is there a way to tell the Orion MP service to talk to the SDK service on a different server (ie, replace localhost with our RMS).

2.  Is there a way to install the Orion MP service on 2008?  I can't simply accept that it "isn't compatible".  That's a ridiculous answer.  I can understand NPM needing migration due to IIS7, but the Orion MP service must be able to run using some "tweak".  I've tried to find the log files to see why it's failing, but it doesn't appear to be writing them (I have given the everyone domain group write permissions to the Progfiles/Public folder and subfolder (which is where the logs are written I believe)).

3.  Any other solutions or suggestions for the above ;)

Failure on this isn't an options...

Thanks in advance,

macro044 · Answer

If you are comfortable rebuilding / restoring SQL databases that may have corrupted (remember the official line is "it is unsupported") then

please take a look at the partial guide I have

There are still a few issues (features of 2008 & IIS7) to negotiate before the website

works. (I suspect a few new security tick boxes somwhere in 2008)

FormerMember · Answer

NPM will support 2008 later this year.

QSE · Answer

What is the ETA for a 2008 tested development?

I still struggle with the statement that it simply "won't work" on 2008 - there has to be a reason (or reasons) why.  It must be looking for some specific DLL, trying to access an area of the file or registry system that now has higher protection or has moved from 2003, trying to bind some port that needs a firewall permission etc etc.  Unfortunately I don't have enough time this coming week to dig deeper but if I find anything I will post it.  If any others reading this could post if they happen on a solution we can all benefit.