Should Root site have a site collection? Or is it better to create all Managed URL Explicit Paths with their own site collections? RRS feed

All replies

  • Hi,


    Per my knowledge, a web application without a site collection in the root managed path will return a 404 error when browsing to the root. You could always create another explicit managed path for multiple portal support in a Web application, i.e. http://webapp.fqdn.msft/HR. HR is a peer to '/'. Now, you can no longer have an HR sub-site in the root - you will get a security validation error because the URL space is already taken.


    For the detailed information about managed path, check out the following articles:







    Rock Wang

    Forum Support

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Regards, Rock Wang Microsoft Online Community Support
    Thursday, August 11, 2011 9:35 AM
  • Thanks Rock - this answers part of my question.  The second part of the question is what is best practice for designing an Intranet?  Is it better to have multiple Explicit Paths each with their own site collection and sub-sites or to use a Wild Card Path and create all the department sites under the one site collection?


    I guess it comes down to is it better/easier to manage an intranet with one site collection and multiple department subsites or manage multiple site collections?



    Thursday, August 11, 2011 3:14 PM