In SCOM 2007 (R2) you had a problem when you put your RMS into Maintenance Mode,

because this meant the workflow ‘Stop Maintenance Mode’ which ran on the RMS,

was actually unloaded

So this meant your RMS actually would never come out of Maintenance Mode ;-(

You had to manually get it out of Maintenance Mode, normally using the “End Maintenance Mode” Console Task.

In SCOM 2012, because of its more distributed architecure, the “Stop Maintenance Mode” workflow will actually be moved to another Management Server, when the MS that currently runs this, is put into Maintenance Mode.

The only thing you need to do, is make sure you never put more then 50% of your Management Servers into Maintenance Mode, because this makes your Resource Pool unusable.

Here’s a slide from the CEP Presentation I attended:

So yet another nice new feature to expect!

]]>https://windowspowered.wordpress.com/2011/09/09/management-server-maintenance-mode-in-scom-2012/feed/1alexvgemstscom2012MS_MMAdd Permissions on Files and Folders using PowerShellhttps://windowspowered.wordpress.com/2011/08/22/add-permissions-on-files-and-folders-using-powershell/
https://windowspowered.wordpress.com/2011/08/22/add-permissions-on-files-and-folders-using-powershell/#respondMon, 22 Aug 2011 13:03:41 +0000http://windowspowered.wordpress.com/?p=86Continue reading →]]>Seems very simple, but I had to puzzle a little to get it working,

here’s a small function I came up with, maybe it will save you some time,

]]>https://windowspowered.wordpress.com/2011/08/22/add-permissions-on-files-and-folders-using-powershell/feed/0alexvgemstOperations Manager 2012 Command Shell revampedhttps://windowspowered.wordpress.com/2011/07/28/operations-manager-2012-command-shell-revamped/
https://windowspowered.wordpress.com/2011/07/28/operations-manager-2012-command-shell-revamped/#respondThu, 28 Jul 2011 10:39:20 +0000http://windowspowered.wordpress.com/2011/07/28/operations-manager-2012-command-shell-revamped/Continue reading →]]> 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:

example:

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!

"None – in this mode, print driver components are loaded into the spooler process. This is essentially the model found in previous versions of Windows

Shared – multiple drivers that are set for isolation are loaded into a single shared process space that is separate from the spooler process (PrintIsolationHost.exe) . Although this protects the spooler process, the drivers that are in shared mode can affect one another

Isolated – each driver is loaded into its own process space. This protects the spooler from individual driver failures, and also protects drivers from each other "

Basically the idea is this, at least this is probably how I would set it up:

-Run all well behaving drivers as ‘Shared’ (default)-Run bad drivers as ‘Isolated’ if no suitable replacement is available -Don’t run drivers in ‘None’, if necessary move those to separate server if you want a stable solution !

One approach for new drivers would be to start them off as ‘Isolated’,

and when proven innocent, ‘upgrade’ them to shared.

(The shared mode saves system resources as fewer isolation processes are needed).

On systems that don’t host a lot of print queues you could consider running them all isolated,

if resources are a non-issue.

Not all drivers will support isolation, I hope all companies that create Windows printer drivers will make them

compatible asap, so we can use it for all printers, to prevent problems, and have more control over our Print Servers.

The global settings can be managed using GPO, where you can disable or enable PDI,