I also thought about a redirect, but then with an ASPX script:
- Create an extra Virtual Server to which I assign all host header names.
- Within this site I create a default aspx file in which I check the hostheader name and based on that redirect the user to the correct teamsite.
CU!
Yorick
Thomas,
Adding an HostHeader name to a site unfortunately does not work. The only thing your achieve is that the site can also be reached in the added name. What I would like is that a FQDN points to a subsite instead of a IIS virtual server. For example:
When I connect to the url...
I have one Sharepoint server which is hosting multiple teamsites. For example:
- http://server1/Teamsite1
- http://server1/Teamsite2
What I would like to do is give the user a nice FQDN to connect to the site. For example teamsite1.domain.com and teamsite2.domain.com. Does anyone have an idea...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.