Getting started!

  1. Download the .msi and run it
  2. If you had PS running when you installed the .msi, restart PS
  3. Then run "PS> Import-Module SMLets"

Your now ready to use the module.

To learn what's in the module, run the following command:

To learn which parameters a cmdlets makes use of, run the following command:
PS>Get-Help Get-SCSMClass
Note: Replace Get-SCSMClass with the cmdlet you want to get parameters for.

To run commands remotely, make use of the -ComputerName parameter.

Last edited Oct 22, 2013 at 6:13 PM by radtravis, version 6


TheoK Mar 5, 2014 at 10:15 AM 
The -ComputerName parameter isn't present in the Add-SCSMRequestOffering CmdLet.

RobertHenry Apr 5, 2012 at 5:40 PM 
Correct me if I'm mistaken, but I believe above command will fail if you run it in a "Service Manager Shell" Powershell session due to overlap with the native cmdlets for SCSM in RC and up. Running the latest bits I have to run the import-module command from a plain Powershell session or I get errors and it appears to fail.

radtravis Apr 21, 2011 at 4:00 AM 
Thanks for pointing this out Lai. I have updated the documentation to fix these errors and to adjust the instructions for Beta 3 which now has an .msi installer.

Lai Jan 11, 2011 at 3:58 AM 
The PS command is "get-help" not "get-hep" as stated above under the "To learn which parameters..."

Lai Jan 11, 2011 at 3:18 AM 
Thanks to Travis Wright for this very important correction. After many failed attempts to import---I am now able to import the module. Number 5 shows that you should type SMLetes when it should be SMLets. No "e." It also shows this in the "Read-Me Notepad" window in the folder.

Please make a note or any changes. There is only one "e" in SMLets.