Re: Site Layout - Suggestions
From: Mike Morisoli (michael_at_removeme.vieon.net)
Date: 02/24/04
- Next message: Steven Collier [MVP]: "Re: SharePoint 2003 is slow"
- Previous message: Steven Collier [MVP]: "Re: SPS 2001 SP 2a"
- In reply to: Richard Cranswick: "Re: Site Layout - Suggestions"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 24 Feb 2004 12:52:26 -0800
The security is handled on a per site or per area level. I don't see how
creating addtional site would really help with security issues. It might
make backups a bit more granular.
Mike
"Richard Cranswick" <richard@nospam-richardcranswick.com> wrote in message
news:c132oa04gc@enews1.newsguy.com...
> Thanks for the response.
>
> The system is intended to be used:
>
> a) as a company wide portal.
> b) to provide basic DM facilities for each department - with task lists
and
> discussion boards for each client.
>
> The client wants the advanced search facilities procided by SPPS 2003.
>
> Would there be any advantage/disadvantage in creating a new virtual server
> with a portal for each department? I'm thinking that having a separate
> portal/virtual server for each department would allow me to better control
> the security and perform backups of individual department sites.
>
> "Mike Morisoli" <michael@removeme.vieon.net> wrote in message
> news:euwX71n9DHA.2640@TK2MSFTNGP10.phx.gbl...
> > Before you decide, take a look into Area's vs. Sites.
> >
> >
> >
> > The Portal Area's are true Sharepoint Portal Server (SPS) "things",
while
> > Sites are Windows Sharepoint Services (WSS) "things".
> >
> >
> >
> > I have found that I tend to keep the more corporate wide portal
> information
> > on SPS and the collaboration and team work in WSS.
> >
> >
> >
> > You really need to create some of both and see how related yet different
> > each technology is.
> >
> >
> >
> > My $0.02 worth, Mike
> >
> >
> >
> >
> >
> >
> > "Richard Cranswick" <richard@nospam-richardcranswick.com> wrote in
message
> > news:c10hrl02p7@enews3.newsguy.com...
> > > I am currently implementing a SharePoint Portal Server 2003 solution
for
> a
> > > client.
> > >
> > > The initial implmentation will be for 2 departments. However, 2 more
> > > departments will be migrated over from SPS 2003 at a later stage.
> > >
> > > Each department has specific clients.
> > >
> > > For each client they want a document library, a task list and a
> discussion
> > > group.
> > >
> > > I was thinking of defining an area under the main portal for the
> > departments
> > > and then a sub area for each client within a department.
> > >
> > > There would probably be between 500 and 1000 clients spread between
the
> > > departments.
> > >
> > > There would be between 50 and 100 users using the portal actively.
> > >
> > > This is a single server configuration, the hardware is a dual
processor
> > box
> > > with 4Gb RAM and hundreds of Gb of storage.
> > >
> > > Would this be an appropriate configuration or does anyone have any
> better
> > > suggestions?
> > >
> > > Any comments would be appreciated.
> > >
> > > Thank you.
> > >
> > >
> >
> >
>
>
- Next message: Steven Collier [MVP]: "Re: SharePoint 2003 is slow"
- Previous message: Steven Collier [MVP]: "Re: SPS 2001 SP 2a"
- In reply to: Richard Cranswick: "Re: Site Layout - Suggestions"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|