Scott Moss at myITforum.com

Microsoft Released Microsoft Windows Servers Base Operating System management pack version 05.0.3500.0010.

This update introduces monitoring of additional components available within the Microsoft Windows Server 2003 R2 operating system including Identity Management for UNIX(IDMU), Hardware Management events,NTFS file system monitoring, File Server Resource Monitoring (FSRM), Shadow Copies for Shared Folders (SCSF) Monitoring and more (See Management Pack Monitoring Scenarios with the Management Pack Guide for more information).

http://www.microsoft.com/downloads/details.aspx?familyid=E553062F-BD85-4772-8037-8B91F457B710&displaylang=en

MOM 2005 SMS 2003 Crash Dumps: Monitoring SMS Executive script error

I've recently run into some bizarre SMS Script Errors. See below for more information.

Description

SMS 2003 Crash Dumps: Monitoring SMS Executive script error.
The script 'SMS 2003 Monitor SMS Executive Crash Dumps' running under processing rule 'SMS 2003 Crash Dumps: Monitoring SMS Executive' encountered a runtime error.Failed to load script variables.

The error returned was: 'Invalid procedure call or argument' 5 (0x5) The ProblemThis script was bombing out b/c it was expecting a value in the file c:\windows\temp\SMS 2003 Monitor SMS Executive Crash Dumps.VarSet on the SMS Server.
In my case this file was empty and caused the script to die.
The date and version number of this SMS 2003 Monitor SMS Executive Crash Dumps script is 08/24/04  05.0.2707.0000.

The fix

Delete the file c:\windows\temp\SMS 2003 Monitor SMS Executive Crash Dumps.VarSetThe next time the script runs it will create the file and put the proper values in it.

Visit my blog

http://myitforum.com/cs2/blogs/smoss/default.aspx

MOM 2005 SMS 2003 Management Point Availability: Script error

I've recently run into some bizarre SMS Script Errors. See below for more information.

Description

SMS 2003 Management Point Availability: Script error.

The script 'SMS 2003 Monitor Management Point Availability' running under processing
rule 'SMS 2003 Management Point Availability: Monitoring' encountered a runtime error.
Failed to load script variables.
The error returned was: 'Invalid procedure call or argument' 5 (0x5)

The Problem
This script was bombing out b/c it was expecting a value in the file
c:\windows\temp\SMS 2003 Management Point Availability.varset on the SMS server.
In my case this file was empty and caused the script to die. The SMS 2003 Monitor Management Point Availability script date and version number were 09/24/04  02.50.2751.0000.

The fix
Delete the file c:\windows\temp\SMS 2003 Management Point Availability.varset
The next time the script runs it should create a new file containing data
listing StartDateTime and UnavailableDuration.

Visit my blog
http://myitforum.com/cs2/blogs/smoss/default.aspx

 Expect a System Center Operations Manager 2007 Reporting Hotfix to be released soon.

One of the items the hot fix will address, allow an install in a disjointed DNS namespace.

Just spreading the good word!! 

I've been a member/poster on momcommunity.com for about a year now.

Its a great site. I look forward to seeing the new site May 28th.

 WOOT!

This can be a useful utility if you deal with XML files.

http://www.microsoft.com/downloads/details.aspx?familyid=72d6aa49-787d-4118-ba5f-4f30fe913628&displaylang=en

Run the following query against your OnePoint database, and it will output all the managed computer names

--SQL QUERY 

select Name from Computer
WHERE [IsConfigManager]=0 AND ManagedType = '2' AND (idConfigManager IS NULL OR idComputer <> idConfigManager) AND  IsAddedByServiceDiscovery = 0 AND [Type] <> 67108864

 -- END

Enjoy!