Comments on: How to Generate an SSL Certificate Request in Exchange Server 2016

By: Aryan

Aryan — Thu, 25 Aug 2022 06:35:01 +0000

I searched on net but could not find a sure shot way to create a private key exportable cert request. The GUI doesn’t have any option for it and on shell the command mentioned by MS also fails
$txtrequest = New-ExchangeCertificate -PrivateKeyExportable $True -GenerateRequest -FriendlyName “Contoso.com SAN Cert” -SubjectName “C=US,CN=mail.contoso.com” -DomainName autodiscover.contoso.com,legacy.contoso.com,mail.contoso.net,autodiscover.contoso.net,legacy.contoso.net
[System.IO.File]::WriteAllBytes(‘\\FileServer01\Data\Contoso SAN Cert.req’, [System.Text.Encoding]::Unicode.GetBytes($txtrequest)).

Can anyone advise what I am doing here?

By: Nimeshin Govender

Nimeshin Govender — Mon, 12 Apr 2021 12:13:37 +0000

In reply to John B. Hi Just an update as I have managed to get passed this error. It was actually the Mcafee antivirus that was blocking the CSR file from being generated. So check your antivirus or firewall on the server that could be blocking the request. Another thing to do is add the Exchange Trusted subsytem account with full access to the shared folder.

By: Nimeshin Govender

Nimeshin Govender — Mon, 12 Apr 2021 10:12:04 +0000

In reply to John B.

Hi,

Did anyone fix this error. Also get the same for exchange 2013

Thanks

By: Sregio

Sregio — Fri, 26 Feb 2021 05:49:56 +0000

Can I make a request from any domain computer from mmc – certificate?

By: George Salambassi

George Salambassi — Thu, 12 Nov 2020 19:07:49 +0000

How would you change the period of validity in the CSR?

By: Brendon Lieberz

Brendon Lieberz — Mon, 27 Jul 2020 15:14:51 +0000

Not sure if anybody still gets the error message on the UNC path. Just specify the FQDN of the server in the path.

By: Vince MacNeil

Vince MacNeil — Mon, 11 May 2020 14:30:44 +0000

In reply to John B. Did you figure this out? I have the same problem Thanks

By: Aanand Singh

Aanand Singh — Thu, 26 Sep 2019 07:37:37 +0000

In reply to Mike Willard.

I had the same issue as I was using remote server UNC path to save Cert.req file. It got fixed, after I have created local shared folder on exchange server and saved the request locally.

try that.

neither C$ nor C: worked for me when trying to save .req file on remote unc path.

By: John B

John B — Thu, 29 Aug 2019 12:52:30 +0000

Hi Paul,
Have just read your article here on requesting a certificate and have previously read your Exchange 2010 version, thank you,

I was not successful in creating an SSL certificate request with our Exch2010 installation so relied on its self created certificate. I have now installed our 1st Exch2016 server which I thought would be successful in this SSL requesting activity. However, it has not been the case. I get an unknown error message every time when following all the steps through.

The folder I am pointing to is empty, the file name is fine and I have changed it many times to elicit another response, Path name used is \\servername\sharename\certreq.req . All to no avail. It fails with:

The Exchange certificate operation has failed with an exception on server exch2016. The error message is unknown error 0xe0434352

No matter what I do I cannot get exchange to create the request. I have searched the internet for the error and cannot find a reference to it. I suspect that the underlying issue may not actually be exchange but at a loss as to where next to look?

I shall be grateful for any pointers you can offer

By: Test Lab Guide: Windows Server 2016 with Integrated Exchange 2016, SfB Server 2015 and SharePoint 2016 – A random blog from a sysadmin

Mon, 15 Jan 2018 11:38:29 +0000

[…] set, it was time to get a new certificate which reflect the above changes. I headed over to trusty practical 365 to refresh my memory. This time I used EAC when requesting a new certificate. I changed the domains to reflect my newly […]