Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Creating new sites in the Portal without the /sites directory

  Asked By: Sonny    Date: Apr 23    Category: Sharepoint    Views: 1081

Is it possible that someone can give some directin on how to configure
my portal so that new sites created from the PORTAL, SITES area are
NOT created under the /sites directory (example: NOT
http://Portal/sites/marketing)- INSTEAD http://Portal/marketing)? Is
there a way to do this? If there is, can someone point me in the right
direction as to how to do this?

Share: 

 

9 Answers Found

 
Answer #1    Answered By: Marty Mcdowell     Answered On: Apr 23

you are speaking of sites  aka WSS sites in the portal? normally you would
create an area.. which is done with "manage portal  site".

 
Answer #2    Answered By: Dakota Shaffer     Answered On: Apr 23

You cannot setup a new top-level site via the SPS user interface that is
only one level deep. You must always give  a named site in a managed
path. You can setup a wildcard included managed path in Central
Administration called marketing and create
http://Portal/marketing/newsite. While creating  a new child site at
http://Portal/marketing is programmatically possible, it is outside of
Portal Server's expectation to have Areas only, it is likely to have
unknown consequences, and will not be a native part of the navigation.

I wouldn't do it.

 
Answer #3    Answered By: Ted Gilmore     Answered On: Apr 23

When I was in Bill English’s class a few weeks ago,
Bill showed us a way to remove the default /sites
directory and in turn allow sites  to be created  by
users under the main portal. I don’t remember the
exact process though. Bill mentioned in class that
there are repercussions to doing this, “the Add Link
button in the Manage Sites to be Crawled list is also
removed” as a result. I also found this at the
Mindsharp blog site
(mindsharpblogs.com/.../687.aspx).
I would just like to find the exact process of doing
this. Can anyone help?

 
Answer #4    Answered By: Monte Cooley     Answered On: Apr 23

You can delete the sites  directory, but you'll lose some of the default
functionality of the sites directory. You can always create new sites
under the sites managed path, but in the absence of a sites directory,
I'm not sure how you would do this.

 
Answer #5    Answered By: Guadalupe Bullock     Answered On: Apr 23

Another alternative is you can change where sites  are created, so for
example you could make it http://portalname/teams/marketing.

That also has a few repercussions, but may better suit your needs. I
would have to go hunt down the documentation on how to do it, so reply
back if you are interested.

 
Answer #6    Answered By: Nathanial Mcclure     Answered On: Apr 23

I am particularly interested in how to remove all urls
in between the portal  site and the teamsite.
For example, I would like to have the ability to
create a team site under http://portalname/marketing,
without the /sites, /teams, or any other directory
between the portal name and the teamsite name. If you
have any insight and/or documentation on this, I
appreciate you posting it.

 
Answer #7    Answered By: Matt Prince     Answered On: Apr 23

"Sites" or "personal" are managed paths that are hard-coded into the product. Not only can you not remove them, you *won't want* to remove them. They provide a new virtual root at which many, many new site collections can be created.

 
Answer #8    Answered By: Brooks Bond     Answered On: Apr 23

Sorry, I was just throwing out another possible solution since you can't
remove that containing bucket for sites.

 
Answer #9    Answered By: Gregg Wilkinson     Answered On: Apr 23

WSS Central Admin --> Configure Virtual Server Settings --> virtserver --> Define Managed Paths --> Add a New Path.

When you create a site in the future, it will provide the new path in the drop-down.

Like portal.foo.bar/sales/admin and portal.foo.bar/CIO/admin

corporate wide sites  still use the /sites managed path and mysites use the /personal managed path

not sure if this would help, but that's how we do it!

 




Tagged: