MOSS and SCOM 2007

We built our server farm and we have this other computer that runs SCOM 2007.  The challenge is to get one to work with the other.

I found the SharePoint Monitoring Toolkit here.

This page has four download buttons:

  1. MOSS Management Pack installer (.msi)
  2. A zip file with "Guides" (.zip)
  3. A Readme (.rtf)
  4. WSS Management Pack installer (.msi)

The Readme is three pages and has some good inrfo on files locations and known issues.  These all have work-arounds and do not seem to be gate issues.

The "Guides" zip file includes .doc and .docx versions of the MOSS and the WSS management packs.  The MOSS doc is 101 pages.

The guide opens with perfunctory boilerplate and then begins with a Getting Started section. These instruct you to import the .mp file into your SCOM console.  This is a problem because we don't get a .mp file, we get a .msi and while some of you may know how to reconcile this distinction but I can only guess that I run the .msi and I get the .mp.

Sure enough, I run both .msi files and I end up with a C:Program FilesSystem Center Management Packs folder and it's got a MOSS and a WSS folder, each with a Management Pack folder with my .mp files inside.

The guide continues to instruct us to open the Operations Console and import the .mp files.  As far as I can be sure, this is my first venture into SCOM and it's Ops Console.  It looks alot like SQLServer 2005.  You find the Administration tree and right-click on management packs and select Import where you can navigate out to the .mps and import them.

That should give us a set of default monoitoring activities these can be modified and other can be created.

Next, we have to add the managment agent and we're pointed to http://technet.microsoft.com/en-us/library/bb309622.aspx. Here we see we have a number of options:

  1. Deploy the agent from the SCOM console.
  2. Deploy the agent directly on the target compuer (a "manual agent install")
  3. Deploy the agent from a command line.
  4. Deploy the agent by including the target in a group.
  5. Deploy the agent to a member of Multiple Management Groups (called "multihoming".)

Selecting the first option, takes me to the instructions on TechNet that introduces me to the Discovery Wizard that describes a three step process: Discover, Select, Configure.
 
Of course, my lab guys have this in one domain and I need to monitor a server in another.  I try a number of computer name options and user options ending up at the IP address and the local administrator account but, alas, the Wizard cannot discover the server.
 
🙁
 
-robot
 
 
 

 

 

 


Tags:

This entry was posted on August 29th, 2008 and is filed under Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

 
«
»
 
 

Comments are closed.