In NT 4.0 days, you could use the key manager to assign more than one SSL
cert to a single IIS virtual web site, as long as each cert had its own
unique IP/port combo.

Is it possible to the same thing in IIS 5.0 or 6.0?   To get around it we
now have to create multiple virtual webs all pointing to the same file
space.  But that is WAY too cumbersome due to all the IIS metabase changes
we need to keep in sync between the virtual webs!  :-(

BTW, the reason we need to do this is that we have multiple DNS names
pointing to the same web site.

Cmon you IIS gurus, there's gotta be a way to do this.....

--Steve S.

[ Post a follow-up to this message ]

Are all the websites under the same domain ?
a.mydomain.com, b.mydomain.com and etc ?
if yes, you can get a wildcard *.mydomain.com cert.

if not, you will need individual site to bind those certs.

--
Regards,
Bernard Cheah
http://www.tryiis.com/
http://support.microsoft.com/
http://www.msmvps.com/bernard/



"Steve S." <SteveS> wrote in message
news:edLOy0JrEHA.896@TK2MSFTNGP12.phx.gbl...
> In NT 4.0 days, you could use the key manager to assign more than one SSL
> cert to a single IIS virtual web site, as long as each cert had its own
> unique IP/port combo.
>
> Is it possible to the same thing in IIS 5.0 or 6.0?   To get around it we
> now have to create multiple virtual webs all pointing to the same file
> space.  But that is WAY too cumbersome due to all the IIS metabase changes
> we need to keep in sync between the virtual webs!  :-(
>
> BTW, the reason we need to do this is that we have multiple DNS names
> pointing to the same web site.
>
> Cmon you IIS gurus, there's gotta be a way to do this.....
>
> --Steve S.
>
>

[ Post a follow-up to this message ]

Thanks for the follow-up.

Yes, they are all under the same domain, but for various reasons we'd rather
not purchase a wildcard SSL.  I was wondering if there was some other way.
Kind of curious why we could do it in NT 4.0, but not in 2000.  Maybe it was
the nature of the certificates back then or something.

"Bernard" <qbernard@hotmail.com.discuss> wrote in message
news:%23khnN5OrEHA.4008@TK2MSFTNGP14.phx.gbl...
> Are all the websites under the same domain ?
> a.mydomain.com, b.mydomain.com and etc ?
> if yes, you can get a wildcard *.mydomain.com cert.
>
> if not, you will need individual site to bind those certs.
>
> --
> Regards,
> Bernard Cheah
> http://www.tryiis.com/
> http://support.microsoft.com/
> http://www.msmvps.com/bernard/
>
>
>
> "Steve S." <SteveS> wrote in message
> news:edLOy0JrEHA.896@TK2MSFTNGP12.phx.gbl... 
SSL[vbcol=seagreen] 
we[vbcol=seagreen] 
changes[vbcol=seagreen] 
>
>

[ Post a follow-up to this message ]

AFAIK, you need a website for each cert.

--
Regards,
Bernard Cheah
http://www.tryiis.com/
http://support.microsoft.com/
http://www.msmvps.com/bernard/



"Steve S." <SteveS> wrote in message
news:uD8jhZKsEHA.1308@tk2msftngp13.phx.gbl...
> Thanks for the follow-up.
>
> Yes, they are all under the same domain, but for various reasons we'd
rather
> not purchase a wildcard SSL.  I was wondering if there was some other way.
> Kind of curious why we could do it in NT 4.0, but not in 2000.  Maybe it
was
> the nature of the certificates back then or something.
>
> "Bernard" <qbernard@hotmail.com.discuss> wrote in message
> news:%23khnN5OrEHA.4008@TK2MSFTNGP14.phx.gbl... 
> SSL 
own[vbcol=seagreen] 
> we 
> changes 
>
>

[ Post a follow-up to this message ]