It's been quite a while since I've looked at that, but if I recall, you would do alternate access within WSS. It should create the site in IIS. Then go into IIS and create the cert req and later import the cert.
Sharepoint gets unhappy when IIS changes are made directly in IIS. It's a control freak :) On Fri, Sep 10, 2010 at 4:03 PM, <[email protected]> wrote: > I have a client with Sharepoint Services 3, running an internal site on > port 8043. The site internally is name sp.domain.com which is hosted > locally on their server as a cname. To access their site internally you > would open http://sp.domain.com:8043 > > > > They want to make this site external. Once they install the SSL cert for > the external name they want to use, is it as simple as adding it to the > alternate access name list as https://sp.domain.com and making sure in IIS > the host header is pointing to the IIS site that is running that site. Its > not in the default web site. > > > > Thx > > > > I have done this a few times before, but all of them have been in the > default web site. > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
