Yes, it has been around since SP2010, but I haven’t given it much thought until some recent 2013 projects. Even though it’s the “preferred” means of deploying site collections now, I’m trying to get a quick grasp on what the common practice is on this capability today and why, 2010 or 2013?
Ease of management, resource constraints, logical requirements, what governs you decision making in deploying one over the other, host-named vs. path-based site collections? I may just be bit behind the ball on this one so please allow me to play catch up 🙂
Thanks in advance
-Atiim
(Visited 76 times, 1 visits today)
The key factors in using host-named is scalability and performance. You do lose self-service site creation functionality, however.
(Visited 1 times, 1 visits today)
