Jason,
PowerShell v3.0 has module auto-loading enabled by default. Unfortunately, this only works for modules that are in the $env:PSModulePath variable. To load the ConfigMgr 2012 PowerShell module, use this: Import-Module -Path e:\path\to\sccm\install\adminconsole\bin\ConfigurationManager.psd1; The .psd1 file is what's called a PowerShell "module manifest," which contains a variety of information about the module inside a HashTable. There are other methods of importing modules (eg. pointing to a .psm1 file, a DLL, or even a .ps1 file), but it just so happens that the ConfigMgr team decided to use a module manifest. Cheers, Trevor Sullivan <http://trevorsullivan.net/> <http://twitter.com/pcgeek86> <http://facebook.com/trevor.sullivan> <https://plus.google.com/106658223083457664096> From: [email protected] [mailto:[email protected]] On Behalf Of Jason Condo Sent: Friday, May 10, 2013 8:38 AM To: [email protected] Subject: [mssms] Silly question about PowerShell and ConfigMgr 2012 How do you load the PowerShell modules so you can run scripts? I am pulling up the PowerShell ISE and don't see any of the xxx-CMxxxxxx commands available. I am running from a 2012 primary site server with SP1 and CU1 and the console installed so I would expect the PowerShell extensions for ConfigMgr to be there. Everything I see says you just need the console installed but I don't see them on the server or my laptop with 2012 sp1 and cu1 installed. OpsMgr and VMM both have their own PowerShell environment. Is there something more I need to install? Jason Condo
<<image001.gif>>
<<image002.gif>>
<<image003.gif>>
<<image004.gif>>
