Comments on: Exchange 2010 Management Console Initialization Failed

By: Eric Weintraub

Eric Weintraub — Mon, 05 Dec 2011 13:15:13 +0000

OMG thank you so much, I was using a test lab with Hyper-V and didnt think to check the time.

By: sarbjit

sarbjit — Tue, 01 Nov 2011 08:34:17 +0000

this was helpful.
did a net time / set after turning off the Hyper-v time sync. It all worked.

Sarbjit

By: jabarca84

jabarca84 — Thu, 27 Oct 2011 17:13:54 +0000

Hi Paul

Thanks. This solved my problem. Time sync problem.

Regards!!

By: S E

S E — Mon, 12 Sep 2011 17:45:51 +0000

It really was just a Time setting for the system. When running Exchange in a VM, if you sync the Time of the Guest OS to the ESXi host using VMtools, you need to make sure that the ESXi host time is consistent with the time on the host of the Active Directory too. Best way is to use NTP client on ESXi so they are surely synchronized. Otherwise disable time sync between the host and the guest and make sure everything is within a few minutes of each other. But NTP is really the smartest choice. Once the times are set, you might have to disable then re-enable the time sync in VMtools and all should be fine again.

By: Exchange 2010 Management Console Initialization Failed « Viral Rathod's Blog

Wed, 31 Aug 2011 06:09:35 +0000

[...] If the above steps does not resolved the issue then Try this all http://social.technet.microsoft.com/Forums/en/exchange2010/thread/6a9e66d8-6ecd-471d-8adb-da3b99fdfea3 http://exchangeserverpro.com/exchange-2010-management-console-initialization-failed [...]

By: Paul Cunningham

Paul Cunningham — Wed, 25 May 2011 03:23:54 +0000

Hi Kevin, you can’t connect to a remote Exchange 2003 server/org with the EMC for Exchange 2010. I believe you will need to run the mailbox move requests via the Exchange Management Shell instead.

By: Kevin

Kevin — Tue, 24 May 2011 19:01:27 +0000

Paul: good post but i’ve got a different error and hoping you can point me in the right direction. “The attempt to connect to http://server/powershell using “kerberos” authentication failed: connecting to remote server failed with the following error message: The winRM client sent a request to an http server and got a response saying the requested http url was not available. This is usually returned by a http server that does not support the ws-management protocol”

This is what i get when trying to connect emc 2010 to a 2003 server to try to add a new forest to start the mailbox migration process. any ideas would be totally apperciated

By: Stephen Lloyd

Stephen Lloyd — Wed, 06 Apr 2011 09:26:16 +0000

Nice post Paul. I’ve been racking my brain trying to find a decent post to resolve this issue. I even came close to throwing in the towel and trying a recover on Exchange box.

Good call, and exact message error in Google – homed it in !!!

Thanks…

By: Paul Cunningham

Paul Cunningham — Tue, 15 Feb 2011 11:15:59 +0000

Certificate issue perhaps. I’ve seen it break when people mess with SSL certs via the IIS mgmt tools.

But yeah you might have gone one step too far with all that role stacking

By: Chad Solarz

Chad Solarz — Tue, 15 Feb 2011 02:19:42 +0000

Nice post paul. hoping you were gonna be able to save the day for me once again. I guess i went to the well one too many times. I know it’s way out of best practices, but i have one consolidated box. DC / Exch 2010 & Ocs 2007 R2. Unsure when it happened, but can’t authenticate to EMC or EMS due to the following error. Not a time issue, even tried resetting the computer and user account passwords.

Did the winRM thing, no luck

IIS seems to have a binding to port 80 on the default website too.