Re: How do you regulate your Exchange domain?
From: Bob Christian (BobChristian_at_removethis.gmail.com)
Date: 09/25/04
- Next message: Victor Ivanidze: "Re: second mailbox or public folder"
- Previous message: Brendon: "Re: Exchange 5.5 Distribution List --> bcc: question"
- In reply to: Andrew: "How do you regulate your Exchange domain?"
- Next in thread: Mark Arnold [MVP]: "Re: How do you regulate your Exchange domain?"
- Reply: Mark Arnold [MVP]: "Re: How do you regulate your Exchange domain?"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 25 Sep 2004 12:02:49 -0400
I like what Mark says. Technically, he is correct in what to do first.
However, politically, I disagree on what to do first.
You don't want to come in and make enemies. Trust me on that.
The first thing that I would do is discuss, with your management, the option
of cutting down SPAM first. The users will be happy about that. Once the
user environment is happy...
Propose to them two options (note: I don't know the specifics of your
organization, so this is generic):
Option 1) Propose a purchase of a new server with plenty of disk. Note
that a rule of thumb that I use is ~150 people per spindle, dependent upon
utilization...more folks if I am using Outlook 2003 Cached Exchange Mode. I
generally use Windows 2000/2003 standard server and Exchange Server
2000/2003 Enterprise edition. Clustered environments are different.
Option 2) In lieu of this, propose moving some of the largest user's
information to .pst files and implement quotas. Remind management that the
loss of the user's local system could result in the loss of the .pst file if
it is stored on the system. Note that the upper limit of .pst files may be
1.85GB of 2.00GB on older versions (pre-2003) of Outlook.
That way you are leaving it up to management to make the decision on what to
do and you do not seem like the bad guy...and you are providing risk
mitigation information. They will talk to the managers and users, most
likely.
Stories:
I had a very large client in Georgia that would rather purchase more SAN
space than implement quotas for their users. We got a few new servers and a
nice beefy SAN.
On the flipside, I had a client in Virginia that did not want to purchase a
new server or software. They opted to implement quotas and their
management sent an e-mail regarding this. Obviously, there were exceptions
to the rule.
Either way, it was management's decision and I did not seem like the bad
guy.
Bob
"Andrew" <Andrew@discussions.microsoft.com> wrote in message
news:8027F27D-6F6C-4331-A608-71FBA3F5058C@microsoft.com...
> I've just started at this new company where their entire exchange is a
mess.
> There is spam every. Users have over 2 gig inboxes, no one deletes
anything.
> There are constant complaints. I figure as my first act here would be to
> setup a project to create some level of organization/mangement of the
> exchange server.
>
> i was wondering what type of exchange policies have you implemented at
your
> organization? (ex: limit the size of inboxes, attachments, etc)
- Next message: Victor Ivanidze: "Re: second mailbox or public folder"
- Previous message: Brendon: "Re: Exchange 5.5 Distribution List --> bcc: question"
- In reply to: Andrew: "How do you regulate your Exchange domain?"
- Next in thread: Mark Arnold [MVP]: "Re: How do you regulate your Exchange domain?"
- Reply: Mark Arnold [MVP]: "Re: How do you regulate your Exchange domain?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
