Exchange Management Console Tools Compatibility

Is there a timeline for getting a compatible version of this software for Windows 8 Enterprise x64.  As an IT Professional, this is really getting in the way of my ability to enjoy your new OS.  I have work to do, and its not enjoyable
bouncing back and forth between OS's to get it done.  Other than this issue there is only minor annoyances, and I can be patient for resolutions.
Thank you,
Exmo14

What version of Exchange are you using?  I have the Management Console for Exchange 2010 installed and running happily under Win8 Ent x64.  Installed from the Exchange dvd, patched to the same level as the server (that was a sticking point for
me initially, didn't realise the versions had to match exactly).
Running it via the following batch file, which I found in another thread somewhere.  Your short filenames may vary depending on what else you have installed, it's "Exchange Management Console.msc" you're looking for.
set __COMPAT_LAYER=RUNASINVOKER
set COMPLUS_Version=v2.0.50727
start C:\Progra~1\Microsoft\Exchan~1\V14\Bin\Exchan~1.msc
Nigel Benfell B.Sc. MCSA

Similar Messages

  • Exchange Management Console couldn't start with Kerberos authentication failed

    When I was making changes to Client Access\owa settings, chaning from Basic authentication to Form authentication (upn name) then changed to Basic again. It was ok after changing to Form authentication but moment after changing back to Basic, I couldn't
    no longer access owa (blank page when one vertical line) and in Exchange Management Console, I got "Initialization failed" - The following error occured while attempting to connect to the specified Exchange server 'sgp-ex1.mydomain.com':
    The attempt to connect to http://sgp-ex1.mydomain.com/powershell using "Kerberos" authentication failed: Connecting to the remote server failed with the following error message: The WinRM client cannto process
    the request. 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.
    I tried the troubleshooting tool from Exchange team blog:
    http://blogs.technet.com/b/exchange/archive/2010/12/07/3411644.aspx. It give 3 possible causes for this error: 1. WSMan module entry is missing from global module section of c:\Windows\System32\InetSrv\Config\ApplicationHost.config; 2. Kerbauth module shows
    up as Managed module or has been loaded in the Default Web Site Level; 3. The Path of the Powershell virtual directory has been modified.
    I checked carefully, all the 3 causes do not apply to my situation as WSman entry is in order, the Kerbauth is native and local and the path of Powershell virtual directory is correct.
    I find that in Application log, there are Event 2297 and 2307 dumped at the time of failure:
    The worker process for application pool 'MSExchangeSyncAppPool' encountered an error 'Confiugration file in not well-formed XML' trying to read configuration data from file '\\?\C:\inetpubl\temp\apppools\MSExchangeSyncAppPool\MSExchangeSyncAppPool.config',
    line number '2'. The data field contains the error code.
    Help is very much appreciated.
    Valuable skills are not learned, learned skills aren't valuable.

    Unfortunately, all the links you provided didn't help.
    The first link contains 3 methods:1 Removing WinRM feature and reinstalling. 2 Rename the web.config file in location C:\inetpub\wwwroot 3 Have you installed Microsoft Dynamics CRM 4. I?
    As my server is Windows 2008 R2, the first method does not apply. I couldn't find any web.config in c:\Inetpub\wwwroot. The web.config however is found in many times in .netframework and winsxs directories. The 3rd method doesn't apply as I don't have CRM.
    The 2nd link contains 3 possible causes. The first 2 are the same as the ones I mentioned in my initial post. I couldn't verify the last cause because when open Exchange Management Shell, I got this error: [sgp.ex1.mydomain.com] connecting to remote server
    failed with the following server failed with the following error message: The WinRM client cannot process the request, it cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalide. For more
    information, see the about_Remote_Troubleshooting Help topic.
    I do not think the user is not remote powershell enabled because the problem happened suddenly, while I was making changes to Authentication settings of OWA(default) in Client Access in Exchange Management Console. If the user account is not remote powershell
    enabled, then I couldn't event connect to EMC in the first place.
    The last link didn't help because I could open up modules under PowerShell virtual directory in IIS.
    I think since the event log is saying MSExchangeSyncAppPool.config and DefaultAppPool.config not well-formed XML, that might be a clue.
    In the event id 2307 this is the message:
    The worker process for application pool 'DefaultAppPool' encountered an error 'Configuration file is not well-formed XML
    ' trying to read configuration data from file '\\?\C:\inetpub\temp\apppools\DefaultAppPool\DefaultAppPool.config', line number '2'.  The data field contains the error code.
    Valuable skills are not learned, learned skills aren't valuable.

  • Manage Mobile Device missing in Exchange Management Console

    Exchange 2007 SP1.
    So up until now, my organization did not support ActiveSync and we had it disabled for all users.
    This summer this will change, and we will start allowing ActiveSync devices to connect.
    As a pilot group I enabled 3 users.  They all connected with their devices days ago (two on Monday, the other on Tuesday).  When looking them up in the Exchange Management console, the Manage Mobile Devices option is not visible.
    If they go into OWA, their devices and all management options are listed there.
    I realize that I could go into ADSIedit and set msExchMobileMailboxFlags to 1 and then it would show up.  That isn't really my concern though. 
    My concern is that when a user leaves the company, we would like to be able to go into EMC and issue a wipe of their device, not have to give ourselves permission to their mailbox, log in to their mailbox via OWA, and issue the wipe there.
    Anybody know why this happens (why a user with a mobile device doesn't get the Manage Mobile Device option in EMC)?
    Thank you

    Hi
    Here's a link for how to wipe a device remote
    http://technet.microsoft.com/en-us/library/aa998614%28EXCHG.80%29.aspx
    Hope it will be helpful for you!
    Jonas Andersson MCTS: Microsoft Exchange Server 2010, Configuration | MCITP: EMA | MCSE/MCSA Blog: http://www.testlabs.se/blog
    Thanks for the link, but I know how to perform a remote wipe.
    My question would be why does the "Manage Mobile Devices" button not appear when highlight some users that do have Mobile Devices?  Yes I could go into the OWA of their mailbox to wipe their device.  Yes, I could use the Shell to wipe
    their devices.  But neither of these would be as convenient as just going into Manage Mobile Devices via Exchange Management Console and performing a wipe there.  Especially for my user admins.
    Right now I am basically looking at creating some script that goes in and makes sure that "msExchMobileMailboxFlags" is set to 1 for every user that has ActiveSync enabled.  My main issue is that I feel I shouldn't have to do this. :P

  • Setting EX2007 mailbox permissions with Exchange Management Shell not reflected in Exchange Management Console

    Hello,
    I'm trying to use PowerShell to script some mailbox permissions.  The mailbox permissions I set in the shell are not displaying in the EMC.  The command I'm using is:
    add-MailboxPermission -accessrights fullaccess -identity $username -user MYDOMAIN\$supervisor -confirm:$false
    I get confirmation from the shell:
    Identity             User                 AccessRights                                               
    IsInherited Deny
    MyDomain.net/Separa... MYDOMAIN\mysupervisor    {FullAccess}                                               
    False       False
    Afterwards, when I look in the Exchange Management Console for this user (Right click, Manage Full Access), even after allowing time for replication, I don't see this new permission reflected there.  But If I use Get-MailboxPermission
    $username, the permissions show up:
    Identity             User                 AccessRights                                               
    IsInherited Deny
    MyDomain.net/Separa... MYDOMAIN\mysupervisor    {FullAccess}                                               
    False       False
    Why is this addition not being reflected in the shell?

    Hi,
    The cmdlet you use to grant full access permission is right. If your case, please let "mysupervisor" access to this user's mailbox and verify if he/she can access it. Maybe Exchange Management Console has not been updated well.
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange management console initialization failure

    Hi all.
    One of my clients SBS 2011 standard servers downloaded some updates yesterday & since then both the Exchange Management Console & Shell fail to open. In addition mail to the smart phones no longer works. Everything else seems ok. Mail is delivered
    & received via Outlook, all services are running. I have tried uninstalling the updates, but the Microsoft C++2010 Redistributable that was installed yesterday does not appear in the list of updates to uninstall. Only one of these updates is listed
    which is from 2012. This is the first part of the problem to resolving this issue. There are no "hidden updates" I am sure that this update was the most likely to be causing this issue. Any clues as to how to remove this update?
    The Exchange Management Console error is below.
    Connecting to the remote server failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid.
    Exchange Management Shell errors.
    Connecting to the remote server failed with the following error message : The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure.
    Connecting to the remote server failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response
    from the destination computer. The content type is absent or invalid.
    I have checked the settings as per the following possible solutions.
    https://support.microsoft.com/kb/2027063?wa=wsignin1.0
    I have added & removed & added the WinRM IIS extension & ran WinRM Quickconfig
    I have checked Powershell directory in IIS on the problem server. Make sure SSL is not required. Allow
    only Anonymous access.
    I have run this command from the Windows Powershell - note the warning
    set-user yourusername -remotepowershellenabled:$true
    Warning: The command completed successfully but no settings of “domain.local/MyBusiness/Users/SBSUsers/User” have
    been modified
    Checked the ExchangeInstallPath environment variable
    Checked the application pool settings in IIS are set to Local System Identity
    About the only item I have not tries is to remove & reinstall the PowerShell directory. I will do this over the weekend.
    This server has been in operation for almost 3 years without an issue. Microsoft updates come down & now I have been working on the issue for about 6 hours. Any other ideas?
    Regards, Scott

    Explore Powershell Virutal Directory , what is the size of Web.config file?
    What happens if you browse Powershell VD ?
    Check the Powershell Application Pool
    Make sure Enable 32 bit application under advance settings is set to FALSE
    Perform an IISRESET
    Also refer to -
    http://blogs.technet.com/b/whats_on_scotts_mind_today/archive/2012/12/07/exchange-2010-unable-to-open-exchange-management-console-initialization-failed.aspx
    Binu Kumar - MCP, MCITP, MCTS , MBA - IT , Director Aarbin Technology Pvt Ltd - Please remember to mark the replies as answers if they help and unmark them if they provide no help.

  • Hide / Remove access to Organization Configuration in Exchange Management console Ex 2010

    Hello,
    I am planning to give EMC access to helpdesk and modified Helpdesk Role so that they have Mail Recipient Creation and Mail Recipents Assigned roles.
    Helpdesk are able to created new and also modify exixiting mail enabled objects fine.
    My boss wants me Hide / Remove access to Organization Configuration in Exchange Management console Ex 2010 as they are able to edit Client access policies. Is this possible ?
    Thanks,
    Ne0

    Hi,
    Please use the following cmdlet to check the permission of Helpdesk support group on all management roles.
    Get-ManagementRoleAssignment -GetEffectiveUsers | Where { $_.EffectiveUserName -Eq "Helpdesk support group" }
    Then you can remove some unnecessary permissions of the Helpdesk support group.
    Hope it helps.
    If there is any problem, please feel free to let me know.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • Exchange Management Console require workstation local administrative rights to run?

    Does launching the Exchange Management Console require local administrative permissions?  
    I understand I need Exchange permissions to perform Exchange tasks, but I am wondering what permissions are required just to run the Management Console?
    Jason Meyer

    Hi,
    If you just want to launch the EMC, you need not require any special permission.
    However, if you want to modify anything, you should assign the corresponding permission to the appropriate user.
    I recommend you refer to the following articles to understand the permission in exchange:
    http://technet.microsoft.com/en-us/library/dd351175(v=exchg.150).aspx
    AD Domain Rights Needed to Manage Microsoft Exchange 2010
    Hope this helps!
    Thanks.
    Niko Cheng
    TechNet Community Support

  • Fail in loading Exchange Management Console

    Please help:After Opening the Exchange Management Console and Clicking on "Microsoft Exchange On-Premises" ,I encountered the following error:
    <The following error occurred when setting up Remote Powershell session to 'ServerName.MyDomain.net':
    Closing remote server shell instance failed with the following error message : The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote Management service is enabled. For more information, see the about Remote Troubleshooting Help topic. >

    1. Remove the WinrmIIS Extension from "Programs and Features"
    2. Reboot the server
    3. Execute the cmd "winrm quickconfig". This adds an exception for the remote management in the Windows firewall.
    4. Install "Winrm IIS extension
    5. Try open Exchange Management Console
    Let me know what happens :)
    Thanks for your guide;
     "WinRM IIS Extension" is not installed.and firewall is off.
    When I open up the Exchange Management Console ,after these message : 
    <Initializing ...
    Setting up Remote Powershell session to: ServerName.MyDomain.net ...>
     I'm seeing these errors:
    <The following error occurred when setting up Remote Powershell session to 'ServerName.MyDomain.net':
    Closing remote server shell instance failed with the following error message : The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote Management service is enabled. For more information, see the about Remote Troubleshooting Help topic. >
    also When I open up the Exchange Management Shell,After several hours the below message remain:
    <VERBOSE:Connecting to  ServerName.MyDomain.net >

  • Exchange management console not able to access after rename the administrative AD account

    I had an administrative user account(AD Admin a/c) KXP004 that
    recently rename as RPS001
    The account which was working fine before renaming and was able to access the exchange console. Since I rename the account, everything is working fine except the exchange management
    console.
    When trying to access the EX Management console displays an error message saying it cannot find the new name. What can we do to make the exchange management
    console work for the renamed account? Please assist.

    Hi Sherieftkl,
    After renaming the administrator account in AD, did you log off and then log on by using the new administrator name? Please log on again and monitor the result.
    In addition, please also open Event Viewer and check if find some related events.
    -->Since I rename the account, everything is working fine except the exchange management console.
    By the way, if this issue just occurred for EMC, I also suggest that you should post the question in
    Exchange Forum. I believe we will get a better assistance there.
    Best regards,
    Justin Gu
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Exchange Management Console not showing anything....

    I have 2 Exchange 2010 servers in production.  My new server is installed, and ever since it was install, I have not been able to see anything under Exchange Management Console.  I receive no errors when I go through the Exchange Management Shell. 
    I don't receive any errors at all until I I try to Collect Organizational Health Data.  When I do this, MMC crashes and I have the option to unload the snap-in or report this error to Microsoft.  I can manage the Exchange environment from my first
    Exchange server with no issues. I am logged in as the domain administrator which has membership to the organizational management security group in the exchange security group.
    Any help is appreciated.

    Hi Lee,
    I suggest install the Exchange 2010 SP1 UR6 or later.
    I found a KB, please check whether we match the situation:
    An empty list returns when you try to use the EMC to specify a server to connect to in an Exchange Server 2010 SP1 environment
    http://support.microsoft.com/kb/2549183
    If this issue caused by permission. Please try to add Administrator into Organization Management (we have done) and Server Management roles via EMS.
    Add-RoleGroupMember "Recipient Management" -Member Administrator
    Add-RoleGroupMember "Server Management" -Member Administrator
    If you won't be able to do this then try adding Administrator user into both groups available in AD.
    If still not working, I suggest re-install it if you don't mind (since there is no data existed on the new Exchange server).
    Please using DASIEdit to check whether we have uninstalled the Exchange server completely.
    Hope it is helpful
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Exchange Management Console, Initialization Failed

    Hi,
    Today when i open the Exchange 2010sp1 EMC it gave me this error
    The following error occurred while attempting to connect to the specified Exchange Server HUBC01.contoso.int
    The attempt to connect to
    http://HUBC01.contoso.int/powershell using "kerberos" authentication failed: connection to remote server failed with following error message: The WinRM client cannot process the request because the server name cannot be resolved. for more information see
    the about_remote-troubleshooting help topic
    Your quick response really appriciated,
    Dilshan

    Hi Dilshan,
    Any updates?
    Please check whether "WinRM IIS Extension" is installed in the Server Manager->Feature. If not, please install it.
    Please also try to use another member of Organization Management to log on to Exchange to open EMC to test.
    Frank Wang
    I came across this thread when troubleshootinga a similiar problem.  I login to Exchange this morning and I'm unable to open EMC and get an Initialization Failed error message.  It states
    The attempt to connect to http://exchange2010server/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message: Access is denied.
    I'm curious if the proposed solution to this thread would solve my problem.  I'm a little stumped as to what could cause this, other than the fact a colleague of mine installed the Exchange management tools on his Win7 workstation.  That really
    is the only change that has taken place in the last week.
    Any thoughts?

  • Completely different objects in Exchange management consoles 2010 and 2013

    HI scripting guys,
    First, apologies for the non-specific title. This is not the first incompatibility I am finding (e.g. scripts perfectly working in exchange console 2010 do not work in 2013).  
    Here is my current problem. I spent a good amount of time, but shame on me could not solve it.
    I run the following line:
    Get-MailboxPermission $mailbox |select @{Name="Access";Expression={([string]::join(',', $_.AccessRights))}}
    and get what I want in EMC 2010:
    Access
    FullAccess, SendAs, ReadPermission
    FullAccess, DeleteItem
    FullAccess, DeleteItem
    However in EMC 2013 I get the following instead:
    Access
    System.Collections.ArrayList
    System.Collections.ArrayList
    System.Collections.ArrayList
    Which is a clear sign that at some point the objects are different. 
    Edit: Just before sending this, I added out-string this way:
    Get-MailboxPermission $mailbox |select @{Name="Access";Expression={([string]::join(',', ($_.AccessRights|out-string)))}}
    which made the script to work in both consoles but introducing the nasty ellipsis:
    Access
    FullAccess, SendAs, ReadPermission...
    FullAccess, DeleteItem...
    FullAccess, DeleteItem...
    Piping the above to "format-table -wrap -autosize" is not a solution. It helps with the ellipsis but introduces blank lines:
    Access
    FullAccess, SendAs, ReadPermission
    FullAccess, DeleteItem
    FullAccess, DeleteItem
    I would greatly appreciate if you can help me with this !
    Thank you !

    one day later, mission accomplished.
    joining strings is not necessary and should be removed in that line in ems 2013 because each "row" is a single string. In contrast in ems 2010 the permissions for each user are an array of strings which need to be joined first in order to user
    "replace" further.  For example in ems 2013 my actual line now looks like this:
    Get-MailboxPermission $mailbox |Select @{Name="User";Expression={$_.User.tostring().replace("UVIC\","")}},@{Name="Access";Expression={$_.AccessRights.replace("Full","Full ").replace("Delete","Delete
    ")}}| sort user| format-table -auto
    and the output looks for example like this:
    Access
    Full Access, Delete Item
    Full Access
    Full Access
    Which is what I wanted to accomplish in the first place.
    =============================================
    Now since I could not find ANYTHING online about incompatibilities between Exchange management shell  2010 and Exchange management shell 2013 , let me share one more:
    it is about "send on behalf" permissions:
    after:
    $MBox = Get-Mailbox $MailboxName
    $SoB=$Mbox.grantsendonbehalfto
    things get different to list the users who has Send on behalf permissions for EMS 2013 and EMS 2010
    in 2010:
    foreach($S in $SoB){$S.name}
    while in 2013:
    foreach($S in $SoB){$S}
    again in EMS 2013 the things are simpler - $S is just a string

  • Exchange management console - fail to initialise - emt shooter contains unrecognised commands

    running on Windows SBS 2011:
    - possible due to tweaking system rights in order to get my backup working since the problem started after solving my backup issue in: http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/d21be14c-de84-479c-951d-751f5d47e857/#1128cda3-0a0d-4859-96cb-30fb4eff121e
    I tried the EMTshooter, maybe its because I'm using sbs 2011 and not all script commands are recognised any more?see output underneath this:
    Sorry Microsoft, getting pretty fed up, troubleshooting days on end. Is Windows SBS2011 standard, open source? Don't think so. Bought 50 user license, bad user experience, debugging your stuff on my account, thank you.
    EMT shooter:
    PS D:\installaties\EMTshooter> C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -noexit -com "d:\EMTshooter\EMT
    shooter.ps1"
    Security Warning
    Run only scripts that you trust. While scripts from the Internet can be useful, this script can potentially harm your
    computer. Do you want to run D:\EMTshooter\EMTshooter.ps1?
    [D] Do not run  [R] Run once  [S] Suspend  [?] Help (default is "D"): r
    Security Warning
    Run only scripts that you trust. While scripts from the Internet can be useful, this script can potentially harm your
    computer. Do you want to run D:\EMTshooter\EMTConnectFunctions.ps1?
    [D] Do not run  [R] Run once  [S] Suspend  [?] Help (default is "D"):
    File D:\EMTshooter\EMTConnectFunctions.ps1 cannot be loaded because you have elected to not run this software now.
    At D:\EMTshooter\EMTshooter.ps1:175 char:2
    + . <<<<  $loadpath
        + CategoryInfo          : NotSpecified: (:) [], PSSecurityException
        + FullyQualifiedErrorId : RuntimeException
    Welcome to the Exchange Management Troubleshooter!
    We recommend that you run the troubleshooter after making changes to
    IIS to ensure that connectivity to Exchange Powershell is unaffected.
    The term 'logevent' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the sp
    elling of the name, or if a path was included, verify that the path is correct and try again.
    At D:\EMTshooter\EMTshooter.ps1:189 char:9
    + logevent <<<<  $eventID $MessageAndParams $Type
        + CategoryInfo          : ObjectNotFound: (logevent:String) [], CommandNotFoundException
        + FullyQualifiedErrorId : CommandNotFoundException
    Checking IIS Service...
    The term '_CheckServicesStarted' 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 that the path is correct and try again.
    At D:\EMTshooter\EMTshooter.ps1:195 char:31
    + $noIIS = _CheckServicesStarted <<<<
        + CategoryInfo          : ObjectNotFound: (_CheckServicesStarted:String) [], CommandNotFoundException
        + FullyQualifiedErrorId : CommandNotFoundException
    The term 'resetWindow' 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 that the path is correct and try again.
    At D:\EMTshooter\EMTshooter.ps1:198 char:13
    +     resetWindow <<<<
        + CategoryInfo          : ObjectNotFound: (resetWindow:String) [], CommandNotFoundException
        + FullyQualifiedErrorId : CommandNotFoundException
    PS D:\installaties\EMTshooter>
    Regards, Chris.

    I recommend that you post your question to the SBS forum because wizards used in that product might best solve your problem.
    http://social.technet.microsoft.com/Forums/en/smallbusinessserver/threads
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Sap Management Console tool (NSP is in yellow - dispatcher stopped status)

    I have installed SAP ABAP Netweaver 7.03 trial version. I was able to log in through sap logon till day before yesterday. Today When i open sap management console, NSP appears in green initially and then turning to yellow completely. Process List  status shows (Disp+Work.Exe) stopped.
    How to make NSP to green flag.

    Hi boss, thanks for your help.....
    could u please guide me how can i check database is up and running or not....
    one thing, i want to tell you, when i was installation SAP, after oracle installation, i didnot load the oracle patch...becuase when i clicked on that patch, patch itself show error "Data error or corupted"... is it reason also for database which is not running. somebody told me ,,not necessary to upload the patch..anyway, if you have a patch,,please send me....
    Oracle version is: oracle 8.1.7
    please , i will really gratuful to you..also guide me , how can i check the database is running or not..

  • Remote Exchange Management Console "W3SVC isn't running on any Exhange servers in site" and always shows older version after SP2 or SP3 installed

    I'm trying to use EMC on a computer to remotely manage Exchange 2010 without having to do from the actual Exchange servers.
    First off, upgrading, uninstalling or installing EMC always fails on "Stopping" services. Seams to be a pretty common problem, but no clear fix other than deleting the registry entry (HKLM\SOFTWARE\Microsoft\ExchangeServer) and the
    "C:\Program Files\Microsoft\Exchange Server" folder. I'm guessing this is a bug since there should not be any Exchange services that need to be stopped on a computer where I'm just trying to use the EMC tool to manage Exchange.
    Next, is where when I open EMC I get "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." From all the reading I am pretty sure that this is due to the Exchange servers being on one version and EMC I'm trying to use is another version.
    This is the version our Exchange Servers are on:
    ProductVersion   FileVersion      FileName
    14.02.0375.000   14.02.0375.000   C:\Program Files\Microsoft\Exchange Server\V14\bin\ExSetup.exe
    Which finally brings me to the part where no matter what SP I install to run EMC it always shows:
    ProductVersion   FileVersion      FileName
    14.01.0218.015   14.01.0218.015   C:\Program Files\Microsoft\Exchange Server\V14\bin\ExSetup.exe
    I've tried SP2, and even SP3 hopeing that an even newer version would let me connect to Exchange, but no matter what it always shows the 14.01 version above.
    I've also tried installing "Exchange2010-KB2874216-x64-en" which should be the same version we are on (Update Rollup 7 for Exchange Server 2010 Service Pack 2), but get a Windows Installer Error stating, "The upgrade patch cannot be installed
    by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program." This Error probably makes sense if no matter what I do I'm stuck with a version prior to SP2. 
    Any ideas?

    Hi,
    From your description, I would like to clarify the following things:
    1. Make sure the World Wide Web Publishing Service is running in Exchange server.
    2. Ensure that the account you use to open EMC is a member of Organization Management role group.
    3. Based on my knowledge, the error "The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program." occurs if you install
    the RU for a different SP. Please re-download the Service Pack 2 and install it on the remote computer since it hasn't been installed successfully from the above information.
    What's more, here is a similar thread for your reference.
    Unable to install Update Rollup 4 for Exchange Server 2010 Service Pack 2
    https://social.technet.microsoft.com/Forums/exchange/en-US/677c21ed-e125-41c1-a468-c268e1f21f8e/unable-to-install-update-rollup-4-for-exchange-server-2010-service-pack-2?forum=exchange2010
    Hope this can be helpful to you.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

Maybe you are looking for