OpsMgr Shell: Another advanced example of PowerShell and the SDK

Here's another post on advanced usage of the OpsMgr SDK and PowerShell. As I get into more complicated things, it seems I keep running into .NET Generics and collections more and more.

I had quite the time when I came across a read-only collection, and needed to edit it. Fortunately, Jaykul, Oisin and Bruce Payette all came to my rescue.

The result is HERE, where I show:
1. How I am handed a read-only collection by the OpsMgr SDK.
2. I recreate a new generic list with just the elements I want from that read-only collection.
3. Then recreate that read-only collection using my new list.

Wow!

OpsMgr Shell: Advanced example using PowerShell and the SDK

I've got a new post up HERE on the System Center Forum site.

The title is "Advanced example using PowerShell and the OpsMgr SDK: Creating and Updating Groups". I basically translate a post from Jakub Olesky HERE.

I'm going to do a few more related blog posts where I split the above code into two functions/scripts.

OpsMgr Shell: OpsMgr Automation Introduction--Part 2

I first blogged HERE about starting a short series on OpsMgr Automation.

I covered the simple get-alert cmdlet in the series introduction post, and now have the second part up on the System Center Forum site HERE.

In the second part, I demonstrate PowerShell’s native .NET functionality by using the OpsMgr SDK .NET assemblies directly from a PowerShell console.

Go to the above link for the full article.

PowerShell in OpsMgr 2007 R2 (beta 1)--Operations Manager Shell

Recently, Microsoft released System Center Operations Manager 2007 R2. This is *not* a SP release, but a new product. I won't go into the licensing details of this as others have covered it, and a search should get you answers.

I haven't seen anyone actually mention PowerShell at all when discussing the new release.

I'm going to try to spend some time this week and next looking for any PowerShell-related changes.

One thing to note at this point is that the "Command Shell" (see note 1 below) appears to have been renamed to "Operations Manager Shell". The decision was likely to follow along with Exchange, where they have their PowerShell extension named "Exchange Management Shell" or "EMS".

As a result, I'm now going to start using the tag "OpsMgr Shell" when referring to the OpsMgr R2 release, and likely any future releases of OpsMgr down the road likely in 2010 or so (that's nothing official or unofficial... I'm just throwing that date out there).

Note 1: The OpsMgr custom PowerShell console pre-loaded with the OpsMgr PowerShell extensions.