locked
Exchange Management Shell run as a service? or speed up launch? RRS feed

  • Question

  • Hello,

    On a (non-production, not in use) Exchange 2010 Mailbox server with 3GB free memory, why does it take 2 minutes to launch Exchange Management Shell?

    If I want to automate some process that is spauned by some other event, how can I do this in some timely fashion without having to wait so long? I understand (and like) the remote powershell, but really... 2minutes?

    Perhaps, if I know that I'll only need command x & Y, can I limit the download? How can I either speed this up, or have remote Exchange management shell running as a service, and issue commands to the already active connection?

    Any help on this would be greatly appreciated.

    --Gene


    • Edited by Gene Laisne Thursday, July 14, 2011 9:04 PM better test
    Thursday, July 14, 2011 8:50 PM

Answers

  • Hi,

    Rather than launch the Exchange Management Shell, I'm going to launch a vanilla PowerShell and use the new-PSSession/import-Session which is much faster.

    Thanks everyone.

    --Gene

    • Proposed as answer by Xiu Zhang Monday, July 18, 2011 6:07 AM
    • Marked as answer by Xiu Zhang Friday, July 22, 2011 7:13 AM
    Friday, July 15, 2011 1:18 PM

All replies

  • I've seen a few instances where changing the number of recipients can increase the response.
    An example here: http://www.petri.co.il/forums/showthread.php?t=27364

    This URL shows you how to change those via EMC: http://www.ntweekly.com/?p=


    Friday, July 15, 2011 6:44 AM
  • Yes also EMC takes a while to open up. I normally keep EMS and EMC both open. ( You can either disconnect or keeping it running)

     

     

    Friday, July 15, 2011 7:00 AM
  • Hi,

    Have a look at the article below:

    Speeding Up PowerShell Startup - Updating Update-Gac.ps1

    http://blogs.msdn.com/b/powershell/archive/2008/09/02/speeding-up-powershell-startup-updating-update-gac-ps1.aspx

    Xiu

    Friday, July 15, 2011 8:26 AM
  • xiu, the update gac doesn't do anything in this situation, It's the remoting part that is slow. I have several systems and using a control, the update gac didn't do anything. I think that's just a general PowerShell thing and not specific to Exchange 2010

    Also, Kris, that change would speed up commands, but my issue isn't the running of the commands, it is the execution of the Management Shell to begin with.

     

    If I have a process that automates the creation of mailboxes and I have to do 30 of them, I don't want it to have to take an extra hour to do that, nevermind the 40 seconds it takes to disable & enable the user.

    Thanks for responding,

    --Gene

    Friday, July 15, 2011 1:06 PM
  • Hi,

    Rather than launch the Exchange Management Shell, I'm going to launch a vanilla PowerShell and use the new-PSSession/import-Session which is much faster.

    Thanks everyone.

    --Gene

    • Proposed as answer by Xiu Zhang Monday, July 18, 2011 6:07 AM
    • Marked as answer by Xiu Zhang Friday, July 22, 2011 7:13 AM
    Friday, July 15, 2011 1:18 PM