Host named site collections are the preferred way to configure site collections in SharePoint 2013, especially for large farms. You'll learn how to transition from path based to host named site collections, how to restore host named site collections between farms, and when you might not want to use host named site collections. I'll also share some tips and tricks from recent experience with migrating from SharePoint 2010 to show you how host named site collections can help you to avoid some common upgrade issues.

1. 1 SPSTC
@SPSTC #SPSTC
SharePoint Saturday
Twin Cities
True Confessions of Host Named Site Collections in SharePoint 2013

2. Thank you #SPSTC
sponsors!

3. 3 SPSTC
@SPSTC #SPSTC
 SAS



 www.linkedin.com/pub/bonnie-springer/7/911/224/

4. 4 SPSTC
@SPSTC #SPSTC







5. 5 SPSTC
@SPSTC #SPSTC
• Can this farm be saved?
• Don’t Do What We Did
• Why SharePoint? Why?
• Descent into SharePoint Madness
• I Love SharePoint More Than SharePoint Loves Me

6. 6 SPSTC
@SPSTC #SPSTC

7. 7 SPSTC
@SPSTC #SPSTC








8. 8 SPSTC
@SPSTC #SPSTC







9. 9 SPSTC
@SPSTC #SPSTC

10. 10 SPSTC
@SPSTC #SPSTC




11. 11 SPSTC
@SPSTC #SPSTC
 “Supported” limit up to 99 web apps per farm/SSP
 10 app
pools per server
 Supported limit up to 20 web apps per farm; 10 app
pools per server


12. 12 SPSTC
@SPSTC #SPSTC





13. 13 SPSTC
@SPSTC #SPSTC





14. 14 SPSTC
@SPSTC #SPSTC

15. 15 SPSTC
@SPSTC #SPSTC
On Oct 5, 2013, at 9:26 PM, "Bonnie Springer" <Bonnie.Springer@sas.com> wrote:
I’ve been trying since 2pm to create a new web application on the SP2013 production farm. The first web app I
tried to create (site1) took about 2 hours … well, it may have taken longer had it not resulted in an error
message about an object being referenced that already existed. When I looked at IIS and the virtual directory
locations, site1 appeared to be partially provisioned – so this one is going to have to be deleted and recreated.
Sites were serving at this time. I decided to try to create another new web app. I first did an iisreset and
restarted the timer service and tracing service on each wfe server. I then kicked off the web app creation for
site2 at 6:33pm. It’s still running as of 8:55pm. I tested site access early on and sites were rendering. However,
around 7:48pm, I couldn’t get any site to serve – not even existing site3 when targeting a specific wfe server. At
8:36pm, site3 displayed this error in the browser:
The server is busy now. Try again later
I finally got a site to render at 8:54 which was around the time I started getting a response from
site3.sas.com/pages/default.aspx. As of 8:57, I got another site to render so sites seem to be coming back up.
I checked site2 and it appears to be nearing the end of the provisioning process. I see that the virtual directories
were created between 8:44 – 8:50pm (depending on the wfe server). The PowerShell command that I kicked off
at 6:33 is still running (that is, it hasn’t returned to the command prompt with a message that the new web app
has been created). I think we’re nearing the end of this drama though. All of the timer jobs (there were dozens
that had piled up in the past 2 hours have now executed. More sites that I’ve tested are now rendering. CPU is
settling down to normal ranges now.
Ah … as of 9:05, the new-spwebapplication command has finished running on sp2013wfe04. I think we’re “back
to normal” now … over 2.5 hours later.
Here is my concern … I’ve got a number of web apps to create to prepare for upcoming migrations. This
evening’s exercise for the site2 creation was not fun and, at various points in the process, I was concerned
that the farm may not come back. Each new web app that we create seems to pose greater and greater risk to
the farm. At the risk of not being able to meet the migration schedule for the upcoming week, I’m going to
stop creating web apps because I’m concerned about the stability and sustainability of the farm in its current
state. I recommend that we open a support case with Microsoft.

16. 16 SPSTC
@SPSTC #SPSTC

17. 17 SPSTC
@SPSTC #SPSTC

18. 18 SPSTC
@SPSTC #SPSTC

19. 19 SPSTC
@SPSTC #SPSTC










20. 20 SPSTC
@SPSTC #SPSTC










21. 21 SPSTC
@SPSTC #SPSTC










22. 22 SPSTC
@SPSTC #SPSTC








23. 23 SPSTC
@SPSTC #SPSTC






HostHeaderWebApplication

24. 24 SPSTC
@SPSTC #SPSTC


 http://acmeold.contoso.com


 http://acmeold.contoso.com

25. 25 SPSTC
@SPSTC #SPSTC
DEMO 1

26. 26 SPSTC
@SPSTC #SPSTC





 HostHeader




27. 27 SPSTC
@SPSTC #SPSTC


HostHeaderWebApplication


 http://acmeold.contoso.com


 http://acmeold.contoso.com

28. 28 SPSTC
@SPSTC #SPSTC
DEMO 2

29. 29 SPSTC
@SPSTC #SPSTC









30. 30 SPSTC
@SPSTC #SPSTC

31. 31 SPSTC
@SPSTC #SPSTC





32. 32 SPSTC
@SPSTC #SPSTC









33. 33 SPSTC
@SPSTC #SPSTC
 What Every SharePoint Admin Needs to Know About Host Named Site Collections
 Guide to SharePoint 2013 Host Name Site Collections
 Script for Migrating Host Named Site Collections
 TechNet: Host-named site collection architecture and deployment (SharePoint 2013)

34. 34 SPSTC
@SPSTC #SPSTC


https://guidebook.com/guide/27567/
