Exchange 2010 EMC Initialization Failed, why?

MS Exchange server 2010 EMC Initialization failed

This is using 1 MS Exchange server 2010 in MS Windows 2008 R2 AD environment. Exchange was working fine until 1 week ago, when we replace the ssl certificate from MS Certificate service originally to GoDaddy. We replace to use GoDaddy SAN SSL Certificate to support autodiscover.* and exchange.* public host names. We ran the new exchange certificate on EMC, got the req, and then sent this req file to GoDaddy. Finally, we got the ssl certificate. However we didn't apply this certificate to Exchange server for the past few days until yesterday. When we wanted to open the emc, we faced with this Initialization problem as attached.

It looks like a Windows Remote management service issue, however, the service is started, and restarted without problem. Further checking on all the Exchange services, all are started without problem. What could be the issue? how to resolve?

thanks in advance.
EMC-Intialization-Failed.JPG
LVL 1
MichaelBalackAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Hasin Ahmed ChoudharyExchange AdministratorCommented:
Have you assigned all services in exchange to third party (GoDaddy) certificate? Specifically IIS ?
MichaelBalackAuthor Commented:
Hi Hasan,

no, not yet.
Hasin Ahmed ChoudharyExchange AdministratorCommented:
Okay, so service is still present on an Old cert. Just verify that cert has not expired.

Few more things to try:
1) Try running EMS on that server, can it auto connect to Exchange Snap-Ins?
2) Try opening EMC as admin once.
3) What if you try to run the same cmd from EMS  (if connecting) as shown in error <Discover-ExchangeServer*****  copy it from error screenshot>.
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Hasin Ahmed ChoudharyExchange AdministratorCommented:
Veerappan SundaramSenior Technical ConsultantCommented:
If the issue continues even after the above recommendations from @Hasin,
Check the Proxy settings in Internet explorer on exchange server - Manual proxy or Auto Proxy should not be enabled.
MichaelBalackAuthor Commented:
Finally, I restored the backup VMs, and everything settled.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MichaelBalackAuthor Commented:
By restoring from the backup image, it works.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Powershell

From novice to tech pro — start learning today.