Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Path for site collection

2 views
Skip to first unread message

John S

unread,
Jul 6, 2009, 6:59:01 AM7/6/09
to
Is there any way to create site collections directly below the portal?

When you go to create a site collection in the Central Administration, you
have to choose a managed path to go in front of the site collection name. Is
there any way of being able to create a site collection directly off of the
root folder(/). I.e. could I create a collection called Sections so that I
could then have subsites coming off of http://Portal/Sections/Section1 etc.

I know I could create Sections as a Managed path but we want it to be a
proper area where people can go to to create additional sub sites etc.

Steven Cheng

unread,
Jul 7, 2009, 5:59:33 AM7/7/09
to
Hi Js,

So far the available path for SiteCollection in WSS web application is
defined by "managed path". And when you add a new managed path, you can
choose to mapping type:

** wildcard mapping

** explicit inclusion mapping

#Define managed paths (Windows SharePoint Services)
http://technet.microsoft.com/en-us/library/cc288905.aspx

For your scenario, I think you can use the "Explicit Inclusion" one. You
can create a managed path with the following value

"/Sections"

Then, "http://servername/Sections" will be the Site collection path(and
root site path), all the sub sites can be created at:

"http://servername/Sections/[sub site name]"

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msd...@microsoft.com.


--------------------
From: =?Utf-8?B?Sm9obiBT?= <js...@newsgroup.nospam>
Subject: Path for site collection
Date: Mon, 6 Jul 2009 03:59:01 -0700

John S

unread,
Jul 7, 2009, 7:07:01 AM7/7/09
to

Sorry that doesn't seem to work.

I created a managed path called sections as Explicit Inclusion as suggested.

If I try to navigate to http://server/sections/ I get a 404 error so at that
point nothing exists. It is not therefore a site collection. If I try to
create a site collection I can create one following that path e.g.
http://sections/sections from which I can then create sub sites etc. That is
not really any different from using the existing path called sites.

I still can't see a way of creating a situation where a user can navigate to
http://server/sections/default.aspx or similar for obtaining details of the
sections that exist and then creating sites with urls like
http://server/sections/section1 or http://server/sections/sectionB etc.

Steven Cheng

unread,
Jul 8, 2009, 2:14:48 AM7/8/09
to
Thanks for your reply Js,

After you add the http://server/sections/ as a manged path, you certainly
need to create a site collection at that path. Otherwise, WSS runtime will
not monitoring requests targeting that address. As WSS only cares about
site collection(only a managed path is not enough).

Also, as for the concept of "Site Collection", whenever you created a site
collection, WSS automatially create a root site(SpWeb) at the site
collection path. That's why when you navigate to the site collection path,
you will see the site default page(that is the root site of the site
collection). You cannot create a site collection with nothing(a root site
is always created).

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msd...@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.

--------------------
Thread-Topic: Path for site collection
thread-index: Acn+8w1yKCPH8ksaQR2exkicrH835A==
X-WBNR-Posting-Host: 195.188.248.226
From: =?Utf-8?B?Sm9obiBT?= <js...@newsgroup.nospam>
References: <B354EE30-E7B8-4309...@microsoft.com>
<Y#SXqmu$JHA....@TK2MSFTNGHUB02.phx.gbl>
Subject: RE: Path for site collection
Date: Tue, 7 Jul 2009 04:07:01 -0700

John S

unread,
Jul 8, 2009, 4:08:01 AM7/8/09
to

Sorry, I'm not sure I understand.

Are you saying that I should be able to create a site collection called
http://server/sections/ that would have a home page such as
http://server/sections/default.aspx? or does it have to be below that and
have a URL like http://server/sections/site_collection/ ?

Steven Cheng

unread,
Jul 9, 2009, 3:46:37 AM7/9/09
to
Hi Js,

Yes, you should be able to create the site collection at the following
address(after you've added /sections as managed path):

http://server/sections

And this is also what I did on my test environment.

The complete steps are as below:

**"http://server:port" is the web application address

**by default, we can only create site collection at the following two
places:

1) web application root --- http://server:port/
2) under predefined managed path(wildcard mapping) ----
http://server:port/sites/[site collection name]

** Then, we add a new managed path "sections", its type is "Explicit
inclusion"

** Finally, we can directly created a site collection at
"http://server:port/sections", and you can visit its root web at
http://server:port/sections/default.aspx

This is what I get on my MOSS test machine.

Btw, when you define a managed path, make sure you have choosed the correct
"Web Application". If you define a managed path under Web Application A,
then you will not be able to use that managed path (to create site
collection) under web application B.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msd...@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.

--------------------

John S

unread,
Jul 9, 2009, 5:34:04 AM7/9/09
to

I just tried it again and it worked fine.

I have no idea what I was doing previously to make it go wrong.

Sorry to have taken up your time and thanks very much for the help.

John S

Steven Cheng

unread,
Jul 9, 2009, 10:43:28 PM7/9/09
to
Thanks for your reply John,

I'm glad that it works for you.

Have a good day!

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msd...@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.

--------------------


Subject: RE: Path for site collection

Date: Thu, 9 Jul 2009 02:34:04 -0700

0 new messages