Have you done this part of it? You need to recreate the certificate request first. Double check to make sure the cert you have is compatible with FMS 14.
Thanks for the reply and link Joshua.
I have not completed the steps outlined in the "Creating a new custom SSL certificate"
I guess I'm wondering why I have to create a new certificate when no details other then the FMS version has changed on my server - Server name has not changed.
Are certificates that were compatible with FMS 13 not compatible with FMS 14?
Thanks again and Happy Monday everyone!
I followed the direction in the linked article.
I deleted the existing serverRequest.pem and serverKey.pem located in the CStore directory.
Successfully ran the fmsadmin certificate create command which created the new serverRequest and serverKey files inside my CStore directory.
I get an error when I run the import command "This certificate does not match the key file"
Inside the directory I received from thawte are the following files
Which file do I point to when running the import command?
I tried running the import command once for each file but continue to get the error "This certificate does not match the key file"
Once you have the certificate request from FMS, you need to have the certificate reissued from your vendor. My experience was that the cert needed to be reissued. Maybe it's not needed, but I couldn't get it to work without it.
Once you have the new cert, you just need to import that cert file ( the actual certificate file ). With the new cert file it should make the key that was generated when you generated the request file in the previous step.
Thanks again Joshua!
You were correct - the issue was I needed to get a new cert.
I also need to restart the server after the import to get web direct to recognize the new cert.
Confusing stuff but I have taken note of the steps for next the time I need to upgrade FMS or the OS.
Now back to work!
Great work. The process isn't really difficult, but yet it is!!