Re: Justifying the more complex use of WSS to store shared documents
From: news.gci.net (brian_sarka_at_labor.state.ak.us)
Date: 11/19/04
- Next message: Jéjé: "how to create an hidden webpart?"
- Previous message: Kit Kai: "Re: MICROSOFT! Help Me!"
- In reply to: Jeff Webb: "Re: Justifying the more complex use of WSS to store shared documents"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 18 Nov 2004 18:55:31 -0900
A good place to start:
In many ways, this is the standard problem of solving problems they didn't
know they had,
but in many cases the supposed advantage is already provided by some other
solution-
Versioning? Provided by Microsoft Office.
Role-based permissions? Thats what security groups and NTFS permissions are
for.
Alerts? Send me an email when your done with your changes. (although - I
think this *will* grab their attention)
Views? Whazzat - is it worth paying the administrator to setup and then to
teach everyone what it is?
Common Interface? Looking at one shared folder is pretty much like looking
at any other shared folder.
Web access? Web browsers are evil. How is browsing to a file in IE
different from browsing to it in WE? How is any of this better than the
shared file solution of STS? Why purchase SQL Server just to store files?
MSDE handles the configuration requirements of STS, why buy SQL Server to
support WSS's need to store 10 GB of documents when those documents are
already on a shared folder?
"Jeff Webb" <jwebb5@cfl.rr.com> wrote in message
news:OHIC0$BzEHA.1596@TK2MSFTNGP10.phx.gbl...
> Versioning, role-based permissions, alerts, views, common interface,
simple
> interface, web access if needed, search...
>
> It's kind of like asking why we started walking upright. It was cool, but
> did it really save us any money?
>
> "news.gci.net" <brian_sarka@labor.state.ak.us> wrote in message
> news:10pkhil54pj2aa1@corp.supernews.com...
> >I originally posted this in .sharepoint.teamservices group, it really
> > belongs here:
> >
> > I find myself in the position of justifying the use of WSS and storing
> > documents through our WSS intranet rather than simply as files on
> > shared directories.
> >
> > Now, I love WSS and the whole integration with .net and SQL server
> > thing, but I am hard pressed to explain how this is the better
> > solution, especially when a simple intranet can be developed with
> > notepad and files in shared folders w/NTFS permissions for *much* less
> > cost.
> >
> > I'm not trolling here, I really need to generate some info for a
> > report to justify the expense and time to upgrade our intranet.
> > Other than being "really cool" for us technoids, what are the solid,
> > substantial benefits?
> >
> > I am likely to post counter-arguments matching those I will have to
> > entertain as I justify the project.
> > I invite responses to my email below, also.
> >
> > Brian Sarka
> > brian_sarka::at::labor.state.ak.us
> > MCSE, SCJP, MCIWD, A+
> > Information Technology Instructor
> > Alaska Vocational Technical Center
> > avtec.alaska.edu
> >
> >
>
>
- Next message: Jéjé: "how to create an hidden webpart?"
- Previous message: Kit Kai: "Re: MICROSOFT! Help Me!"
- In reply to: Jeff Webb: "Re: Justifying the more complex use of WSS to store shared documents"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
