To install the cmdlets:

  1. Extract the downloaded zip archive
  2. Open the powershell window as administrator
  3. Move to the directory where you extracted archive
  4. Execute deploy.ps1 (this will "install" the assembly and load the snap-in)

Note: To load the snap-in manually the next time you open the powershell window, write: "Add-PSSnapIn smcomlets"

Your now ready to use the cmdlets.

To learn how to use each cmdlet you can get help from the powershell window by writing:
  • Get-Help Get-SCSMIncident
  • Get-Help Set-SCSMIncident
  • Get-Help New-SCSMIncident

Note: There is a hidden property "-ServerName" in the cmdlets which gives you the possibility to execute them remotly. If "-ServerName" isn't passed the cmdlets targets localhost.

Last edited May 31, 2010 at 8:05 PM by Sundqvist, version 2

Comments

RobertHenry Apr 5, 2012 at 4: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 3: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 2: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 2: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.