Friday, 18 January 2013

Enabling Exchange Cmdlets in Powershell

In order to run Exchange Server commands within a Powershell script, the relevant cmdlets need to be 'called' within Powershell.

This is accomplished with the following line, which is found at the start of nearly all of my Powershell scripts.

#Enable Exchange cmdlets
add-pssnapin *exchange* -erroraction SilentlyContinue

 If you attempt to run Exchange commands in Powershell (eg. Get-Mailbox) without loading the Exchange cmdlets first, you will get an error similar to the following;
The term 'get-mailbox' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:12
+ get-mailbox <<<< 
    + CategoryInfo          : ObjectNotFound: (get-mailbox:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException


Posted by at
Labels: , , , , , , ,

32 comments:

  1. Adrian Hayes26 July 2013 at 07:30

    Thank you! That did the trick.

    ReplyDelete
  2. Anonymous12 June 2014 at 07:16

    Of course, you need to have the Exchange management tools installed as well. Otherwise your script silently continues but does nothing.

    ReplyDelete
  3. Anonymous7 August 2014 at 05:08

    You are a lifesaver! I had to run this within my Exchange Shell on my Exchange 2013 server in order to get the Exchange commands to work. I have no idea why it doesn't run automatically!

    ReplyDelete
  4. Anonymous7 August 2014 at 16:29

    this is the best solution ever.
    Thank you Peter

    ReplyDelete
  5. Khalid Rehan3 September 2014 at 15:55

    It worked

    ReplyDelete
  6. Anonymous8 October 2014 at 05:06

    YES!!!!!

    ReplyDelete
  7. Anonymous12 November 2014 at 02:00

    Thank you !

    ReplyDelete
  8. Anonymous6 December 2014 at 00:19

    I have been searching the solution for hours. Thank You!!!

    ReplyDelete
  9. Anonymous27 January 2015 at 22:46

    Thanks, was looking for this, can it harm if i set it on top of all my exchange PS1 scripts?

    ReplyDelete
  10. Anonymous26 February 2015 at 03:51

    thanks !!!!

    ReplyDelete
  11. Anonymous20 March 2015 at 22:06

    thx, so much.

    ReplyDelete
  12. Anonymous25 May 2015 at 12:02

    It worked. Thanks!!

    ReplyDelete
  13. Anonymous5 November 2015 at 06:03

    Thanks. this did the trick

    ReplyDelete
  14. Chris A11 March 2016 at 23:28

    You are a fucking legend. Same issue as anonymous, my Exchange shell no longer loads this and i was FREAKING OUT!!!! Thank you SOOOOO much!

    ReplyDelete
  15. Anonymous21 April 2016 at 22:34

    thanks!!!

    ReplyDelete
  16. carmel19892 June 2016 at 22:50

    Thank you so much!!!

    ReplyDelete
  17. Anonymous5 September 2016 at 21:40

    Thanks!!!!! so much, was searching for solution like this

    ReplyDelete
  18. afripino16 September 2016 at 07:00

    Thank you thank you thank you!!!!!! This fixed my problem with remotely administering exchange through powershell!!!

    ReplyDelete
  19. Anonymous18 October 2016 at 06:19

    Thank you very much for the tip. It worked well, but after a restart again I have to use this commands to enable cmdlets. Any way to keep it permanent? Thanks again.

    ReplyDelete
    Replies
    1. Peter Morrissey18 October 2016 at 13:33

      You would need to add the cmdlet to your powershell profile
      Here's some info in the link below:
      http://www.howtogeek.com/50236/customizing-your-powershell-profile/

      Delete
  20. Unknown24 March 2017 at 22:01

    Awesome job, thank you.

    ReplyDelete
  21. Anonymous4 May 2017 at 00:24

    BEST man, THE BEST, thanks very much.

    ReplyDelete
  22. Unknown23 June 2017 at 23:28

    Searched far and wide for this! thanks

    ReplyDelete
  23. Anonymous17 August 2017 at 18:10

    i love you dude, thanks so much!

    ReplyDelete
  24. Unknown10 October 2017 at 02:50

    i love you dude, thanks so much!

    ReplyDelete
  25. Anonymous27 October 2017 at 05:33

    Thank you from the Netherlands! ;)

    ReplyDelete
  26. Unknown8 March 2018 at 18:38

    Thank you in 2018!!

    ReplyDelete
  27. Unknown20 July 2018 at 21:58

    Thank you it worked for me on 2010 Exchange

    ReplyDelete
  28. AI23 August 2019 at 10:16

    THIS WORKED

    On-prem exhange 2008 server - get-mailbox cmdlet not recognized
    -Opened elevated powershell then ran add-pssnapin *exchange* -erroraction SilentlyContinue
    Get-mailbox worked!

    thank you!!

    ReplyDelete
  29. Dan7 November 2019 at 22:47

    god knows what causes this, but thank you!

    ReplyDelete
  30. Ken27 December 2019 at 08:41

    Wow! Thank you so much. So many complicated options out there but this was very simple and precise.

    ReplyDelete
  31. Anonymous2 November 2021 at 05:13

    Same here. This solution from Peter WORKED for me on Exchange 2013. Thanks Peter --Ike E.

    ReplyDelete

Subscribe to: Post Comments (Atom)