Archive

Archive for March, 2012

New Dashboards and SharePoint Integration

March 7, 2012 1 comment

SCOM 2012 beta sees some snazzy new dashboards including a Network Summary Dashboard and a Management Group Health Dashboard. Even better, you can create your own dashboards and then display them via SharePoint.

 

Network Summary Dashboard

Creating Dashboards

I’ll run through creating dashboards in a future article but here is the official documentation.

http://technet.microsoft.com/en-us/library/hh227265.aspx

Integration with SharePoint 2010

I’ve found the integration with SharePoint 2010 to be straight forward to setup. I’ll run through some screen shots in a future article but here is the official documentation.

http://technet.microsoft.com/en-us/library/hh205998.aspx

Here is the Network Summary Dashboard in SharePoint 2010

Advertisements

Avicode becomes APM

March 7, 2012 3 comments
Avicode is now integrated into SCOM 2012 as APM (Application Performance Monitoring) but there are some important caveats.
 
1) SCOM 2012 will support web applications \ services running on IIS7 only. There is no IIS6 support.
2) You cannot use the Avicode 5.7 Managementy Packs in SCOM 2012. There are new APM management packs which are part of the download but not installed by default.
3) The Intercept Service becomes the System Center APM Service. This is disabled by default but enabled when you start APM monitoring on a server.
4) The Avicode databases, consoles and reports are now integrated into the Operations Manager databases, console and reporting.
  • SE Viewer becomes a resource utilisation web page with the same drill down capabilities SE Viewer
  • New views for managing APM agents Monitoring View
  • Alert Context for Alert details Alert Context

5) Avicode SE Viewer and SE Advisor are still available

6) A new security role to view the APM web consoles

7) For Client Side Monitoring, the CSM Collector is now always local

Upgrade considerations

March 7, 2012 1 comment

Just a quick heads up on a couple of items that need to be considered if you will be looking to upgrade OpsMgr 2007 R2 to SCOM 2012 at some future date.

 

In SCOM 2012:

1) There is no support for windows 2000. You won’t be able to upgrade SCOM 2007 agents on Windows 2000 and you won’t be able to install SCOM 2012 agents on Windows 2000.

2) Management Servers must be Windows 2008 R2 or later

3) SQL Server needs to be SQL 2008 SP1 or SQL 2008 R2

4) All SCOM 2007 R2 agents must have cumulative update 4 or later applied

The full list is here – http://technet.microsoft.com/en-us/library/hh205990.aspx

Network Device Discovery – one discovery rule per Management Server

March 7, 2012 1 comment

In SCOM 2012, A Management Server can only run one network device discovery rule. So if you already have one network device discovered, when you try and create a new discovery rule you won’t have any Management Servers available.

You’ll either need to:

– edit the original discovery rule to cover both network devices

– add another Management Server

http://technet.microsoft.com/en-us/library/hh278846.aspx

“Each management server or gateway server can run only one discovery rule. You specify a single management server or gateway server to run the discovery rule and a management server resource pool to perform the actual monitoring of the network devices.”

Kevin Holman does a great walk-through here.

Enable-SCOMRule

March 7, 2012 1 comment

We now have the capability to enable SCOM Rules using PowerShell.

 

$MS=”XXXX” $MaPName=”XXXX” $ClassName=”Windows Server 2008 R2 Operating System” $RuleName=”Performance registry corruption”

if ((Get-PSSnapin | Where-Object {$_.Name -eq ‘Microsoft.EnterpriseManagement.OperationsManager.Client’}) -eq $null) { Write-Host Write-Host “File loaded.” Write-Host “Initializing shell for operations manager…” Write-Host “Add Microsoft.EnterpriseManagement.OperationsManager.Client snap in.” Add-PSSnapin Microsoft.EnterpriseManagement.OperationsManager.Client -ErrorAction SilentlyContinue -ErrorVariable Err

if ($Err) { $(throw write-Host $Err) } }

if ((Get-ManagementGroupConnection | Where-Object {$_.ManagementServerName -eq $MS}) -eq $null) { Write-Host “Connect to Management Server: $MS” New-ManagementGroupConnection $MS -ErrorAction SilentlyContinue -ErrorVariable Err if ($Err) { $(throw write-Host $Err) } }

if ((Get-PSDrive | Where-Object {$_.Name -eq ‘Monitoring’}) -eq $null) { Write-Host “Create Monitoring drive from Provider.” New-PSDrive -Name: Monitoring -PSProvider: OperationsManagerMonitoring -Root: \ -ErrorAction SilentlyContinue -ErrorVariable Err

if ($Err) { $(throw write-Host $Err) } Write-Host “Operations manager shell initialized.” Write-Host }

Set-Location Monitoring:\$MS

$MP = Get-SCOMManagementPack -displayname $MPName | where {$_.Sealed -eq $False} $Class = Get-SCOMClass -DisplayName $ClassName $Rule = Get-SCOMRule -DisplayName $RuleName Enable-SCOMRule -Class $Class -ManagementPack $MP -Rule $Rule -Enforce

Disable-SCOMRule

March 7, 2012 1 comment

We now have the capability to disable SCOM Rules using PowerShell.

 

$MS=”XXXX” $MPName=”XXXX” $ClassName=”Windows Server 2008 R2 Operating System” $RuleName= “Performance registry corruption”

if ((Get-PSSnapin | Where-Object {$_.Name -eq ‘Microsoft.EnterpriseManagement.OperationsManager.Client’}) -eq $null) { Write-Host Write-Host “File loaded.” Write-Host “Initializing shell for operations manager…” Write-Host “Add Microsoft.EnterpriseManagement.OperationsManager.Client snap in.” Add-PSSnapin Microsoft.EnterpriseManagement.OperationsManager.Client -ErrorAction SilentlyContinue -ErrorVariable Err

if ($Err) { $(throw write-Host $Err) } }

if ((Get-ManagementGroupConnection | Where-Object {$_.ManagementServerName -eq $MS}) -eq $null) { Write-Host “Connect to Management Serve

Enable-SCOMMonitor

March 7, 2012 1 comment

We now have the capability to enable SCOM monitors via PowerShell

 

$MS=”XXXX” $MPName=”XXXX” $ClassName=”XXXX” $MonitorName=”XXXX”

if ((Get-PSSnapin | Where-Object {$_.Name -eq ‘Microsoft.EnterpriseManagement.OperationsManager.Client’}) -eq $null) { Write-Host Write-Host “File loaded.” Write-Host “Initializing shell for operations manager…” Write-Host “Add Microsoft.EnterpriseManagement.OperationsManager.Client snap in.” Add-PSSnapin Microsoft.EnterpriseManagement.OperationsManager.Client -ErrorAction SilentlyContinue -ErrorVariable Err

if ($Err) { $(throw write-Host $Err) } }

if ((Get-ManagementGroupConnection | Where-Object {$_.ManagementServerName -eq $MS}) -eq $null) { Write-Host “Connect to Management Server: $MS” New-ManagementGroupConnection $MS -ErrorAction SilentlyContinue -ErrorVariable Err if ($Err) { $(throw write-Host $Err) } }

if ((Get-PSDrive | Where-Object {$_.Name -eq ‘Monitoring’}) -eq $null) { Write-Host “Create Monitoring drive from Provider.” New-PSDrive -Name: Monitoring -PSProvider: OperationsManagerMonitoring -Root: \ -ErrorAction SilentlyContinue -ErrorVariable Err

if ($Err) { $(throw write-Host $Err) } Write-Host “Operations manager shell initialized.” Write-Host }

Set-Location Monitoring:\$MS

$MP = Get-SCOMManagementPack -displayname $MPName | where {$_.Sealed -eq $False} $Class = Get-SCOMClass -DisplayName $ClassName $Monitor = Get-SCOMMonitor -DisplayName $MonitorName Enable-SCOMMonitor -Class $Class -ManagementPack $MP -Monitor $Monitor -Enforce