Skip to main content

Exchange 2010 Management Console "Initialization failed"

I'm migrating from Exchange Server 2003 to Exchange Server 2010. The installation of Exchange Server 2010 is almost complete but stopped me in Exchange Management Console with the error "Initialization Failed". No worries, so I logged in forums and search this error. I spent at least 30 to 60 minutes reading all the posts but no success finding solution to my problem. So I called Microsoft Professional Services where I will pay $259 + $15Tax per incident to address this issue.

Microsoft Exchange Server 2010 Best Practices (Best Practices (Microsoft))Error "The following error occurred when searching for On-Premises Exchange Server:
[server#.Domain] 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. For more information, see the about_Remote_Troubleshooting help topic"

To make the story short and correct this issue, follow this simple steps.

  1. In Windows Server 2008, InetPub, wwwroot folder, and rename web.config to web1.config. To rebuild the web server config.
  2. In Services, restart IIS Admin Service.
Check it, run Microsoft Exchange Management Console and it should work. You will not see the Initialization Failed error again. If you still having issue, please join this forum for discussion.


  1. Initialization failed
    The following error occurred whilst searching for the on-premises Exchange Server:
    No Exchange servers are available in any Active Directory sites. You can't connect to remote Powershell on a computer that only has the Management Tools role installed. It was running the command 'Discover-ExchangeServer -UserWIA $true -SuppressError $true -CurrentVersion 'Version 14.1 (Build 218.15)".

  2. Thanks alot for this. You've saved me a lot of time and trouble.

  3. This comment has been removed by the author.


Post a Comment

Popular posts from this blog

Alternative Social Networks

If you are planning to create your social network e.g. similar to Facebook. Here's a short list of alternative software's:

Open Source and Free​ - Wordpress (Open Source and Free) - (Open Source and Free)Commercial Social Networks software ($299 Stand Alone, $29/mo Cloud) (run with Joomla, need to know CMS) (very expensive, $399 for Standard) (from free to Commercial, I left my networks and they are selling it (I used this before, it's hard to maintain. I moved to NING but left too after it was sold to another company) (I don't recommend using this service, it's hard to export your data when it's time to move)Something to check when selecting your next soc…

Frequent Account Lockout in Active Directory

I have a user in Windows Pro 7, and Windows Server 2003 environment that is frequently account locked out. I tried many different scenarios to resolve this account lockout issue, from resetting his password, changing a new password, remove and re-join the domain, rebooting the workstation and active directory servers.

I tried to use the command prompt utility to run "rundll32.exe keymgrdll, KRShowKeyMgr" (case sensitive) to delete the account in Windows 7 password cache, and still no luck.

Still searching for answer ... Let me know if you encounter a similar issue in Windows Pro 7 and Windows Server 2003.

Continue reading updated post here:

Example of Out of Office Reply for Terminated Employee

This is a sample message that I used for terminated employees, unless HR staff specified a different message.
=== Example for KING.NET Employee === John Doe (employee or consultant) is no longer with KING.NET effective June 1, 2008 (termination date). For matters relating to "Project Name here" please direct your concerns to John Smith at (Manager or Supervisor). For all other matters, please direct your email to Mary Smith HR at
Please call our main office 703-345-6789 if you have other concerns.
Thank you.
=== end of message ===