Export Exchange 2016 certiifcate error.


i am trying to export the exchange certificate from an Exchange 2016 server but i get the error :
  Special Rpc error occurs on server ***** : The private key couldn’t be exported as PKCS-12. It either couldn’t be accessed or isn’t exportable.”

Any help?

Thank you in advance.
Who is Participating?

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

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.

Jeff GloverSr. Systems AdministratorCommented:
Well, it sounds like you didn't mark the key as exportable when you ordered it. I assume this is the Public certificate? Can you export it via the Certificates MMC on the Server? If not, you may have to get it reissued with a new CSR marking the key as exportable.
Comp_supportAuthor Commented:

It is a self-signed key and if remember well , i selected exportable during installation.

In any case i have to create a new certificate ?
Jeff GloverSr. Systems AdministratorCommented:
If you need to export it and cannot, then yes. If it is a self-signed cert then it is easier I guess. We never use them so I cannot help you there.
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Adam BrownSr Solutions ArchitectCommented:
There isn't really a reason that a Self-Signed Certificate should be exported with the private key included. The private key is only necessary if you are planning to import the certificate for use on a different server, which would be pointless, since the Self-Signed Certificate would only have the server name of the server you're exporting from. It would never be valid on any other server. If you are trying to export it to allow import for the purposes of establishing certificate trust on clients that access the server, you don't need the private key.
Comp_supportAuthor Commented:
Finally the problem was something else.

I was trying to connect remote and local users to exchange 2016 server.

There was a problem with the local DNS zones and the hosting service of the domain. After fixing that , the users are connected properly.

Thank you for you assistance.

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
Seth SimmonsSr. Systems AdministratorCommented:
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

Accept: Comp_support (https:#a42410345)

If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

Experts-Exchange Cleanup Volunteer
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

From novice to tech pro — start learning today.