Host Named Site Collections SharePoint

What is Host Named Site collections?

Host-named site collections are the best option if you want to create multiple root-level site collections within a web application. (Or Unique URL for each site collection)

* SharePoint supports both path-based & host-named site collections.
* The primary difference:

 All path-based site collections in a Web application share the same host name (DNS name), where as each host-named site collection in a Web application is assigned with a unique DNS name.

In other words:

Host-named site collections allow you to create many root-level host-named sites within a single Web application.
With path-based sites, you are limited to a single root-level site collection within a Web application


What are the advantage/dis-advantages:

Path-Named:

* These sites can be accessed from any zone that you configure.
* Alternate access mappings feature, which provides support for SSL, works with all path-based sites. * you are limited to a single root-level site collection within a Web application, But the managed paths option allows you to create top-level sites beneath the initial root-level site collection.

Host-Named:

They give you more control over URLs.
* Host-named site collections are only available through the default zone.
* The alternate access mappings feature does not work.
* You can't use both HTTP and HTTPS together.
* You can create up to 100,000 host-named site collections within a single IIS Web site

How to Create Host-Named site collection?

Well, Create a web application with out Host header(You can create using SharePoint Central Administration or with PowerShell New-SPWebApplication cmd-let) , and execute the PowerShell command, Of course, Host-named site collections can be only created by using the Windows PowerShell only:

 New-SPSite http://<URL-For-Site-Collection> -OwnerAlias Domain\username -HostHeaderWebApplication <Web-App-URL>

This creates a host-named site collection with the URL <URL-For-Site-Collection> in the SharePoint 2010 Web Application with the URL <Web-App-URL>.


To Change URL of the Host Named site collections, use: Stsadm -o RenameSite. E.g.

stsadm -o renamesite -oldurl "http://intranet.crescent.com/" -newurl "http://portal.crescent.com"
Don't forget to update IIS!

Add IIS Binding:

Don't forget to add IIS bindings! Otherwise, your host named site collections will not be accessible.
* Go to IIS, Pick the Web Applications which hosts the Host Named Site collection.
* Click on Bindings,  Add the Host header URLs of Host Named site collections.





Its also possible to add site bindings from PowerShell. Here is the script:
  
Import-Module WebAdministration
New-WebBinding -Name "<Web Site Name in IIS>" -Port 80 -Protocol http -HostHeader "prod.crescent.com"



Plan for host-named site collections

Comments

Post a Comment

Popular posts from this blog

"There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word." Office WebApp Error

Problem: When Opening a word document I get the following error when Office Web Apps tries to render the document " There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word. " Initial Hypothesis: Check the ULS logs on the Web Front End (SharePoint Server) as this doesn't tell me much.  I found the following issue in my UL S: WOPI (CheckFile) - Invalid Proof Signature for file SandPit Environment Setup.docx url: http://web-sp2013-uat.demo.dev/Docs/_vti_bin/wopi.ashx/files/6d0f38c0d5554c87a655558da9cedcad?access_token... Resolution: Run the following PS> Update-SPWOPIProofKey -ServerName "wca-uat.demo.dev" More Info: http://technet.microsoft.com/en-us/library/jj219460.aspx
Continue Read

"We’re sorry. We ran into a problem completing your request. Please try that again in few minutes." Excel Service SharePoint

Image
This article explains about Excel related issue in our SharePoint 2013 Environment. Whenever user tries to open excel files uploaded in document library, it launches browser to open the file and then displays below error- " We’re sorry. We ran into a problem completing your request. Please try that again in few minutes." Also see below screenshot- As part of issue analysis, following checks were performed- 1.) Check if Excel Services is running. ( This was running in our case. ) Open Central Administration -> System Settings -> Manage Services on Server -> Excel Calculation Service -> Started 2.) Check if Excel Service Application is associated to Web Application in question. ( This was configured in our case. ) Open Central Administration -> Application Management -> Manage Web Applications -> Select Web Application -> Select Configure Service Associations 3.) Check if Trusted File Location is configured for Excel Service...
Continue Read

Deployment error "The web.config is invalid on this IIS Web Site"

I've developed a webpart that deploys and works properly in my DEV environment. When I attempt to deploy to PROD I get the following error: SOMESERVER : http://acme.com/ : SharePoint - 41981 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\41981\web.config. SOMESERVER : http://acme.com/ : SharePoint - 41981 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\41981\web.config. SOMESERVER1 : http://acme.com/ : SharePoint - 23994 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\23994\web.config. None of these virtual directories exist. Any ideas how to resolve? Solution : In Central Administration-> Operation-> Services on Server, please stop the Windows SharePoint Services Web Application service , SharePoint will remove the sites in IIS. And then start the Windows SharePoint Services Web Application service agai...
Continue Read