[2] Suggested Contacts
The bane of my life currently as they broke the corrupt mailto: address fix
they put in place for outlook 2007
Nick Turner
This electronic message contains information from CACI International Inc or
subsidiary companies, which may be confidential, proprietary,
privileged
What is the best practice or guideline when you create/organize
databases in your organization? How do you add/organize users into
different databases?
By location?
By their size of current mailbox?
By department?
By users' job title?
...
Thanks.
Henry Shih
System Administrator
No idea about best practice but we do it by department so in the event of a DR
we can restore the databases of the most important teams first.
Sent from my Windows Phone
-Original Message-
From: Shih, Henry
Sent: 14/02/2012 17:38
To: MS-Exchange Admin Issues
Subject: Exchange 2010
By job title/mailbox size. There seems to be a correlation between the two.
From: Shih, Henry [mailto:hms...@ci.livermore.ca.us]
Sent: Tuesday, February 14, 2012 11:30 AM
To: MS-Exchange Admin Issues
Subject: Exchange 2010 database
What is the best practice or guideline when you
By doing it by department you're ensuring that a whole department's email is
out of action should their database fail.
Better to scatter people randomly.
Or is it?
Cheers,
Phil
From: Tobie Fysh [mailto:tobie.f...@freebridge.org.uk]
Sent: 14 February 2012 19:03
To: MS-Exchange Admin Issues
My two cents... First, I think it depends on the organization!
I usually recommend, if most mailbox limits are going to be the same, going for
a balanced/random distribution based on the mailbox profile and planned users
per DB rather than another factor. And, if you have an entire department
We go by surname with appropriate splits for DB sizing. - that spreads users
pretty randomly for location, department and all that. Works well for us.
Blackberry
From: Steve Goodman [mailto:st...@stevieg.org]
Sent: Tuesday, February 14, 2012 04:49 PM
To: MS-Exchange Admin Issues
