SCOM: Alert Generating Rules vs Collection Rules
A quick Google search didn't yield a quick explanation of this, so I'll quickly describe the difference.
Alert Generating Rule:
A rule setup that generates an alert that shows up in the active alerts. It stays in a "New" state until it's modified by a script or manually closed.
Collection Rules:
A rule setup that collects information and can be displayed via the "Event" view. These rules don't generate alerts but allow for reporting via the event view and via the datawarehouse.
Schedule a URL into Maintenance Mode
Found a nice article about how to script a URL (or web application) into maintenance mode. This was a little bit of a challenge to find so I'm reposting it to hopefully get some more attention. I've also posted the modified version of the script that allows for multiple watcher hosts.
param($rootMS,$urlName,$minutes,$comment,$reason)
Add-PSSnapin "Microsoft.EnterpriseManagement.OperationsManager.Client" -ErrorVariable errSnapin;
Set-Location "OperationsManagerMonitoring::" -ErrorVariable errSnapin;
new-managementGroupConnection -ConnectionString:$rootMS -ErrorVariable errSnapin;
set-location $rootMS -ErrorVariable errSnapin;
$URLWatcher = (Get-MonitoringClass -name Microsoft.SystemCenter.WebApplication.Perspective) | Get-MonitoringObject | where {$_.DisplayName -eq $urlName}
$startTime = [System.DateTime]::Now
$endTime = $startTime.AddMinutes($minutes)
"Putting URL into maintenance mode"
foreach ($name in $URLWatcher) {
New-MaintenanceWindow -startTime:$startTime -endTime:$endTime -monitoringObject:$name -comment:$comment -Reason:$reason }
Usage:
C:WINDOWSsystem32WindowsPowerShellv1.0powershell.exe URLMaintenanceModeV4.ps1 -rootMS: `SCOMRMS1′ -urlName: ‘MSN Website Checker’ -minutes:45 -comment: ‘My Comment’ -reason: ‘PlannedOther’
http://www.scom2k7.com/schedule-a-into-url-maintenance-mode/
OpsMgr 2007 – No graphs in emailed reports
Some of you may have found that there are no graphs in your emails (scheduled reports) from SCOM 2007. I posted this up on the MSMOM email distro and Kevin Holman pointed me to a KB article.
http://support.microsoft.com/kb/972821
Just add this to your ReportingServicesService.exe.config file in the ReportServerbin
<dependentAssembly> <assemblyIdentity name="Microsoft.ReportingServices.ProcessingCore"publicKeyToken="89845dcd8080cc91" culture="neutral" /> <bindingRedirect oldVersion="9.0.242.0" newVersion="10.0.0.0" /> </dependentAssembly> <dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1"> <assemblyIdentity name="Microsoft.ReportingServices.ProcessingCore"publicKeyToken="89845dcd8080cc91" culture="neutral" /> <bindingRedirect oldVersion="9.0.242.0" newVersion="10.0.0.0" /> </dependentAssembly>
Place this between the tags:
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> </assemblyBinding>
OpsMgr 2007 – Author Privileges
Have you run into setting up permissions/privileges for your administrators within the scom console. This can be quite confusion. You often run into cryptic areas where certain functions don't react as they should and you run into the error "The user domainuser does not have sufficient permission to perform the operation".
Some important information here:
Greyed out Domain Controllers
I spent a while searching around for this gem. Basically the domain controllers don't trust the local system account so you have to run the HSLockdown.exe tool. I found this blog article that explains:
http://scug.be/blogs/scom/archive/2008/08/18/opsmgr-agent-greyed-out-on-domain-controller.aspx
