Here is a summary of the steps to create a new Host Named Site Collection (HNSC)
- Create a new Web Application – default Web App on port 80 or use an existing Web Application. I chose http://HNSCWebApp as my Web Application – the default Web App listening on port 80 on all my Web servers in the farm.
- Note – HNSC can be created on a non default Web Application but you’ll need to add bindings in IIS for your HNSC as the Web Application isn’t listening to all port 80 requests and would need to know about the HNSC it hosts. Thats why a lot of blogs usually specify HNSCs on default web apps, because adding IIS bindings can get messy. But its worth a note in this post.
- Decide what your new Site Collection unique URL should be. I chose http://test and http://teamsite to run off a Team Site template.
- Run the following in the SharePoint Management Shell:
$w = Get-SPWebApplication http://hnscwebapp New-SPSite http://test -OwnerAlias "testdomain\testowner" -HostHeaderWebApplication $w -Name "test" -Template "STS#0" New-SPSite http://teamsite -OwnerAlias "testdomain\testowner" -HostHeaderWebApplication $w -Name "teamsite" -Template "STS#0"
- Ensure that you create a dummy ‘root’ site collection with a site template http://hnscwebapp. Its required for Search & Send to Other location.
- Configure kerberos for your Host Name site collection.
- Create a Managed Path if required (New-SPManagedPath)
- You can create new zones for HNSC so that it can be accessible via a different name.
My recommended links for you to read:
Wicto Wilen – Clearing up the confusion with Host Named site collections and Path Based site collections
Marko Rosberg – For more information on creating Host Named Site Collections and App host configuration:
Kirk Evans – Host Named Sited Collection in SharePoint 2010 (applies to SharePoint 2013):
Technet – Host-named site collection architecture and deployment (SharePoint 2013):
Brian Farnhill – Multiple zones for host named site collections in SP2013