I took a first peak at the SCOM 2012 Beta, and was interested in the announced new PowerShell CmdLets for Operations Manager 2012 of course !
Here’s some stuff I noticed after playing around a bit:
All CMDLets have the ‘SCOM’ identifier in it, according to the documentation it should be ‘SC’, possibly this will change in the future, I’m not sure which one it’s gonna be.
Also the CmdLets are implemented in a Powershell 2.0 compliant ‘Module‘, not in a PoSh 1.0 ‘Snap-In’.
The module is automatically loaded if you start the ‘Operations Manager Shell’ using the default shortcut in the Start Menu.
You can load it yourself in PowerShell using the command: ‘Import-Module OperationsManager’
There are various totally new CmdLets, like ‘Get-SCOMGroup’ for example
Get-SCOMGroup –DisplayName *Agent*, *Windows*
displays all SCOM Groups with the specified Displaynames:
You can create temporary and permanent connections to a Management Group.
Temporary connections mean you can specify a computername.
By the wayhis can be any Management Server now, because they all run the Data
Acess service,the RMS role is basically gone,
And you can specify credentialswith the CmdLets:
Get-Agent -ComputerName MyMgmtServer –Credential (Get-Credential)
Permanent connections is more like the connections we’re used to make in Ops Mgr 2007.
The ‘Get-SCOMAlert’ CmdLet seems to be revamped, it’s got a lot of default parameters, in OpsMgr 2007 we had to use the ‘-Criteria’ switch a lot, which could be a bit clumsy in my experience:
The Install-SCOMAgent CmdLet seems to have improved.
There is no need to first perform a discovery like in Ops Mgr 2007 (R2).
Also you can specify an ActionAccount (which performs the deployment so needs Administrative permissions on the to-be Agent)
And also an ‘AgentActionAccount ‘, this is the account the Agent will use by default, if not specified Local System is used:
(Just specifying this because it’s slightly confusing)
Anyway these are my very first findings of the new Ops Mgr 2012 PowerShell Module.
O yeah, it still seems possible to load the ‘Old’ OpsMgr 2007 R2 PowerShell Snap-In, so your old scripts won’t break I suppose, and you can migrate them to the New style at your own pace!