Marcelo Guterres's Blog

Creating a Performance Rule to collect SCCM SQL Service Broker Queue

Marcelo Guterres — Wed, 06 Sep 2017 17:44:56 GMT

Hi everyone! Sometimes we need get some information that SCOM don't collect for us natively. The SCCM Broker queue is an example. I'll show you with few steps how to create a view like this: The first step is create a script to get all information that you need. The script below need some changes, please pay attention to change all BOLD values.

Dim objCN
Dim strConnection
Dim oAPI, oBag
Set oAPI = CreateObject("MOM.ScriptAPI")
Set oBag = oAPI.CreatePropertyBag()
Set objCN = CreateObject("ADODB.Connection")
strConnection = "Driver={SQL Server};Server=SQLSERVERNAME\INSTANCE;Database=DATABASENAME;Trusted_Connection=TRUE"
objCN.Open strConnection
Dim strSQLQuery
strSQLQuery = "SELECT COUNT(*) as value FROM [dbo].[ConfigMgrDRSQueue] WITH(NOLOCK)"
Dim objRS
Set objRS=CreateObject("ADODB.Recordset")
Set objRS = objCN.Execute(strSQLQuery)
valor = objRS.Fields("value")
Call oBag.AddValue("PerfValue",CDbl(valor))
Call oAPI.Return(oBag)

The second step is create a Collection Rule to get the values of each queue. Go to Authoring > Management Pack Objects > Rules, and select the template Probe Based > Script (Performance), like the picture below: Select the destination Management Pack and click Next. Give a name to the Rule and choose the target the Windows Computer Class. VERY IMPORTANT: Uncheck the "Rule is enable". Give a name to the script. Don't forget the ".vbs" in the end. Paste the script with all needed alterations and click Next. In performance mapping information put your values but don't change the last item $Data/Property[@Name='PerfValue']$. Save the Rule. The third step is create a Override to enable the Rule to the Windows Computer of the SQL Server that have the SCCM Broker. The last step is create a Performance View and select all Rule that you have created with the steps above. Enjoy!!!

Enabling ACS Forwarder by filter

Marcelo Guterres — Wed, 20 Apr 2016 10:01:02 GMT

On Large environments it's very common use Audit Collection Service. With the powershell script below, it's possible enable ACS Forwarder automatically. This is the "Monitoring" workspace on SCOM Console showing ACS Views:

The Collector Server in my lab: My Forwarders. I don't have any at the moment: The script below has two parameters for change: "$collectorName = 'Name of your Collect Server' " and "($Object -like '*String for filter the servers*')" Below you can see the script code. It's a very simple script:

$collectorName = 'LAB-SCOM02.mgs.lab'
$override = new-object Hashtable
$override.Add('CollectorServer',$collectorName)
$healthServices = Get-SCOMClass -Name 'Microsoft.SystemCenter.HealthService'| Get-SCOMMonitoringObject
$EnableAcsTask = Get-SCOMTask | Where {$_.Name -eq 'Microsoft.SystemCenter.EnableAuditCollectionService'}
write-host $EnableAcsTask
foreach($Object in $healthServices){
if ($Object -like '*SQL*'){
write-host $Object
Start-SCOMTask -Task $EnableAcsTask -Instance $Object -Override $override
}
}

I execute using the filter "SQL" for enable ACS Forwarder at any server with the string "SQL" at the name: Now I can see at the "Forwarder State View" the server LAB-SQL01: I create this script for using like an example when you have a lot of servers for enable ACS Forwarder. It's possible increase the script for enable automatically using many strings for filter and running with a Schedule Task.

A simple way to test a lot of SCCM distribution point availability with System Center Operations Manager

Marcelo Guterres — Mon, 18 Apr 2016 23:39:31 GMT

Hi everyone! This is a simple way to monitor a URL of a SCCM Distribution Point. I have some customers with a necessity of a visualization about Distribution Point health. The customer has a lot of Distribution Points and a big problem with authentication for remote url tests. So, is not my first option create a "Web Application Availability Monitoring" for each "URL" for each "Distribution Point" (the customer has a thousands distribution points). The simple way for this object is test the URL locally. How is this possible? I created a monitor with the script below: Script VBS:

Option Explicit
Dim objWinHttp
Dim strCheckURL
Dim oAPI
Dim oBag
Set oAPI = CreateObject("MOM.ScriptAPI")
Set oBag = oAPI.CreatePropertyBag()
strCheckURL = "https://localhost/sms_dp_smspkg$/cas00001"
Set objWinHttp = CreateObject("WinHttp.WinHttpRequest.5.1")
objWinHttp.SetTimeouts 29000, 29000, 29000, 29000
objWinHttp.Open "GET", strCheckURL
On Error Resume Next
objWinHttp.Send()
If Err.number = 0 Then
If (objWinHttp.Status = 200) Then
Call oBag.AddValue ("Status","OK")
End If
else
If (objWinHttp.Status <> 200) Then
Call oBag.AddValue ("Status","Error")
End If
End If
Set objWinHttp = Nothing
oAPI.Return(oBag)

The URL showed above change on each SCCM environment because the name of the SCCM Client package. I created an override for the monitor pointing to the "ConfigMgr Distribution Point" class. With this target all new Distribution Point with the Operations Manager Client will be automatically monitored. It's simple but very useful!