Re: why shouldyou not rely on public folders??
- From: "Mark Arnold [MVP]" <mark@xxxxxxxx>
- Date: Thu, 05 May 2005 09:09:26 +0100
On Wed, 4 May 2005 13:55:46 -0700, Kahlan
<Kahlan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>Hello
>I always here that it is better to put documents on file servers vs. public
>folders but I can not seem to track down why? security, performance,
>whyyyy....
>Thanks
>Kahlan
Using public folders as a file server can increase accessibility to
the information if you have OWA but not a VPN etc. But you will
inevitably get a performance hit from your server as you load it up.
Also the permissions model is nowhere near as flexible. It's also more
fiddly to save and deposit versioned files there.
Also the future of public folders is shrouded in mist. Conventional
wisdom is that if you do need to web enable file share type
information then SharePoint is your solution. If you don't want
SharePoint then FileWay (google for it) is a good application.
If you don't need to web enable any of it then put it on a file share.
.
- References:
- why shouldyou not rely on public folders??
- From: Kahlan
- why shouldyou not rely on public folders??
- Prev by Date: Re: why does exchange go outbound for unknown internal mail?
- Next by Date: Re: why does exchange go outbound for unknown internal mail?
- Previous by thread: why shouldyou not rely on public folders??
- Next by thread: Blocking telnet connections
- Index(es):
Relevant Pages
|