Archive for July, 2011

Export-SCOMEffectiveMonitoringConfiguration

Tuesday, July 26th, 2011

A new cmdlet that allows you to export the effective configuration for an agent. I can’t get the example on the SCOM help file to work but have re-written it below. It will create a seperate csv file for each monitored server. Good Luck!

Read the rest of Export-SCOMEffectiveMonitoringConfiguration »

Avicode becomes APM

Monday, July 25th, 2011
Avicode is now integrated into SCOM 2012 as APM (Application Performance Monitoring) but there are some important caveats.

Upgrade considerations

Saturday, July 23rd, 2011

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.

Read the rest of Upgrade considerations »

Network Device Discovery – one discovery rule per Management Server

Saturday, July 23rd, 2011

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.

New PowerShell cmdlets – All change

Friday, July 22nd, 2011

Some good news. Some bad news.

Good news first – some great new cmdlets, including enable \ disable scomrule and scomonitor. And a real biggie, export-scomeffectivemonitoringconfiguration.

Bad news .. all the scripts have changed. They now have a ‘SCOM’ prefix in the name and the parameters have changed. NewMaintenanceWindow becomse Set-SCOMMaintenanceMode and the parameters have changed.

To bring a hint of good news to proceedings. The SCOM 2007 cmdlets still seem to work. They may well now be classed as deprecated as could well disappear in future versions but at least it looks like we’ll get some extra time to do all the conversions.

Read the rest of New PowerShell cmdlets – All change »

Enable-SCOMRule

Friday, July 22nd, 2011

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

Read the rest of Enable-SCOMRule »

Disable-SCOMRule

Friday, July 22nd, 2011

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

Read the rest of Disable-SCOMRule »

Enable-SCOMMonitor

Friday, July 22nd, 2011

We now have the capability to enable SCOM monitors via PowerShell

Read the rest of Enable-SCOMMonitor »

Disable-SCOMMonitor

Friday, July 22nd, 2011

We now have the capability to disable SCOM monitors via PowerShell

Read the rest of Disable-SCOMMonitor »

Maintenance Mode changes in SCOM 2012

Wednesday, July 20th, 2011

Operations Manager 2012 still doesn’t block placing management servers into maintenance mode. However, the way Management Servers behave when placed into maintenance mode has changed:

  • If a Management Server is placed into Maintenance Mode then the System Center Management Configuration Service will change the agent assignment to force the agents to failover to another management server so data loss will not occur.
  •  

  • In Operations Manager 2007 a Management Server couldn’t take itself out of Maintenance Mode as Maintenance Mode unloads all workflows (including the “End Maintenance Mode” workflow). This has changed in Operations Manager 2012 by assigning the “End Maintenance Mode” workflow to the “All Management Servers” resource pool. This way the workflow will failover to another Management Werver and reload to be able to exit maintenance on the Management Server that was placed into Maintenance Mode.Note: If you only have one Management Server and you place it into Maintenance Mode it will never come out because there is no other Management Server for workflow failover.