First, go and read Kirk Evans’ post: What Every SharePoint Admin Needs to Know About Host Named Site Collections.
Now see what has changed with SharePoint 2013.
Limitations in the previous version:
- You could set host name per web application, but this was limited to about 20 web applications. (see also)
- You could set host name per host-named site collection, but this was limited to one URL for the Default Zone. For extended web applications using other zones with different authentication settings or policies, you weren’t able to make use of any of that in host named site collections.
New with SharePoint 2013:
- You can add multiple URLs to host-named site collections. URL will be mapped to one of the 5 zones which are the same as for a web applications. But you can add multiple URLs to one zone.
- You can now leverage the zone settings of a web application also in host-named site collections. (This is useful for different public URLs when working with HTTPS / SSL.)
- Multitenant environments can now use a lot of additional URLs with no serious limitations left.
So with SharePoint 2013 this now is ideal for hosters. It is Microsoft’s new cloud first approach working for you. I guess they needed it for SharePoint Online.
Let me show you how to make use of this new functionality:
Step 1: Create a host-name site collection via PowerShell
New-SPSite "http://www.own-url.com" -HostHeaderWebApplication "http://existingwebapp" -Name "Portal" -Description "Customer portal" -Own erAlias "preview\administrator" -language 1033 -Template "STS#0"
Step 2: Add additional URLs
Set-SPSiteUrl -Identity http://www.own-url.com -Url https://another-ssl-url.com
Control the result:
Get-SPSiteUrl -Identity http://www.own-url.com
Want to learn more?
Read this Waldek Mastykarz’ article: SPSiteUrl’s in SharePoint 2013