Re: Best practice for PST files?
- From: "John" <jdean@xxxxxxxx>
- Date: Fri, 7 Jul 2006 22:02:32 -0500
Look people, any question asked can raise a lot of comments. I didn't say
"what options are there for mail servers?" Most of my clients run exchange,
and I've been administrating exchange since it first came out, so yes, I'm
aware of all the benefits of Exchange vs. POP and IMAP servers.
But when you have a company that has just two people, a lawyer and his
secretary, they DO NOT spend money on things like Exchange. Those are the
types of clients on this particular terminal server. Tiny places that don't
invest in the technology because they barely use it. Most of them are on it
not for the simplicity of having a terminal server and the benefits it gives,
but because it gets backed up every night, unlike their local machines, so
they'd rather pay a monthly fee for it's usage knowing they're getting backed
up at the same time. These are places that don't use calendaring, etc.. All
they do is send email and receive email.
So please, we can stop the "I can't believe someone uses POP" because believe
it, there are a ton of businesses out there who simply can't justify the cost
of exchange, or if they could justify it, are too cheap to bother.
So let's end the thread of how horrible POP is.
On the "Thank you" side, though, I appreciate having pointed out to me that
Microsoft doesn't support PST's over a network - that answers my question
since if they don't support it, there's generally a reason why. Easy enough
to leave the PST's on the server's drive instead of the network share.
John
On 7/7/2006 9:16:59 PM, Patrick Rouse wrote:
Jeff took the words right out of my mouth. I can't believe people use PST
storage and POP mailboxes. One word, "Exchange". Before you exclaim, it's
too expensive fo my client... consider these:
1. Centralized information store containing everyone's mailboxes will
reduced the overall storage requirement due to Exchange's Single Instance
Storage, i.e. 5MB PPT file sent to 20 people using PST storage consumes 100MB
of network storage that needs to be backed-up. This same email in the
Exchange Information Store uses about 5MB, because it's only stored once, and
referenced by each mailbox.
2. Simplified backup and restore. Since the mailboxes are centralized in
one database, backup is a snap, and restore is almost never needed due to the
following features of Outlook & Exchange:
a. Deleted Item Recovery allows users to undelete items from any folder
in outlook (when enabled on the mailbox store), going back as many days as
you configure (30-90 days is pretty standard).
b. Deleted Mailbox Retention allow you to reconnect a deleted mailbox to a
new user account.
c. Exchange 2003 has a recovery storage group which allows you to mount a
copy of your information store for the purposes of exporting items that need
to be restored, without having to bring a recovery server online.
3. Reduction in bandwidth usage. Since users maiulboxes are on one SMTP
Server, emails sent to a bunch of users are delivered once, instead of being
downloaded individually by each user. If you get a 5MB PPT emailed to 20
people in your company, you consume only 5MB of bandwidth as the message is
delivered in one transcation, whereas with POP & PST you'd consume 100MB of
bandwidth as each user downloads the message when they open Outlook. This is
a very big deal.
4. Storing PST on a network drive is NOT supported by Microsoft.
5. If you own Exchange Server and Software Assurance, you always have
access to the latest version of Outlook, as this is part of the Exchange
License.
6. Centralized Virus Scanning. Scanning for viruses after the email has
arrived in the users mailbox is just the wrong way to prevent an outbreak.
Exchange supports VSAPI scanning, which scans the SMTP message for viruses
before the item is placed in user's mailboxs, allowing your to delete
infected attachments or file types you want to block without users ever
seeing them.
7. Ability to access your mailbox from multiple computers simulaneously, or
remotely, whereas PST is a single user file, i.e. if you have outlook open on
your desktop, you can't access it from another PC and you can't allow another
staff member to access any part of your mailbox while you're in it, i.e.
sharing contacts, calendars....
I could probably go on typing for another hour.....
PST, is primary storage for home users, not for businesses.
--
John
.
- References:
- Best practice for PST files?
- From: John
- Re: Best practice for PST files?
- From: Jeff Pitsch
- Re: Best practice for PST files?
- From: John
- Re: Best practice for PST files?
- From: Patrick Rouse
- Best practice for PST files?
- Prev by Date: Re: Best practice for PST files?
- Next by Date: Re: terminal server on VMware
- Previous by thread: Re: Best practice for PST files?
- Next by thread: Re: Screen resolution
- Index(es):
Relevant Pages
|
