exchange 2013

I created and applied enterprise CA on Exchange server 2013 and after migrating mailboxes from 2007, I removed other certificate from Exchange server 2013 including SS certificate. Now Exchange 2013 does not allow me to open EAC or powershell. Do I have to recreate another SS cert and apply on IIS.
LVL 4
pchettriIT DirectorAsked:
Who is Participating?
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.

Will SzymkowskiSenior Solution ArchitectCommented:
Did you remove the Self-Signed cert from the Exchange server?

You need to run the following command from the Client Access Server.

New-ExchangeCertificate

This will then create a new Self-Signed Cert. This will allow you to get back into the ECP.

However if you want to use your Cert externally then you are going to have to generate a new CSR. I have outlined all of the steps required to do this on my site.

http://www.wsit.ca/how-tos/exchange-server-2/exchange-2013-certificate-generation-csr-import-enable-exchange-certificate/

Will.
0
pchettriIT DirectorAuthor Commented:
I found an article https://support.microsoft.com/en-us/kb/2779694?wa=wsignin1.0 which fixed the issue.
Created a new SSL and assigned to 444 on back-end vdirectories of IIS.

Thanks for your response.
0

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
pchettriIT DirectorAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 500 points for Will Szymkowski's comment #a40813090
Assisted answer: 0 points for pchettri's comment #a40813180

for the following reason:

I found an article https://support.microsoft.com/en-us/kb/2779694?wa=wsignin1.0 which fixed the issue.
Created a new SSL and assigned to 444 on back-end vdirectories of IIS.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

pchettriIT DirectorAuthor Commented:
I found an article https://support.microsoft.com/en-us/kb/2779694?wa=wsignin1.0 which fixed the issue.
Created a new SSL and assigned to 444 on back-end vdirectories of IIS.

Thanks for your response.
0
Will SzymkowskiSenior Solution ArchitectCommented:
Not sure why my answer was revoked?

Will.
0
pchettriIT DirectorAuthor Commented:
did use the command New-ExchangeCertificate before applying actual fix from microsoft
0
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
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.