Hi, having a bit of trouble with an SSL cert on SBS2k3 and hoping for some
clarification.

Box is SBS2k3 SP2. The box only hosts RWW on port 443 and SPS on 444. We
have set up a domain as remote.domain.com, which is fully DNS'd and works
well.

Problem is the usual self-signed cert issue in browsers. To eliminate this
we obtained an SSL cert for RWW by using the default website in IIS to
generate the CSR, and installed the cert for port 443. Works great.

However, in IIS we generated also a CSR for a cert for SBS using the
companyweb site. It validated and we installed the cert (which has
companyweb as friendly name in it) without issue for port 444. Browsers,
however, still get the 'Cert Problem' screen, this time indicating the cert
was issued to a website with a different name. Again we used the friendly
name companyweb in the CSR, and of course the remote.domain.com domain.



Can anyone help me sort this SPS site cert issue out?

Thanks,

Fred Orcutt

Hi Fred,

Did you follow this procedure?

How to Install a Public 3rd Party SSL Certificate on IIS on SBS 2003
http://blogs.technet.com/sbs/archive...-sbs-2003.aspx

--
Merv Porter [SBS-MVP]
============================

"Fred Orcutt" <forcutt@newsgroup-technology.net> wrote in message
news:OkoGRe3SKHA.4144@newsgroup

> Hi, having a bit of trouble with an SSL cert on SBS2k3 and hoping for
> some clarification.
>
> Box is SBS2k3 SP2. The box only hosts RWW on port 443 and SPS on 444. We
> have set up a domain as remote.domain.com, which is fully DNS'd and works
> well.
>
> Problem is the usual self-signed cert issue in browsers. To eliminate
> this we obtained an SSL cert for RWW by using the default website in IIS
> to generate the CSR, and installed the cert for port 443. Works great.
>
> However, in IIS we generated also a CSR for a cert for SBS using the
> companyweb site. It validated and we installed the cert (which has
> companyweb as friendly name in it) without issue for port 444. Browsers,
> however, still get the 'Cert Problem' screen, this time indicating the
> cert was issued to a website with a different name. Again we used the
> friendly name companyweb in the CSR, and of course the remote.domain.com
> domain.
>
> Can anyone help me sort this SPS site cert issue out?
>
> Thanks,
>
> Fred Orcutt
>