Exchange 2010 Management tools
-
Thursday, March 01, 2012 5:52 PM
Is there anyway to install the Exchange 2010 management tools on Windows 8?
I'm running the setup for Exchange 2010 SP2 and when it checks the preqs, it says Exchange can't be installed on Windows 8.
All Replies
-
Friday, March 02, 2012 1:48 PM
So there might be a way to run Exchange 2010 management tools on Windows 8. I haven't yet tried it but will try and report. Paul Cunningham from exchangeserverpro.com has tried installing exchange server 2010 on windows server 8 and run into the same issue. The key is that exchange bpa, looks at the OS version and throws an error when it sees the operating system version at 6.2. You can change the registry key to trick the install to go through. The registry key you are looking for is HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion and look for the CurrentVersion string value, which will be set to 6.2, change this to 6.1 and you should have the install to go through.
For more info look at this blog post from Paul here http://exchangeserverpro.com/installing-exchange-server-2010-windows-server-8
Let me know how it goes.
-Sumeeth
-
Friday, March 02, 2012 5:47 PM
That worked for getting it installed. However it doesn't seem to work correctly.
After I opened it, I can't seem to expand out Microsoft Exchange On-Premises
https://skydrive.live.com/#cid=33E32910D95D57E9&id=33E32910D95D57E9%21436
-
Wednesday, March 07, 2012 7:23 AMModerator
Windows 8 is not indicated to support it.
Exchange Server Supportability Matrix
http://technet.microsoft.com/en-us/library/ff728623.aspxMay need to wait for new version.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
-
Saturday, May 12, 2012 12:17 AMI did not know it. If it true hope the upgrade to be easy and not change all the PowerShell or EWS auth policies .
P Velachoutakos
-
Tuesday, June 12, 2012 6:02 AMDo we know if anything has changed since Windows 8 RC?
-
Thursday, August 16, 2012 9:37 PMAs of today (8/16/2012), it still behaves as described above for Win 8 Ent RTM with E2k10 SP2 Rollup 4
-
Tuesday, August 21, 2012 9:22 AMI could really use this, all the other admin tools are working great, its just exchange
MCP, MCDST, MCTS x 6, MCITP x 3
Please don't forget to mark this post as an answer if it is the solution to your problem!
If you like trance music, please subscribe to my podcast Trancendance Podcast
-
Friday, August 24, 2012 1:33 AM
I was able to do this with a few additional steps:
- Modify the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion registry key from "6.2" to "6.1" as stated above.
- Install the .NET Framework 3.5 Windows Feature
- Install the IIS 6 Management Console Feature
- Install the IIS Metabase and IIS 6 Configuration Compatibility Feature
Once I completed those steps I was able to install the management tools on my Windows 8 Enterprise (RTM) machine without issue. After the install I changed the above registry key back from "6.1" to "6.2" as it originally was. The console now works as expected. Sure, it's not officially signed off on by Microsoft but it works fine as far as I have seen so far. It's probably worth noting that I have the RSAT installed also which may have corrected some other dependencies that I am not aware of. Installing the RSAT requires extracting the files from the MSU file and manually installing it.
Hope that helps,
Don
- Proposed As Answer by Brian_Jones Friday, August 24, 2012 7:53 AM
- Unproposed As Answer by Brian_Jones Friday, August 24, 2012 7:55 AM
- Proposed As Answer by SleepyXray Monday, January 07, 2013 10:50 PM
-
Thursday, September 20, 2012 1:01 PM
This is a great workaround, as supplied by my boss.
Create a bat file:
set __COMPAT_LAYER=RUNASINVOKER
set COMPLUS_Version=v2.0.50727
c:\admin.msc
create an mmc and save it with the exchange tool to c:\admin.msc
MCP, MCDST, MCTS x 6, MCITP x 3
Please don't forget to mark this post as an answer if it is the solution to your problem!
If you like trance music, please subscribe to my podcast Trancendance Podcast
- Proposed As Answer by Brian_Jones Thursday, September 20, 2012 1:01 PM
-
Wednesday, December 05, 2012 11:52 PM
One small tweak I would suggest, instead of creating a custom admin.msc, just point to the normal Exchange EMC.msc. I believe it defaults to "C:\Program Files\Microsoft\Exchange Server\V14\Bin\Exchange Management Console.msc"
Worked like a charm to me. I just wish there was some way to change the compatibility settings on the regular msc so we didn't have to mess with a batch file.
-
Friday, December 07, 2012 12:43 PM
Thanks Jerquiaga, that works a charm!
So, edited, that is:
set __COMPAT_LAYER=RUNASINVOKER
set COMPLUS_Version=v2.0.50727
"C:\Program Files\Microsoft\Exchange Server\V14\Bin\Exchange Management Console.msc"
exit
MCP, MCDST, MCTS x 6, MCITP x 3
Please don't forget to mark this post as an answer if it is the solution to your problem!
If you like trance music, please subscribe to my podcast Trancendance Podcast
- Edited by Brian_Jones Friday, December 07, 2012 12:43 PM added code
- Proposed As Answer by Brian_Jones Friday, December 07, 2012 12:43 PM
-
Tuesday, December 11, 2012 11:45 AM
This worked for me.
Thanks Brian_Jones and Jerquiaga for posting this workaround.
D.E.
-
Tuesday, December 18, 2012 2:23 PM
You may get it to work, but you may not. Powershell 3 is not compatible with Exchange 2007/2010.
Mike
-
Thursday, March 21, 2013 3:19 PM
Tweaked a little more so it will close after the launch.
set __COMPAT_LAYER=RUNASINVOKER
set COMPLUS_Version=v2.0.50727
START "C:\Windows\System32\mmc.exe" "C:\Program Files\Microsoft\Exchange Server\V14\Bin\Exchange Management Console.msc"
exit- Sebastien Plante (nka)
- Proposed As Answer by nka_ Thursday, March 21, 2013 3:20 PM
.png)
