SCOM Alert Description

A list of custom properties for alert description and notification:
For event Rules:

EventDisplayNumber (Event ID): $Data/EventDisplayNumber$ EventDescription (Description): $Data/EventDescription$ Publisher Name (Event Source): $Data/PublisherName$
EventCategory: $Data/EventCategory$ LoggingComputer: $Data/LoggingComputer$
EventLevel: $Data/EventLevel$
Channel: $Data/Channel$ UserName: $Data/UserName$
EventNumber: $Data/EventNumber$

For event Monitors:

EventDisplayNumber (Event ID): $Data/Context/EventDisplayNumber$ EventDescription (Description): $Data/Context/EventDescription$ Publisher Name (Event Source): $Data/Context/PublisherName$
EventCategory: $Data/Context/EventCategory$ LoggingComputer: $Data/Context/LoggingComputer$
EventLevel: $Data/Context/EventLevel$
Channel: $Data/Context/Channel$ UserName: $Data/Context/UserName$
EventNumber: $Data/Context/EventNumber$

The full list here:
http://blogs.technet.com/kevinholman/archive/2007/12/12/adding-custom-information-to-alert-descriptions-and-notifications.aspx

SCOM Rule based notifications

Whilst SCOM can handle a more granular rule/monitor based notification, it currently cannot be done through the UI. Deploy the following code to acomplish that:
http://blogs.msdn.com/jakuboleksy/archive/2007/01/18/notification-subscriptions.aspx
or a powershell veriosn of the same:
http://code4ward.net/cs2/blogs/code4ward/archive/2007/09/19/set-notificationforalert.aspx

SCOM Script Maintenance Mode

Powershell scripts to schedule a computer, or a group to maintenance mode:
http://systemcenterforum.org/wp-content/uploads/CmdSchedMaint.zip

Developing workflow solutions

To start building workflow solutions on SharePoint read the SharePoint Team Blog, the community forum and MSDN technical article by Daniel Odievich and Alireza Etemad Mazaheri.

SCOM MP Guides

Remote Dubuggin SharePoint

Created a share on my client machine on my C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\Remote Debugger folder.
Then I remoted into the SharePoint server and mapped a drive to connect to the share on my client machine.
Open the mapped drive on the server and navigate down the folders to x86\msvsmon.exe and run it on the server through the share.
Once the remote debug monitor is running. Click on tools -> permissions to give the account your logged in as permissions to debug.
You will also need to deploy the PDB file generated by visual studio when it creates your assembly to the GAC as well on the server. You will need to copy via the command line utility or map a drive to it since it is not available through the folder structure in windows. the folder you have to copy the PDB file to is c:\windows\assembly\gac_msil\\__. You will need to replace the three place holders (identified with <>) with the appropiate names for your assembly. Once the PDB file is copied over to that folder location, you are ready to attach and debug
In visual studio, select attach to process from the debug menu
In the "Qualifier" text box enter the netbios name of the server that the remote debugging monitor is running. It should refresh the screen and connect to the remote debugging session on the server. You can verify by going to the server and looking at the remote debugging monitor to see who is connected.
I choose to change the types of code I will be attaching to. I used the "select..." button to remove TSQL from the list since it was causing issues and I wasn't debugging SQL anyway.
Select your process and happy debugging.

SharePoint Logging

Noticed that SharePoint wasnt putting anything into the log files, except :
"Tracing Service lost trace events" messages. This required a restart of the WSS Tracing service.

BTW need to figure out why the Central Admin Diagnostic Settings does not maintain the values of Event Throttling, and where it is saved.