I am currently struggling with an Epicor server deployment because I cannot get the Epicor server to “behave” after selecting an SSL certificate issued by GoDaddy (details purposefully left out, unless you reeeeaaaaalllly want to know).
My IT manager opened a case with EpicCare and was summarily told —
This isn’t something Technical Support can assist with. We have a Professional Services team that can help you with getting this outside certificate to work on your servers since it involves your network/IIS/Security setup.
The new install guide was also provided in the case history for us to review (we already have a copy of this, for obvious reasons). However, selecting an “existing certificate”, or a self-signed certificate is noted in the guide as part of the general setup and is not something identified as requiring Epicor Professional Services to implement:
(starting on page 42)
5.In the SSL Certificate Options dialog, select one of the following options, based on your requirements:
• Pick an existing SSL Certificate.
When you select this option, the Windows Security - Select a Certificate dialog opens and displays the available certificates. You can click More choices to view all available certificates. Select the certificate you want to use for Epicor Server and click OK. The SSL certificate you pick must have a Friendly Name assigned so that the Epicor ERP servercould recognize it. For information on how to verify and assign a Friendly Name to a certificate, review the Troubleshooting section in the System Administration Guide or the Epicor ERP 10.2 Installation Guide.
• Generate a new Self Signed Certificate.
Shouldn’t assistance with errors in this part of the installation process be handled by EpicCare, as it is one of the options listed in the new installation guide?
In my layman opinion:
This seems like it should be a very common and simple aspect of the Epicor server deployment process to resolve.
We can’t be the only customer site in the “EpicSphere” who has ever tried to deploy with an existing SSL issued by GoDaddy (or other SSL issuer)
It’s listed in the new installation guide and is not a deployment configuration that we’re “experimenting with”, or Frankensteining together under the direction of Joe Internet from some obscure forum. It’s – in – the – guide.
What am I missing here?