>>>>1. Set mailbox limits. Let users manage their mailboxxen within those
>>>>limits however they choose.
>>>Does anyone else see this strategy as a problem waiting to happen when
>>>Exchange 2000 and the WebStore is used as a place to store everything?
>>Yep. Users will use it as the ultimate dumping ground and demand
>>'unlimited' storage.... fortunately things appear to be a bit more
>>scalable (however I imagine demand will outstrip reasonable
>>scalability in a relatively short amount of time for most of us).
>How will that affect the storage already allocated for file servers?
>Will the data there be moved to the WebStore? Will it bemore useful if
>it's stored in a public folder than a home directory? How about a
I don't know, that's a very good question. Since Exchange 2000 will
support multiple private information stores, will it be possible to
use one box instead of 10? And if so, for how long?
I know that in our case I don't think we're ready to commit to storing
the types and amounts of data our users create in that store. Other
pending complimentary technologies may make that somewhat more
palatable/ feasible, but I'm not sure to what extent one could scale
>>>>2. Buy more servers until the cost of servers outstrips the value of
>>>>not managing mailbox resources.
>>>Today that's true. Do you see a lot of that information _becoming_
>>>valuable in the future?
>>Hmm... the 2 3MB AVI files I found in one of my users mailboxes today
>>will probably be just as useless 18 months from now....
>Will you continue to look at Exchange as only an e-mail system? This
>isn't only directed at you, Chris. I'm curious if other people see
>potential in what Exchange will be capable of doing.
Oh, I know, I'm hoping someone else will jump in with some ideas. My
experience is limited by, my experience. I'd like to see what others
are thinking as well.
Quote:>That AVI file isn't really what I was after. Most of us clamber for
>users to dump old mail, but will that mail (the useful stuff, not the
>stuff from Mom) be useful if it's given a place in the company and
>indexed so others can read and reference it? Places like town and
>county governments that have a requirement that all communications are
>public records, stuff like that.
I see your point, and in our situation we have a separate document
management system which is supposed to house and index that type of
information... never even opened the client interface for it. Watched
someone else use it once and cringed in horror. Integrating that with
an interface users access every day has some serious merit.
Quote:>That's the point. is all the stuff in the mailbox worthless? What
>about things like policies and procedures, engineering specs, etc.
>that are relegated to PST's rather than public folders and then just
>sit there while someone else reinvents the same stuff?
Well, the big push now is to put many of those object on an
intranet... in which case the webstore seems to be the logical
progression. However, it's not (yet) a robust enough document
management solution (IMHO) to be the Alpha and Omega document
Chris Scharff ! One man with courage
Exchange Consultant ! makes a majority.
BV Solutions Group ! - Andrew Jackson
ROT13 required for SMTP Address
Exchange FAQ: http://www.swinc.com/resource/exch_smtp.htm