The windows Powershell snap-n ‘Microsoft.Exchange.Management.Powershell.E2010’ is not installed on this machine

I was onsite recently and a vendor from a 3rd party product was having difficulties installing the application. When I looked at the error it was referencing ‘Microsoft.Exchange.Management.Powershell.E2010’ which should be there since this was a physical Exchange 2010 SP1 RU1 box. This was a bit odd so I looked at the current snapins by using the “get-pssnapin” command and nothing but Microsoft.Exchange.Management.PowerShell.Setup was there! WHAT!? I was expecting to see the following:

Microsoft.Exchange.Management.PowerShell.Setup
Microsoft.Exchange.Management.PowerShell.E2010
Microsoft.Exchange.Management.Powershell.Support

I then tried to manually load the Microsoft.Exchange.Management.Powershell.E2010 and we got the following error:

“The windows Powershell snap-n ‘Microsoft.Exchange.Management.Powershell.E2010’ is not installed on this machine.”

REALLY!!?

The next thing to check was to see if ConnectFunctions.ps1, RemoteExchange.ps1, and CommonConnectFunctions.ps1 was in D:Program FilesMicrosoftExchange ServerV14bin (this paticular install path for Exchange) and they were. Apparently there have been reports that issues occurred on this server only during the SP1 roll out and after the fact some random issues with running basic commandlets also occurred. Looking into the registry we found somethign interesting in HKLMSOFTWAREMicrosoftPowerShell1PowerShellSnapIns. We saw only 1 out 3 keys and you might have guessed it.. the Microsoft.Exchange.Management.PowerShell.Setup

I then tried to manually load the Microsoft.Exchange.Management.Powershell.E2010 and we got the following error:

“The windows Powershell snap-n ‘Microsoft.Exchange.Management.Powershell.E2010’ is not installed on this machine.”

We then looked in HKEY_LOCAL_MACHINESOFTWAREMicrosoftPowerShell and found only the Setup key in parent key of the broken server but all three are there for servers that work ok. Since the install path was exactly the same we safely exported the missing registry keys and imported them in and it worked (no reboot needed). The followign is the actual keys that are needed:

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftPowerShell1PowerShellSnapInsMicrosoft.Exchange.Management.PowerShell.E2010]
“CustomPSSnapInType”=”Microsoft.Exchange.Management.PowerShell.AdminPSSnapIn”
“ApplicationBase”=”D:Program FilesMicrosoftExchange ServerV14bin”
“AssemblyName”=”Microsoft.Exchange.PowerShell.Configuration, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35”
“Description”=”Admin Tasks for the Exchange Server”
“ModuleName”=”D:Program FilesMicrosoftExchange ServerV14binMicrosoft.Exchange.PowerShell.Configuration.dll”
“PowerShellVersion”=”1.0”
“Vendor”=”Microsoft Corporation”
“Version”=”14.0.0.0”
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftPowerShell1PowerShellSnapInsMicrosoft.Exchange.Management.PowerShell.Setup]
“CustomPSSnapInType”=”Microsoft.Exchange.Management.PowerShell.SetupPSSnapIn”
“ApplicationBase”=”D:Program FilesMicrosoftExchange ServerV14bin”
“AssemblyName”=”Microsoft.Exchange.PowerShell.Configuration, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35”
“Description”=”Setup Tasks for the Exchange Server”
“ModuleName”=”D:Program FilesMicrosoftExchange ServerV14binMicrosoft.Exchange.PowerShell.configuration.dll”
“PowerShellVersion”=”1.0”
“Vendor”=”Microsoft”
“Version”=”14.0.0.0”
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftPowerShell1PowerShellSnapInsMicrosoft.Exchange.Management.Powershell.Support]
“CustomPSSnapInType”=”Microsoft.Exchange.Management.Powershell.Support.SupportPSSnapIn”
“ApplicationBase”=”D:Program FilesMicrosoftExchange ServerV14bin”
“AssemblyName”=”Microsoft.Exchange.Management.Powershell.Support, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35”
“Description”=”Support Tasks for the Exchange Server”
“ModuleName”=”D:Program FilesMicrosoftExchange ServerV14binMicrosoft.Exchange.Management.Powershell.Support.dll”
“PowerShellVersion”=”1.0”
“Vendor”=”Microsoft Corporation”
“Version”=”14.0.0.0”

Advertisements

About Joe Trombley (MSFT)

Got a question about Exchange and want to ping it off a Microsoft Certified Master that works for Microsoft as a Senior Premier Field Engineer or just recieve some good information about Exchange? This is the place. Join today! I am here for you.
This entry was posted in Uncategorized. Bookmark the permalink.

17 Responses to The windows Powershell snap-n ‘Microsoft.Exchange.Management.Powershell.E2010’ is not installed on this machine

  1. Igor_Z says:

    Thanx a lot for your post! It was very usefull!

  2. Doug says:

    I really appreciate this post. It seems that many are having this issue.
    I run one exchange server here, having this issue I had to recreate the mentioned registry keys and uninstall the SP1 for exchange 2010. It would have been nice if you could have posted a link to the export reg files. The character escaping on the HTML post is all messed up. I don’t have another server to export them from.
    At this point my OWA works. However, I have not loaded SP1 back in. I was wondering if there is any test I could do to make sure the snap-ins work?

  3. Daniel says:

    Thanks for the info. I had the same issue, although I could still actually use EMS on the server in question. Here’s a registry export of a working Ex2010SP2UR2 server that I used to fix the broken one. http://db.tt/I43GNR7S

  4. Pingback: 281: Server Summit 2012 – Exchange Troubleshooting I « Wolfgang on the Road

  5. Tom says:

    a wonderful article, but how did this happen? does anyone know?

  6. Paul says:

    Thanks for this great post!
    This fix made the power shell scripts work on my laptop with the Exchange management tools installed. I’m running the Exchange 2010 tools on Windows 8.

  7. Jojo says:

    thank you for the great post, you saved my day 🙂

  8. Anonymous says:

    Thanks for this post, it was very helpful. I recently upgraded Exchange 2010 from SP2 to SP3 on 8 servers and two of them were missing the registry keys and the ps1 script files from the Bin directory after the upgrade. Copying the script files and registry keys from working servers fixed everything up.

  9. Anonymous says:

    good information
    thanks!

  10. Anonymous says:

    Thanks! Helped me out also.

  11. Olivier says:

    Thanks a lot. This post help me to solve a problem in the install of an extern Exchange connector. Bonne journée depuis Bordeaux, FRANCE !

  12. njmatty says:

    Thank you, thank you, thank you!! Saved my bacon here at 10:30 PM on a Saturday when the Exchange Admin’s on vacation and left me some scripts to run before a maintenance window 🙂

  13. Pingback: Jim-Doyle.com » Microsoft.Exchange.Management.Powershell.E2010 Not Installed

  14. Anonymous says:

    Ran Sp3 and RU5 upgrades and had one server suffer this issue, thank you.

  15. Pingback: msdigest.net - The Windows PowerShell snap-in Microsoft.Exchange.Management.PowerShell.E2010 is not installed on this machine by Peter Schmidt

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s