I’m currently going through the TrainSignal Course “SharePoint 2013 Administration” Course by Bill Kulterman. An excellent beginning course in SharePoint Administration.
I’m a developer that beginning to dabble in Administration. I’ve had to setup a few Dev Machines for SP2013.
My specific question concerns Managed Paths and Site Creation. In the course the Main Site is created on it’s own Path: An Explicit Path but not the Root “/” Path.
In my experience, the main sites are created on the root managed path–thus the site collection and main site have the same URL.
In this case “Main” would be the Root Site Collection? Correct? Also another site should not be created at the Managed Path root? Correct? Even though it is available? This would be confusing.
Normally on the machines I’ve used, someone types in the site collection and then it resolves to the site collection plus default.aspx or “Pages/default.aspx” for the root site.
In the case I mentioned, I believe you would need specifically to add the site “Main” to the Site Collection Url? Then it would resolve correct?
thanks,
Stephan Onisick
Let me add a little more clarity. I tried this out on my test system.
Under http://intranet.contoso.com I added a managed path for main and created a site collection with the path http://intranet.contoso.com/main. So I now have two site collections.
Basically I think http://intranet.contoso.com is the root web of the first and http://intranet.contoso.com/main is the root web of the second.
If I run the powershell command:
Get-SPWebapplication http://intranet.contoso.com | get-spsite
I see two site collections which is what I expect.
I guess what threw me was that I just hadn’t seen other Explicit Inclusion Path besides root used. Â So I think you can add all the Explicit Managed Paths that you want.
