Exchange 2010 FAQ: How Do I Install the Exchange 2010 Management Tools?

Question: How do I install the Exchange Server 2010 management tools on my workstation?

The Exchange Server 2010 management tools can be installed on a computer running one of the following operating systems:

  • Windows Vista 64-bit with Service Pack 2
  • Windows 7 64-bit
  • Windows Server 2008 64-bit with Service Pack 2
  • Windows Server 2008 R2

To install the Exchange 2010 management tools on your Windows 7 computer you first need to configure the pre-requisite components.

Open the Control Panel, click on Programs and then click on Turn Windows Features On or Off.  Enable the features shown here.

Enable Windows 7 features required for Exchange Server 2010 management tools

Download the Exchange Server 2010 SP1 installation files and extract them to a temporary folder on your computer.  From that folder launch Setup.exe.  If your computer is missing either the .NET Framework or Windows PowerShell pre-requisites there will be links for Step 1 and 2 to download and install them.

Install pre-requisites for Exchange Server 2010 SP1 on Windows 7

Otherwise click on Step 3 and choose Install only languages from the DVD.

Choose language options for installing Exchange Server 2010 SP1 on Windows 7

Next, click on Step 4 to begin the installation.

Begin installation of Exchange Server 2010 SP1 on Windows 7

Click Next at the introduction page, then accept the license agreement and click Next, then choose your preference for Error Reporting and click Next again.

At the Installation Type page choose Custom Exchange Server Installation, and also tick the box to Automatically install Windows Server roles and features required for Exchange Server and click Next.

Custom Exchange Server installation for installing management tools on Windows 7

Select the Management Tools role and click Next.

Installing the Management Tools role for Exchange 2010 on Windows 7

When the Readiness Checks have completed successfully click Install.

Begin installation of Exchange 2010 management tools on Windows 7

After the install has completed you can launch the Exchange Management Console from the Start -> All Programs -> Microsoft Exchange Server 2010 menu.

Comments

  1. craigp says

    Hi Paul,

    thanks heaps for this article, I’m hoping it will prove to be useful but unfortunately I have encountered an error when at the Readiness Check.

    The Configuring Prerequisites section fails with the following error:

    Error:
    The following error was generated when “$error.Clear();
    if($RoleInstallWindowsComponents)
    {
    # Install any Windows Roles or Features required for the Management Tools role
    Install-WindowsComponent -ShortNameForRole “AdminTools” -ADToolsNeeded $RoleADToolsNeeded
    }
    ” was run: “The system cannot find the file specified”.

    The system cannot find the file specified
    Click here for help… http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=ms.exch.err.Ex88D115&l=0&cl=cp

    Elapsed Time: 00:00:01

    Unfortunately the Technet page is of no help at all (“You’ve found an error that doesn’t have an article written about it”).

    Any advice would be most appreciated.

    Thank you.

    Regards,
    Craig

      • craigp says

        Hi Paul,

        thanks for the reply and my apologies for overlooking the obvious – I’m running Windows 7 Professional 64 bit edition, with up to date patches (to just before Win 7 SP1) and I installed the 64bit SP1 you linked to above ( filename = Exchange2010-SP1-x64.exe ).

        I followed all steps you listed above exactly, but unfortunately encountered the error in the Readiness Check (and google didn’t help.. only 1 hit and it was the same error in a .log file).

        So any suggestions or advice would be most appreciated.

        Oh and thank you for your time.

        Regards,
        Craig

        • Jon Scriven says

          Yes, I had this error despite having admin rights on the machine. However, right-clicking and running setup “as administrator” was the fix.

      • davidm says

        Hey guys,

        I was getting this same error; I am not sure exactly what fixed it but after installing KB958830 and enabling SMTP RSAT tools in windows features I was able to get this to work.

        Hope this helps!

  2. craigp says

    Hi Paul,

    I’ve been trying more options, but with no luck so far.

    I noticed at the top of the article you list Windows 7 with Service Pack 2 as a prerequisite, I gather that’s a mistake as SP1 was only released a week or so ago?

    Also I tried installing with the ‘Automatically install Windows Server Roles …” option unticked, but it failed (I cannot recall the error message unfortunately, I’ll see if I get time to try it again later)

    regards,
    Craig

    • says

      Yes thats a typo.

      For your issue, “The system cannot find the file specified”, have you done anything like delete the cache of Windows 7 source files from your C: drive to save on disk space?

  3. Kris Doosje says

    I had the same issue as craigp, but after unticking to automatically install roles and features required for Exchange, the install went fine and the management console is working for me.

    • craigp says

      hi all,
      just getting back – I originally tried with the ‘install roles’ unticked and it gave me an error message, but I tried it again recently (after installing Windows 7 SP1) and it worked for me. so maybe I was missing a KB?

      anyways, thanks for all the help and that’s my suggestion if anyone else has any issues.. try SP1, then try installing the management console (don’t forget to apply the MC update as well).

    • JSoto says

      Thanks had the exact same issue as craigp and used Kris Doojse solution and nailed it. Thanks. The error message was linking to a technet page with no solution as craigp was stating. I am on Windows 7 x64 with SP1 and all patched up and Exchange 2010 with build:

      Exchange Server 2010
      Microsoft Corporation
      Version: 14.02.0328.009

  4. Kris Doosje says

    I was a bit to quickly.. the install went fine, and the management console starts up just fine. But I don’t have the right permissions somehow?

    I installed it on Windows 7 SP1. If log on to the Exchange server with the same user account, I have all permissons, when I log on with this user on the Windows 7 machine, I can only view some properties, but I can’t change anything.

    Any suggestions?

  5. Chad says

    I am not sure what I am missing here, but I did have the exchange tabs in Active Directory Users and Computers. We upgraded to Exchange 2010. I installed RSAT on my W7x64 machine, then I followed these instructions. I have the Exchange Management Console, but I would like to have the Exchange AD tabs back!

  6. says

    any experience a crash wehn trying to install i get to “microsoft Exchange Server 2010 setup initializing” .. hangs there for about 10 to 15mins then i get an error saying that “lpsetupui.exe not responding” this is what i get in event viewer

    Faulting application name: ExSetupUI.exe, version: 14.1.218.13, time stamp: 0x4c6b8aab
    Faulting module name: KERNELBASE.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c78c
    Exception code: 0xe053534f
    Fault offset: 0x000000000000a49d
    Faulting process id: 0x%9
    Faulting application start time: 0x%10
    Faulting application path: %11
    Faulting module path: %12
    Report Id: %13

  7. John A says

    I had the same issue with the first inital post. I unticked the “Automatically install Windows Server roles and features required for Exchange Server” and my install worked. The only thing I can say is that I installed Windows 7 Administrative Tools Windows”6.1-KB958830-x64-RefreshPkg” and installed every option available via control panel – windows features afterwards.

    John

  8. Todd says

    Windows 7 x64 SP1
    All RSAT features turned on.
    All Windows Updates installed as of today (18 Aug 2011)
    Followed Paul’s article exactly (including pre-reqs and check boxes).
    Installing from “Exchange2010-SP1-x64.exe” and I get the following…
    Please advise.

    +++++

    Summary: 3 item(s). 2 succeeded, 1 failed.
    Elapsed time: 00:01:09

    Configuring Prerequisites
    Failed

    Error:
    The following error was generated when “$error.Clear();
    if($RoleInstallWindowsComponents)
    {
    # Install any Windows Roles or Features required for the Management Tools role
    Install-WindowsComponent -ShortNameForRole “AdminTools” -ADToolsNeeded $RoleADToolsNeeded
    }
    ” was run: “The system cannot find the file specified”.

    The system cannot find the file specified
    Click here for help… http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=ms.exch.err.Ex88D115&l=0&cl=cp

    Elapsed Time: 00:00:02

    Management Tools Prerequisites
    Completed

    Elapsed Time: 00:00:59

    Languages Prerequisites
    Completed

    Elapsed Time: 00:00:07

    • Todd says

      So … I ended up installing the Windows 7 SP1 RSAT Refresh (KB958830), restarted my machine and Viola! … the Exchange 2010 SP1 Management Tools installed.

      Now … back to work!

      • Ryan says

        I have tried the solutions you offered; however, I still have been unable to install Exchange 2010. I keep getting the error that says “Install-WindowsComponent -ShortNameForRole “AdminTools” -ADToolsNeeded $RoleADToolsNeeded”
        I followed the steps above exactly. Any help would be greatly appreciated. Thanks!

  9. Jamie Forster says

    Hi,

    I am interested in this article as I am trying to fix some issues with my backup solution and have been told to install exchange management tools on a second server where the backup is running from.

    I am just wondering if I require a licence to have the management tools on a different PC or not.

    thanks

    Jamie

  10. Ash says

    Hi Paul,

    I have followed your instructions and have managed to install the EMC on to a DC server but when i try to connect to the EMC it fails with the following – Initialization failed – The world Wide Web publishing service isn`t running on any exchange servers in the site. If you want to connect to remote Powershell, this service must be running. Make sure teh W3SVC is running on at least one exchange server. well i have checked and the service is running.
    We have two DC servers and have installed on the secondary the reason i need it is for Gal modifers group to access the mail contacts.

    Am i missing something simple?

    servers are windows 2008r2

    thank you

    Ash

      • Ash says

        Hi Paul,

        Sorry for the delay in replying.

        I have now abondoned the DC option and setup a test server.

        The version on the exchange server is – 14.00.0722.00 and the EMC on my test server is 14.01.0218.013.

        services are running.

        thank you,

        Ash

      • Ash says

        Hi Paul,
        just to give you an update.

        I have managed to get the EMC to work!

        The problem was the exchange version was different so i uninstalled the emc off the test server then installed off the original dvd for exchange.
        connection now successfull.

        thank you

        Ash

  11. Mirjam says

    Hi Paul,

    we´ve got Exchange 2010 on a 2008R.
    All available updates are installed.

    Since few days, I´m trying to install the Management Console for Exchange 2010 on my Windows 7 Pro 64bit SP1 system.
    If I check “Automatically install Windows Server Roles”, I get the same error like Craig.
    If I uncheck the box, the console will be installed, but then I get “initialization failed” and there is no
    connection to the server.
    I´ve installed all updates and KBs, also hotfixes, which were talked about in this thread… but for me nothing t works.
    I´ve installed the RSAT tools twice… now I am at my wit’s end.

    Any other ideas?

    It would be great, if someone could help me!

    Thx
    Mirjam

  12. TimC says

    I did not have any problems installing the Management Tools, but when I try to run them and connect to the server from my Windows 7 Pro x64 machine, i get the following error:

    ——————————————————————————————————————————————
    Initialization Failed

    The following error occurred while searching for the on-premises Exchange Server:

    The World Wide Web Publishing Service (W3SVC) isn’t running on any Exchange servers in the site. If you want to connect to Remote PowerShell, this service must be running. Make sure that the W3SVC is running on at least one Exchange server.

    (i) Click here to retry
    ——————————————————————————————————————————————

    I check and see this service is running on all 4 of our exchange servers. I have no problem running the management tools on any of the exchange servers, but several tries reinstalling the management tools on my system all resulted in this error.

    • cdiakiw says

      Hi Tim
      i had the same issue after i upgraded to sp2, try upgrading the mamangement tools to the current version

  13. Michael says

    Hi Paul – i was reading some of the comments above and noticed some folks were having trouble with getting an error. I am not sure if you addressed this yet, but I too had the same error but was able to resolve it. The things I did to resolve the installation error were:
    1) After downloading the tool, extract it to a local folder.
    2) Right-click the setup.exe file and choose run as administrator

    …and that resolved the error and got the program to install properly.

    hope that helps.

  14. says

    I had the same error message as Craig. Running SBS 2011. I never use the SBS wizards/tools because they never do all I need to do. I’m not a powershell guy. Maybe I should be, but I’m not yet. Anyway, once I unticked the box “install roles” I was able to start the install. (Win 7 64 bit SP1 with RSAT refresh installed.) The only reason I really need the management tools is to go in and create mailboxes for users created by the accounting department. Right now I’m RDPing in to the server and doing it through the Man. Console. I would love to just use ECP and delegate that task as well. I don’t really want to install Exchange Management Tools on the delegated user’s computer. Unfortunately, Microsoft is really making it hard for everybody to do what used to be easy. Maybe Exchange 2010 is great for larger businesses, but I don’t think so for small businesses.

    • says

      Gabriel, you could have a scheduled task running a script that looks for users created in the last 24 hours and mailbox enables them. Would be a good exercise to turn you into a “Powershell guy” ;-)

      Otherwise (and I haven’t tinkered with SBS 2011 yet) but isn’t there a way to install the SBS management console on a workstation?

  15. VJ says

    My Exchange 2010 management console was working fine but today it started giving me a connectvity issue. I did my best to trouble shoot. Can you help me with the error below:

    ERBOSE: Connecting to WIN-S3O5NM2A9V8.forexglobal.local

    [win-s3o5nm2a9v8.forexglobal.local] Connecting to remote server failed with the following error message : WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found.
    Possible causes are:
    -The user name or password specified are invalid.
    -Kerberos is used when no authentication method and no user name are specified.
    -Kerberos accepts domain user names, but not local user names.
    -The Service Principal Name (SPN) for the remote computer name and port does not exist.
    -The client and remote computers are in different domains and there is no trust between the two domains.
    After checking for the above issues, try the following:
    -Check the Event Viewer for events related to authentication.
    -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport.
    Note that computers in the TrustedHosts list might not be authenticated.
    -For more information about WinRM configuration, run the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic.
    + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException
    + FullyQualifiedErrorId : PSSessionOpenFailed
    The Exchange Management Troubleshooter successfully completed connecting to:

    WIN-S3O5NM2A9V8.forexglobal.local

    **********************
    Windows PowerShell Transcript End
    End time: 20120319154852

  16. Nathan Winters says

    Just a “food for thought” comment to those complaining that their local EMC doesn’t connect due to the error:
    “The World Wide Web Publishing Service (W3SVC) isn’t running on any Exchange servers in the site. If you want to connect to Remote PowerShell, this service must be running. Make sure that the W3SVC is running on at least one Exchange server.”

    This error with the EMC not finding W3SVC occurs if you try to run the EMC from an AD site/subnet with no Exchange servers installed.

    Consider that you install management tools on an x64 laptop in site NEWYORK, but all Exchange servers are in a different MSAD site NEWJERSEY. The EMC will run fine on the servers, because they discover servers in the same site/subnet container where the EMC runs…

    The EM”S” always works because MSAD will recognise that there is no “on-site” powershell interface and auto-redirect you to the nearest server based on your AD topology and site-to-site costs. You’ll see a brief “Warning” stating:

    “WARNING: No Exchange servers are available in the Active Directory site XYZ.
    Connecting to an Exchange server in another Active Directory site.”

    If there’s a way to “workaround” that, I’d certainly also be happy to hear it…

  17. Dave says

    Just to add to the posts – i too was experiencing the install problem with the same error as “craigp” and UNCHECKING the automatically install server roles option allowed the install to complete successfully. MS SUX!

    • Jeremy says

      Thanks Dave that worked. Been trying a few times to get the EMC installed on my computer since i don’t want to Remote Desktop into the exchange server every time i have to add or delete an email account, etc, etc.

      Maybe it fails because we already had the remote server admin tools features installed and didn’t need to check that box.

  18. Arif S says

    Can Not uninstall EMC from win 7 x64, it says some services are running.. but not so sure which services need to be turn off … help please…
    thanks
    A

    • says

      Try closing down any MMC admin tools and any PowerShell windows you may have open.

      Otherwise you’ll need to provide more details on the exact error message before I can suggest anything else.

  19. Arif S says

    thanks for your reply… antivirus was the issue.. i was able uninstall that and now i am trying to install it again.. we will see….
    ps- last time it was not working… it gave me the following error..
    “Connecting to remote server failed with the following error message: Exchange Management Console cannot connect to this Server because the version are incompatible, the current server version is: ’14.1.218.15′. For more information, see the about_Remote_Troubleshooting Help topic.””

    We will see this time…

    thanks
    A

  20. Arif S says

    wee i think i need to run Sp1 version 14.1.218.15 to get my EMC going on win7 and i am doing as we r talking
    will post…
    thanks
    A

  21. Arif S says

    I got it going this time but now i need to .. Restrictions on the Exchange console to recipient creation How?? any idea??
    Thanks
    A

  22. Melissa Dyer says

    Alright so I have installed RSAT for Windows 7 64 bit (type of machine I have) and selected the settings as shown above to do the install. However, when I check the box to automatically install Windows Server roles and features required for Exchange Server the installation fails on configuring pre-reqs as shown by Craigp. Now If I uncheck that box the installation goes through fine but when I go to launch the initialization fails with the error as stated by Tim C. I have uninstalled and reinstalled RSAT like 3 times with and w/out my domain admin account and yes I have admin privs on my machine. Turned off and turned back on the settings needed to see if that work but no success. This is also a recently reformatted machine and the installation was able to work on it before the reformat. Any ideas on how to correct or to get the installation to work?

    • Jeremy says

      I looked at my RSAT features for Web Manager tools, Make sure the IIS 6 Management Compatibility folder and sub folders are all checked, World Wide Web Services with Application Development Features and .NET Extensibility, Security folder check with Request Filterering sub folder checked. Also just for giggles enable every main feature folder and sub folder in the Remote Server Administraotr Tools even if you dont need them. Restart your PC and than log back on and try the EMC install again. Let me know if that fixes it. Also to everyone in the process of installing EMC or getting it to work please note I had a different version of EMC than on the Exchange Server 2010. I read the message when adding the exchange forest/exchange server and I had to remote log into the exchange server and open up the EMC console and go to help and about which had a different and I think newer version of EMC. i than had to download the same version EMC console on my workstation that is on the exchange server. After that I have been able to connect to and manage our Exchange Server via my local workstation EMC. Just a FYI if any one else runs into that little bump in the road after installing EMC on there desktop or workstation computer.

  23. Ben Long says

    We tried various ways of doing this and in the end tried a 32 bit version of the tools recommended to us by a reseller. They hadn’t used it before but it worked well for us as it allows us to do basic administration from ADUC. Have a look on http://www.onesixtyfour.co.uk.

    p.s. haven’t bought it yet but so far so good.

  24. NARASIMHA TEGATI says

    Hi, Paul
    I am getting this error after instlled ( 2010 exhcnage sp1 ) above the steps.
    INITIALIZATION FAILED

    WInrim Client It cannot determine the content type of the HTTP Response from the destination computer. the content type is absent or invalid. for more information, see the about_Remote_Troubleshooting Help topic. It was running the command “Discover-Exchangeserver-userWIA$true-suppressError $true-Current version 14.1 ( Build 218.15)”
    Resolution: I check HTTP Response is ok and WinRIM Client service is also fine.

  25. Rehman says

    Hi, Paul
    I instaled Exchange Managment feuters on My Win 7 64Bit now i want to upgrade that to SP1 as some on backup command not supported on Exchange Plain versiom(Basic ) So when trying to do I am getting the 2 error .
    1) Active Directory Schema is not up-to-date and Ldifde.exe is not instlled.
    2)The active directory needs to be prepared for exchange server and Ldifde.exe is not instlled on this computer.

    My question where i need to installed this on Win 7 or My exchanges Server 2010 or DC.
    and if possible how ?

    Many thanks,
    Rehman

  26. says

    Hi Paul,

    I have been searching around for informatio and found your article. Thanks for writing this, I have a question regarding the poerating systems.
    Do you have information/experience installing Exchange Management Tools 2010 on a Windows 2003 64 server? The Exchange server is 2008R2, Exchange 2010R2. Our backup software is requiring the tools but I am concerned they do not function on a 2003 server.

    Thanks for any assistance you may be able to provide,
    Jim

  27. Sam says

    I had the same issue, i unflagged “automatically install roles and features required for Exchange” and it worked after that..

  28. Mel says

    Install Exchange patch “Exchange2010-KB2608646-x64-en.msp” and live would be great, it took’s me a while to figure out this, good luck.

    Thanks
    Mel

  29. Ji says

    I’m running into the following error when Configuring Prerequisites, even though I’m running the installation with admin permission:

    The following error was generated when “$error.Clear();
    if (Get-Service RemoteRegistry* | ?{$_.Name -eq ‘RemoteRegistry’})
    {
    Set-Service RemoteRegistry -StartupType Automatic
    Start-SetupService -ServiceName RemoteRegistry
    }
    ” was run: “Service ‘Remote Registry (RemoteRegistry)’ cannot be configured due to the following error: Access is denied”.

    Any suggestion please? Thanks!

  30. K-dub says

    Hello,

    Has anyone found a solution to Ji’s issue? i am having exactly the same problem, and have been trying for two days, scouring the interwebs, to no avail. i have followed Paul’s document, and tried pretty much every suggestion made in the comment section, and still get the same error.

    I just want to manage my Exchange environment from my desktop, instead of RDP’ing into my server. That’s all.
    :..(

    I would be forever grateful to anyone that can help to resolve this issue! (forever!)

    Regards,
    K-Dub

  31. Ricky says

    I have a succesfull installation for the Ms-Exchange Console ToolBox,
    but how i can reset and create the new user account using the console?

    did i miss the option during installations?

  32. Anthony says

    Thanks for this easy and quick tutorial.
    The install couldn’t have gone smoother for me, except of course if the computer would have selected all the options and clicked install for me.

  33. Bill says

    Paul, this is an excellent post. Thanks for this great info!

    Do people ever read the comments before asking questions?
    This will be at the bottom of the page so nobody will EVER see this, but just in case…
    I did an install of Exchange 2010 Management Console onto an IT Managers Win7 64bit machine and have some tips that might assist some people?

    These tips are potentially only valid with a Win7 64bit installation. I dont know. I didn’t test other OS versions. One thing to note is that I already had the AD DS features of RSAT installed on this machine to enable a custom AD Taskpad snap-in to run. If you follow these tips and still get a pre-requisite error, might be worth enabling the RSAT features for AD DS.

    #1 tip: You need to be installing the management tools for the same version of Exchange Server that you are actually running. You might be able to use a NEWER version management console, but to be sure, use the same version. If you are seeing “W3SVC” errors this is probably the cause.

    #2 tip: You need to have the RSAT Refresh installed for your operating system and enable the IIS features as listed in Pauls excellent post.

    #3 tip: You need to run the Exchange setup.exe as an ADMINISTRATOR… as in, you right-click setup.exe and Run As Administrator. If you are getting failed pre-requisite checks, this is probably the cause.

    #4 tip: Do not tick the box to install pre-requisites as required. If you have this ticked, the pre-requisite check will fail. Microsoft owes us all cake for this one.

    #5 tip: The PC you run the management tools on needs to be in the same “Site” as the exchange server? (I am not too sure on this one, didn’t test it). If you are getting “W3SVC” error this could be the cause.

    #6 tip: If you are getting some random connectivity error, try disabling the windows firewall and if that fixes the problem identify culprit rules and make adjustments to only the minimum amount of rules required to get it working.

  34. thelastbadboy says

    I have a Windows 7 32 bits on user’s Desktops, i’m planning to install Exchange 2007 MGMT Tools to give them access to CONTACTs management area, so they can update contacts on the address lists.

    Have you managed Exchange 2010 with Exchange 2007 Management tools?

    I really don’t want to update users operating system to 64 bits Windows 7

    greetings

    badboy

    • says

      No, you can’t manage Exchange 2010 with the 2007 tools.

      If you don’t want to give them 64-bit OS on their workstation consider setting up a terminal server for them to all share for admin tasks.

  35. Joe says

    Paul
    I am gettnig the error: the world wide web publisihing service isn’t running on any exchange servers in the site. I checked my services and i do have that service and it is running. Any help would be greatly appreacaited.

    Thanks.

  36. Tony Barrios says

    I am currently trying to to upgrade management console to Version: 14.02.0342.003 how can I do that?

    win 7 64
    Management console 3.0
    Version 6.1 (build 7601: Service pack 1

  37. Ozz says

    Thanks for the article, I am currently trying to get the Management Tools installed on our TS so that we can offload some Exchange tasks though there when remote to avoid the extra hop.
    The TS is 2008R2 and I get a few errors:
    Warning: The description for Event ID 4 from source MSExchange CmdletLogs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:

    Uninstall-MsiPackage
    {ProductCode=521e6064-b4b1-4cbc-040c-25ad697801fa, LogFile=C:\ExchangeSetupLogs\Uninstall.040C.Server.20131022-135916.msilog}
    Domain.local/Domain User Accounts/Service Accounts/Systems Admins/saxxxxx
    Exchange Management Console-Local
    3396
    28
    00:00:18.8205335
    View Entire Forest: ‘True’, Configuration Domain Controller: ‘DC_FQDN’, Preferred Global Catalog: ‘DC_FQDN’, Preferred Domain Controllers: ‘{ DC_FQDN }’

    the message resource is present but the message is not found in the string/message table

    Error: The description for Event ID 6 from source MSExchange CmdletLogs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:

    Get-ExchangeServer
    {Identity=TS_hostname}
    Domain.local/Domain User Accounts/Service Accounts/Systems Admins/saxxxxx
    Exchange Management Console-Local
    264
    29
    00:00:00.1249968
    View Entire Forest: ‘True’, Configuration Domain Controller: ‘DC_FQDN’, Preferred Global Catalog: ‘DC_FQDN’, Preferred Domain Controllers: ‘{ DC_FQDN }’
    Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn’t be performed because object ‘TS_hostname’ couldn’t be found on ‘DC_FQDN’.
    Context

    the message resource is present but the message is not found in the string/message table

  38. Ozz says

    Answering my own question, if you do run into similar issue, the service errors are nothing but red herrings, this was actually due to the fact that the EMT and the Exchange servers were on different versions, being the EMT on the TS SP2 while the servers are all SP3.
    Cheers,

    Ozz.

  39. Deepak says

    Hello Paul,

    I am installing Exchange Server 2010 64 bit -SP1.
    But this is not install on my OS. I use Window 7 64 bit Ultimate.
    and I want to Inform you that I have followed this Step for Installation.
    and I did not get successfully result. so please help me.

  40. Deepak says

    Hello Paul,

    I am getting error in Management tool Prerequisites

    1. Active Directory does not exist on cannot be concatenate.
    2. This is not part of a windows domain.
    3. The User is not logged on to a window domain.

    Please help me in Installation.
    It very Urgent Task.

    Deepak

  41. IramCH says

    Hello Paul,

    My users can configure autoreply using outlook.
    Exchange 2010 and office 2010!

    Any idea? we can however go to OWA and do it there! Thanks

  42. ArielZusya says

    HI Paul,

    Thanks for this tutorial. Can I do the same thing with SP3 in place of SP1? I have SP3 installed on the server and I want to add EMC to a local machine running Windows 7 Pro 64bit sp1. I have RSAT installed and all the other prereqs above. I right-click on setup.exe and run as admin, it gets me into the setup and everything seems ok until I tell it to actually install and then I error out as follows:

    Summary: 3 item(s). 2 succeeded, 1 failed.
    Elapsed time: 00:04:11

    Configuring Prerequisites
    Failed

    Error:
    The following error was generated when “$error.Clear();
    if($RoleInstallWindowsComponents)
    {
    # Install any Windows Roles or Features required for the Management Tools role
    if ($RoleIsWindows8OrHigher)
    {
    if($RoleADToolsNeeded)
    {
    $ADToolsNeeded = 1
    }
    else
    {
    $ADToolsNeeded = 0
    }
    Invoke-Expression ” Powershell -Command {& $RoleBinPath\InstallWindowsComponent.ps1 -ShortNameForRole AdminTools -ADToolsNeeded $ADToolsNeeded} ”
    }
    else
    {
    Install-WindowsComponent -ShortNameForRole “AdminTools” -ADToolsNeeded $RoleADToolsNeeded
    }
    }
    ” was run: “The system cannot find the file specified”.

    The system cannot find the file specified
    Click here for help… http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp

    Elapsed Time: 00:00:22

    Management Tools Prerequisites
    Completed

    Elapsed Time: 00:03:48

    Languages Prerequisites
    Completed

    Elapsed Time: 00:00:01

  43. Anthony Hope says

    You should also add the SMTP Server Tools and run the setup.exe as Administrator and it will install without any issues

  44. Lee says

    I am getting an ‘ExSetupUI has stopped working’ error running as admin or not.

    PS:
    Problem Event Name: CLR20r3
    Problem Signature 01: exsetupui.exe
    Problem Signature 02: 14.1.218.13
    Problem Signature 03: 4c6b8aab
    Problem Signature 04: ExSetupUI
    Problem Signature 05: 14.0.0.0
    Problem Signature 06: 4c6b8aab
    Problem Signature 07: 15
    Problem Signature 08: 5b
    Problem Signature 09: System.BadImageFormatException

  45. Jared says

    Anyone having this issue:

    Initialization failed – The world Wide Web publishing service isn`t running on any exchange servers in the site. If you want to connect to remote Powershell, this service must be running. Make sure teh W3SVC is running on at least one exchange server.

    I finally figured out the EMC did not automatically connect to “Microsoft Exchange On-Premises”

    Right click Microsoft Exchange (within the console), and click add new forest to manually add your mail servers URL.

    The forest “Microsoft Exchange On-Premises” will still be displayed but is not functional.

      • Jared says

        Yes – we never had any issues with the console on the server. I took some time yesterday to finally figure out how to get it working on other computers. A lot of people say they have the issue with the World Wide Web Publishing service error, even though the service is running on the exchange server.

        I just thought the console on my desktop would automatically locate/load Exchange. It did not, I had to open EMC on my desktop and add a new forest and type in our mail server URL.

Leave a Reply

Your email address will not be published. Required fields are marked *