Skip to main content

Featured Post

Exchange Admin Center language

Depending on your computer language settings, Exchange Admin Center can take those and open in a language you actually don't want to use.
You'll Google that this can be changed if administrator/ admin user has mailbox by openening OWA settings and changing Regional parameters.

But usually Admin user does not have mailbox or you don't want her/him to have it. You will search again and find that you can add mkt=en-US (as an example) to the URL of the Exchange Admin Center (https://yourexchangehostname/ecp?ExchClientVer=15&mkt=en-US)

Third option you have is opening Internet Explorer settings (I am using Windows 2016)

Click languagesClick Set Language Preferences

Add language you want to use by clicking Add language
Use Move up or Move Down options to put desired language on topClose Internet ExplorerOpen it again and login again to Exchange Admin Center

The attempt to connect to http://yourserver/PowerShell using "Kerberos" authentication failed

The error you get: The attempt to connect to http://yourserver/PowerShell using "Kerberos" authentication failed: 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

If you removed Exchange server from the machine and installed it again, you can get following error when you open Exchange Management Console:
The following error occurred while attempting to connect to the specified Exchange server '':The attempt to connect to using "Kerberos" authentication failed: 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.

The solution is to first export and then delete
HKCU\Software\Microsoft\ExchangeServer\v14\AdminTools\NodeStructureSettings (REG_BINARY key) registry key.

All credits go to Paul Newell on this forum


  1. anybody tried this? was it successful?

  2. Well, actually everything that you see on this blog was in fact done by me and tested before it is put out for public. There are no "sounds like" stories here. Just facts. :)

  3. This fixed did indeed fix my issue! consider it tested

  4. yup worked like a charm

  5. This worked for me - confirmed nice easy fix. Thank You !

  6. No luck. Now it fails with "the client cannot connect to the destination specified in the request. Verify that the service on the destination is running." and yes, it's running.

  7. Thanks it worked but no before I restarted the server I am using 2008 R2, after deleted the registry key it showed another error message so I restarted and tried again to open EMC and it worked , restarted a couple of time and it keeps working. Thanks

  8. This worked perfectly.


  9. Thanks for this information, wish I had gotten this sooner.

    Greg Tench

  10. Thanks so much for this. You are a genius!

  11. No change here.

  12. I tried it, it work like a charm

    Thanks Dušan

    Mahmood Sabt

  13. Thank you very much for the great post Dusan, worked wonders in minutes!

  14. Truly saved my backside... Thanks my friend.

  15. Worked a charm. Thanks

  16. thanks.saved a lot of time for me.

  17. This worked perfectly. Note:I had to log off after and log back in before it worked. Thank you for this article. -Willy

  18. We havn't un/installed Exchange and have 3xMB 3xCas 2xEdge... Oddly I could connect to the EMC on everything except one of the MB servers.

    Removing this key on that one server fixed the issue!


  19. i tested it and its worked right away :)

    Million Thanks

  20. Thank you that was a quick and easy fix, that came up on my first search for the issue. Well done!

  21. This procedure works, only need to IIS reset

  22. Worked for me - didn't need an IIS reset or server reboot. Made the change and launched EMC, right in. Still get an error on PowerShell but otherwise EMC works...

  23. Спасибо огромное, очень пригодилось.

  24. It didn't work for me, I had to restart IIS in order for it to connect. the problem happened when I changed the local DNS to an external one in order to check whether Exchange's Hybrid wizard will be able to confirm the public DNS changes for my domain. but didn't work.

  25. This worked perfect for me after an IISreset, no need to reboot server.

  26. experienced the same issue with EMC on exch2010sp3/w2008r2 server after applying Windows patch for wannacry virus, i ve tried all the solutions posted here without succes, finally got it to work again by modifying this IISmanager>default web site>ecp>Windows authentication>Advanced setting> extended protection = accept (it was on OFF)

    thanks everybody


Post a Comment

Popular posts from this blog

Error "<#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP#" when you send attachment in your mail

Some users were receiving error <#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP# when they sent message with attachment. The problem is when attached document name is longer than 50 characters. Some Firewalls have header size restriction and that limit blocks this messages to be sent. To correct this, change header limit on affected Firewall or shorten the name of the document you are sending (which is probably not good permanent solution).******
Update #1: Default header size limit in Exchange 2007 is 64K.Update #2: It might be the SMTP version problem. Mail is rejected with CONTENT-DISPOSITION error (overly long message header field for CONTENT-DISPOSITION) but not for all SMTP servers (same mail sent through different SMTP servers). If you send mail with attachment that has name longer than 50 characters from Exchange 2007 directly through DNS you may encounter this error, but if you send same mail from Exchange 2007 through smart host (other than Exchange) mail is d…

Change SMTP port 25 in Exchange 2007, 2010

For some reason you might want to change default SMTP port number 25 Exchange 2007 is using. Exchange 2007 uses RECEIVE AND SEND connectors, one for receiving mails and other for sending mails (obviously ;)
So you need to change ports on those connectors. I will not say those two, because you might be using more than two.
You change Receive connector port by opening the connector properties in Exchange Management Console --> Hub Transport --> RECEIVECONNECTORNAME --> Properties --> Network --> Local IP Addresses (Edit Receive Connector Binding)
Just to clarify what "Local IP Addresses" and "Remote Servers" are (from Exchange 2007 help), because I find it little bit confusing: Use these local IP Addresses to receive mail Use this list to specify the IP addresses and port numbers on which this Receive connector listens for incoming mail. Receive mail from remote servers which have these IP addresses Use this list to specify the remote IP address range fr…

Move-ActiveMailboxDatabase - Failed

If by any chance you see the error below after updating the server which is part of DAG, just suspend and then activate the database copy. Exchange will resynchronize the copies and you’ll be able to move the database. You do that by clicking on the database under Database Management, then select non active copy in the Database Copies window, right click on it and select Suspend Database Copy. Repeat the step and select Resume Database Copy.
An Active Manager operation failed. Error The database action failed. Error: An error occurred while trying to validate the specified database copy for possible activation. Error: Database copy 'DBx' has been blocked from activation on server '' by an administrative action. Reason: None specified.. [Database: DBx, Server:]
An Active Manager operation failed. Error An error occurred while trying to validate the specified database copy for possible activation. Error: Datab…