Skip Ribbon Commands
Skip to main content

Quick Launch

Todd Klindt's home page > Todd Klindt's SharePoint Admin Blog > Posts > Curious about Host Headers? Wonder No More!
November 26
Curious about Host Headers? Wonder No More!

Site collections that have the cursed /sites/ managed path in their URL has been the bane of SharePoint administrators for generations. In previous versions of SharePoint there were some ugly workarounds to deal with this, but they involved AAMs, lots of web applications, and ancient incantations. None of those things are good for your soul. SharePoint 2013 provides a much healthier option, the Host Named Site Collection, or HNSC. Unfortunately, getting your head wrapped around the complexity of HNSCs can be daunting, and many SharePoint administrators haven’t embraced them. Some out of confusion and some out of fear. There’s good news though, I recently published at SharePointProMag.com, The Case for Using SharePoint Host-Named Site Collections. In this article I explain what HNSCs are, and how to use them, and give you some PowerShell you can use to create some HNSCs of your own.

So please, read my Host Name Site Collection article and let me know what you think.

tk

ShortURL: http://www.toddklindt.com/HNSCArticle

Comments

HNSC and Managed Path

Hi Todd,

I like the idea of HNSC and interested in taking the leap. :-)

What are your thoughts on maintaining 1 web application with managed path and another for HNSC?

We need to maintain a web application policy that will allow access to our Intranet but deny all access for certain groups to all other sites.  Is it possible to do that with 1 web application and HNSC? 

Also, does the complexity of mapping IP addresses to each web application, http://technet.microsoft.com/en-us/library/cc424952(v=office.15).aspx?

Also, does HNSC pose issues with MySites due to the self service site creation?

Thanks!
 on 12/9/2014 4:59 PM

HNSC and Managed Path

Hi Todd,

I like the idea of HNSC and interested in taking the leap. :-)

What are your thoughts on maintaining 1 web application with managed path and another for HNSC?

We need to maintain a web application policy that will allow access to our Intranet but deny all access for certain groups to all other sites.  Is it possible to do that with 1 web application and HNSC? 

Also, does the complexity of mapping IP addresses to each web application, http://technet.microsoft.com/en-us/library/cc424952(v=office.15).aspx?

Also, does HNSC pose issues with MySites due to the self service site creation?

Thanks!
 on 12/10/2014 7:20 AM

Web App Limit

Your article says SharePoint 2013 is limited to 10 web apps per farm. TechNet shows the supported limit to be 20. Can you explain?

http://technet.microsoft.com/en-us/library/cc262787(v=office.15).aspx
 on 12/26/2014 1:40 PM

Add Comment

Items on this list require content approval. Your submission will not appear in public views until approved by someone with proper rights. More information on content approval.

Title


Body *


Today's date *

Select a date from the calendar.
Please enter today's date so I know you are a real person

Twitter


Want a message when I reply to your comment? Put your Twitter handle here.

Attachments

 

 Please Support my Sponsors