P
Phillip Armitage
In a couple of weeks our firm will switch from our current e-mail system to
one using Outlook 2007 and Exchange Server 2007. The new system is up and
running and I have some people using it in production, although they have
access to the old system should something "funny" happen.
One of the issues that I'm battling with as I prepare to switch the office
over to the new system is how best to handle mailboxes that are assigned to
projects.
In our current system, I can create a mailbox specifically for a project
number. As people receive e-mails associated with a project they move the
message to the project mailbox, as opposed to just a project folder within
their own mailbox. The idea is that all e-mail associated with a given
project gets recorded in one place.
These projects are archtectural design/build ones, so many of the e-mails
contain large attachments. At present, I have one project folder, that does
NOT contain duplicate messages (they've been cleaned out), that has reached
7Gig in size and will probably double in size before it's complete. No,
archiving to CD/DVD is not an option (just had a 20 minute "discussion" with
the Partner in charge of the aforementioned project and having every message
from day one available at an instant's notice is REQUIRED.)
What are my options?
1) Create a PST file on a network drive, perhaps within the project folder,
then give shared access to it to the ten or twelve people working on the
project?
2) Use a public folder within my Exchange mail system?
3) Implement Sharepoint and store the mail in a folder assigned to the
project?
4) Create a new mail store on my Exchange mail server, then create a mailbox
for the project, storing the data within this new mail store.? Give people
working on the project shared access to this Exchange mailbox?
Any suggestions on how to set up a system to support large shared mailboxes
would be appreciated.
one using Outlook 2007 and Exchange Server 2007. The new system is up and
running and I have some people using it in production, although they have
access to the old system should something "funny" happen.
One of the issues that I'm battling with as I prepare to switch the office
over to the new system is how best to handle mailboxes that are assigned to
projects.
In our current system, I can create a mailbox specifically for a project
number. As people receive e-mails associated with a project they move the
message to the project mailbox, as opposed to just a project folder within
their own mailbox. The idea is that all e-mail associated with a given
project gets recorded in one place.
These projects are archtectural design/build ones, so many of the e-mails
contain large attachments. At present, I have one project folder, that does
NOT contain duplicate messages (they've been cleaned out), that has reached
7Gig in size and will probably double in size before it's complete. No,
archiving to CD/DVD is not an option (just had a 20 minute "discussion" with
the Partner in charge of the aforementioned project and having every message
from day one available at an instant's notice is REQUIRED.)
What are my options?
1) Create a PST file on a network drive, perhaps within the project folder,
then give shared access to it to the ten or twelve people working on the
project?
2) Use a public folder within my Exchange mail system?
3) Implement Sharepoint and store the mail in a folder assigned to the
project?
4) Create a new mail store on my Exchange mail server, then create a mailbox
for the project, storing the data within this new mail store.? Give people
working on the project shared access to this Exchange mailbox?
Any suggestions on how to set up a system to support large shared mailboxes
would be appreciated.