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