Its looks like your server may part of a GPO which is auto enrolling a
server certificate, however it is confusing as to why the new cert is being
used. You can view the installed certificates using the certificates MMC
snap-in, make sure you view the "computer account" personal store. This may
give you a better idea of what is happening with your certificates.
For your second issue - your certificate common name (you entered this when
you created the certificate request) must match the FQDN that you want your
users to enter into their browsers to access your web site, e.g web site is
accessed via
http://www.microsoft.com - common name must equal
www.microsoft.com (note you do not include the http://).
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only
[quoted text, click to view] "Andy" <Andy@discussions.microsoft.com> wrote in message
news:ED095665-4361-46DB-900E-6F10856E7DE2@microsoft.com...
>I issued Certificate using WebServer Certificate Template. I installed it
>at
> Directory Security, Secure Communications, Server Certificate... and
> secure
> site is functional. However after restarting Windows my certificate always
> got replaced by another certificate. Site also works but it prompts first
> that site name doesnt match. How can I prevent this annoying certificate
> behavour?