System Center 2012 Configuration Manager –WHERE ARE MY CMDLETS in Service Pack 1 !??!?!

That was my reaction.  I went through the headache of updating to Service Pack 1 in my Lab environment to get the best features of all, the Powershell Cmdlets.

Then I started looking.

No Shortcut to the Cmdlets

No Registered Module

No helpful little line stating “Cmdlets over HERE!”

But everywhere online  I see the praises of “Service Pack 1 for Configuration Manager” and the MIGHTY POWERSHELL CMDLETS! …. But not a one to be found.

….grumble grumble grumble…

So I did some poking about and it turns out they are installed but just well…. left in the background.  Like you’d never need them.  HARUMPH!  Some Developer needs a spanking for this!

So to SAVE you the headaches I had you will NOT see a shortcut for Powershell for System Center 2012 Config Man.   Don’t try, there is no magic “Oh I forgot to click this button.” It’s not there.

But you can get to it.   The module is sitting under the BIN folder in your Config Man folder under Program Files.  On my test lab it was

‘C:Program Files (x86)Microsoft Configuration ManagerAdminConsoleBin’

To load the module you’ll have to run this little line in Windows Powershell

IMPORT-MODULE ‘C:Program Files (x86)Microsoft Configuration ManagerAdminConsoleBinConfigurationManager.psd1’

…and the world of Cmdlets for Config Man will open up.

You can verify this afterwards by executing the following Cmdlet

GET-COMMAND –module ConfigurationManager

which will show you a massive pile of goodies available at your fingertips.

If you’d like a shortcut for this (something a ‘Certain Team’ at Microsoft forgot to provide… Bad Bad Bad Bad!!!!) just run this line in Windows Powershell to create one in a default folder called “C:Foo”

$sh=New-object –comobject



$lnk.Arguments="-command `"{ IMPORT-MODULE ‘C:Program Files (x86)Microsoft Configuration ManagerAdminConsoleBinConfigurationManager.psd1 }`""


There.   Now stop banging your head on the shiny spot on your desk.  It’s all better Smile

The Energized Tech

Systems Center 2012 Orchestrator –My Wishlist for Powershell

I write this today as I have fallen in love with something really cool.  Automation to the EXTREME!

Systems Center Orchestrator 2012.    And this new fascination is enhanced over the top by it’s ability to internally leverage Powershell!

Excuse me for a minute while I wipe up this puddle of drool on the floor.

For those of you not aware, Systems Center 2012 Orchestrator is a massive workflow system that is EASY to use and gives you the ability to translate many IT Processes for managing your Infrastructure into solid workflows that can allow you to be many places at once, without actually BEING there.

Now the fact I can also get these workflows to work with my OTHER most favorite thing on the planet, POWERSHELL, is even better!

But I know there are little ears out there listening saying “What we do to improve?”

Little ears listen well and listen now.  It’s so EASY to improve!  Here’s what Systems Center Orchestrator 2012 needs to REALLY just start me singing.  (Warning!  Ask Jeffrey Snover as THIS HAS HAPPENED IN THE PAST!)

1. Integrate the Editor for Editing Powershell Scripts INTO the Powershell ISE

2.Allow Powershell Variables to be “AutoPublished” (whether this is a list to click on or something that can “prepopulate” the Publish field for the bus, don’t care)

3.Tie in the Powershell ISE into the Runbook tester to allow a more granular testing of the internal script structure

You see it won’t take much to send this over the top.    Presently, editing internal Powershell scripts in Orchestrator when I am used to having an ISE is painful.  Troubleshooting is worse.   Editing…. Well Notepad even has CTRL-Z.

But I know you can do this.  You have the ability and the power to improve Automation in a way that nobody else can.  I put this to you Systems Center 2012 team.   Make this happen and make Orchestrator 2012 go out and Kick ass in a way that nobody has EVER imagined!

”The Energized Tech”