Exchange Management Shell (EMS) missing after applying Exchange 2010 SP1


Problem: After installing Service Pack 1 for Exchange Server 2010, the Exchange Management Shell is missing.

Cause: Missing certain .ps1 scripts from the bin directory, removed during SP1 setup.Resolution: There is no resolution at this time. 

 


Workaround:

 

1.

Verify that the ConnectFunctions.ps1 , RemoteExchange.ps1 and CommonConnectFunctions.ps1 files are present in the %ExchangeInstallPath%\bin directory.

NOTE : If these files are missing, you can copy the files from the Exchange Server 2010 Service Pack 1 installation media to the %ExchangeInstallPath%\bin directory.
These files are present in the \setup\serverroles\common folder.

2.

Right click an open area on the Desktop, click New , click Shortcut .

3.

In the Type the location of the item , type in the text below:
%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe -noexit -command “. ‘%ExchangeInstallPath%\bin\RemoteExchange.ps1’; Connect-ExchangeServer -auto”

4.

Name the shortcut Exchange Management Shell and click Finish .

5.

Right click the Exchange Management Shell shortcut, click Properties and remove the text from Start In field on the Shortcut tab.

6.

On the Shortcut tab, click Change Icon , click Browse  and type in the text below:
%SystemRoot%\Installer\{4934D1EA-BE46-48B1-8847-F1AF20E892C1}\PowerShell.exe

7.

Select the Exchange icon and click OK .

8.

Click Apply and click OK .

9.

Copy the new Exchange Management Shell shortcut to this location:
%systemdrive%\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft Exchange Server 2010


Comments (22)

  1. Anonymous says:

    thank you very much

  2. Anonymous says:

    Thank you so much! Nobody can ask this question before you!

  3. Anonymous says:

    First time encountering with SP3 update. Glad this article is available!

  4. Anonymous says:

    thank you very much

  5. Anonymous says:

    the same issue found after installing E2k10 Sp3, is this bug

  6. Anonymous says:

    I have a server 2008 SP1 with Exchange 2007 Installed, Due to some issue server halted. After starting the server I can’t see EMC in the start menu. Can any one help me to get back the EMC. Your help is most appreciated.

  7. Sanyapong K. says:

    The error should appeared as follow:

    The term 'C:Program FilesMicrosoftExchange ServerV14binRemoteExchange.ps1

    ' 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 tha

    t the path is correct and try again.

    At line:1 char:2

    + . <<<<  'C:Program FilesMicrosoftExchange ServerV14binRemoteExchange.ps

    1'; Connect-ExchangeServer -auto

       + CategoryInfo          : ObjectNotFound: (C:Program File…oteExchange.p

      s1:String) [], CommandNotFoundException

       + FullyQualifiedErrorId : CommandNotFoundException

    The term 'Connect-ExchangeServer' is not recognized as the name of a cmdlet, fu

    nction, 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:98

    + . 'C:Program FilesMicrosoftExchange ServerV14binRemoteExchange.ps1'; Co

    nnect-ExchangeServer <<<<  -auto

       + CategoryInfo          : ObjectNotFound: (Connect-ExchangeServer:String)

      [], CommandNotFoundException

       + FullyQualifiedErrorId : CommandNotFoundException

    Has to copy them from another server. The installation left only 5 .ps1 files, while there are 8 in another SP1 machine.

    Those 3 missing files are

    CommonConnectFunctions.ps1

    ConnectFunctions.ps1

    RemoteExchange.ps1

  8. Emmanuel Cambier says:

    Thanks a lot for this info !

    It's the third installation bug that i'm facing with SP1 !

  9. lotus says:

    Thank you very much for the info, It was very helpful.

  10. Chris S. says:

    This also worked for me post SP1 install.

  11. pelin says:

    Hi Sanjays11,

    This is not a bug. However, if you have experienced some issues when installing/upgrading your server previously, and it didn't finish the setup properly, it leaves a watermark in the registry, under HKLMSoftwareMicrosoftExchangeServerv14AdminTools.

    You should remove watermark and Action completely and leave only Configuredversion entry there.

  12. Ilyas Azmi says:

    Thank you so much. Exchange SP3 blew away the files you described earlier. Had me in a little bit of panic until I found this article. cheers

  13. Anonymous says:

    I have written before about the case of a missing shortcut for Exchange PowerShell here http://blogs

  14. AI says:

    Or for anyone who wants the correct original document that explains the issue and isn’t a glory hound posting look here – http://support.microsoft.com/kb/2397266

  15. Drew says:

    Thanks for the tip, worked like a charm. For a while I thought that the shell wasn’t installed at all.

  16. Dave says:

    Nice Post, it works great!!

  17. Scott King says:

    Thanks! I discovered the problem after installing SP3. Your guidance worked great!

  18. Chris says:

    Thanks, I had the same problem when upgrading from Service pack 1 to Service PAck 3

  19. Kanta Prasad says:

    I have installed SP3 on 3 servers with the same file. I found this issue on 1 out of 3 servers which got perfactly fixed following above steps.

    Excellent Blog.

    Thanks,
    Kantaprasad@carillionplc.com

  20. Ben says:

    Nice one. Thank you

  21. dingoes says:

    also had this issue on a dag member, this sorted it out perfectly