We help IT Professionals succeed at work.
Get Started

SSL Certificate Name Mismatch windows Server 2012 R2 Internal CA

Last Modified: 2015-02-27
We have recently set up an internal CA for the purpose of internal SSL certificates (and eventually other things like Direct Access but thats for a later date...). Being new to the Certificate game this wasn't the quickest process in the world for me.

Through group policy all of the domain computers now happily recognise the CA as a root certificate authority. The machines that I have given permission to the certificate template can also request SSL certificates through the certificate manager quite happily.

However the certificate that is issued is issued with the FQDN (webserver.domain.com), which means that when clients connect to https://webserver they get a certificate mismatch and have to connect to https://webserver.domain.com.

I am sure I may need to provide more information. But how would I go about issuing these SSL certificates from my internal CA to the computer name rather than FQDN?

Watch Question
Distinguished Expert 2019
This problem has been solved!
Unlock 1 Answer and 3 Comments.
See Answer
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE