1. Having renewed and installed our wildcard certificate we now have two wildcard certificates installed on the Windows 2003 server for the same *.domain.com; one of which is about to expire. Although the new wildcard certificate is a renewal of the existing one it is appears to be essentially a new certificate, with both certificates coexisting on the same server.
2. Two web sites have been configured in IIS6 to use the new certificate: the first is a new temporary web site which was created specifically to generate the certificate renewal request, and the other an existing web site initially using the old certificate. The secure binding of each of the two web sites has been reset using the standard command form below, and the corresponding application pools restarted:
cscript adsutil.vbs set /w3svc/nnnnnnnnn/SecureBindings ":443:SiteName.domain.com"
There also exist several other web sites currently using the old certificate which have not yet been reconfigured.
3. The problem is this: when either of the above two web sites is visited via a browser; the browser always shows the old certificate and not the new one. However the IIS6 properties of both web sites confirm they are configured to use the new certificate.
Can anyone suggest how to mobilize or activate the new certificate - preferably without having to reboot the server endless times or hack the certificate store?
Thanks in advance.
