This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have been setting up a new Exchange Server 2019 and am stuck with the syntax to generate an SSL CSR via powershell where the domain name is not in the US
example mycompany.com.au and the FQDN of the server to be used in the cert is mail.mycompanyname.com.au
Is this the correct syntax for an .AU domain
New-ExchangeCertificate -GenerateRequest -RequestFile "\\mymailserver\share\Mail.mycompany.com.au Cert.req" -FriendlyName "Mail.mycompany.com.au Cert" -SubjectName "C=AU,CN=mail.mycompanyname.com.au"
Okay I've found that because I am on CU12 there may be more to the command than I have from Docs resources
So - Its exchange 2019 with CU12 on Server 2019 Std V1809
The syntax
$request = New-ExchangeCertificate -GenerateRequest -SubjectName "c=US,o=Woodgrove Bank,cn=mail.woodgrovebank.com" -DomainName autodiscover.woodgrovebank.com,mail.fabrikam.com,autodiscover.fabrikam.com
Set-Content -Path "\FileServer01\Data\woodgrovebank.req" -Value $request
NO matter what I use as the path it says Set-Content : The network name cannot be found.
This doc https://learn.microsoft.com/en-gb/exchange/architecture/client-access/create-ca-certificate-requests?view=exchserver-2019 is different to https://learn.microsoft.com/en-us/powershell/module/exchange/new-exchangecertificate?view=exchange-ps where both refer to the same thing
Hi @Shane King
I am writing to see how everything is going on with this thread. If you still have further concern on this, please feel free to let us know.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi there,
The RequestFile parameter that takes the UNC path as input was removed with the 2022 H1 Cumulative Updates release. To export the requested file to a UNC path, you must use the Set-Content cmdlet.
For the error, network name cannot be found it occurs if one of the following conditions is true:
-The network components on the domain controller are not configured correctly.
-You did not update the network drivers on the domain controller
-The server is unavailable or unreachable.
You can follow the troubleshooting steps from the below article and see if that helps you
https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/system-error-67-network-name-cannot-be-found
----------------------------------------------------------------------------------------------------------------------------
--If the reply is helpful, please Upvote and Accept it as an answer–
Hi @Shane King
For the error "The network name cannot be found." you received, please check if you have correctly set the sharing/permission for this path "\FileServer01\Data"
You could try using "Run" to access this path to see if any issue:
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.