Yeah I'm with Geoffrey on this---not seeing the need in the need to involve an Exchange server at all if you are "working with" a PST. Just mount it using Outlook and be done with it----right? The PST would reside on a network share (not recommended) or on your local hard drive, and doesn't count toward any mailbox size limits.
On Wed, May 28, 2014 at 12:06 PM, Orlebeck, Geoffrey < [email protected]> wrote: > What do you need to do with the PST file? If it's just mounting/browsing > the PST, you can create a second Outlook profile on a local workstation and > open the PST file from there without any need for Exchange. If you must > perform an action that requires the EMC/EMS/Mgmt tools from Exchange > itself, then I'll defer to others on how best to handle that. > > > > -Geoff > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Heaton, Joseph@Wildlife > *Sent:* Wednesday, May 28, 2014 7:48 AM > *To:* [email protected] > *Subject:* [Exchange] Setting up a test server > > > > Our organization has moved into a managed e-mail system. I have a need to > be able to work with a rather large PST, which is larger than our allowed > mailbox size. My thought is to throw up an Exchange server internally, so > I won't have to worry about the size, and I won't have to create a much > more expensive mailbox online. > > > > Do I still need all 3 roles to do this, or can I do without the HT? > > > > I'm going to be doing this in 2010, by the way, since that's what we had, > and that's what our online service is using. > > > > Thanks, > > > > Joe Heaton > Confidentiality Notice: This is a transmission from Community Hospital of > the Monterey Peninsula. This message and any attached documents may be > confidential and contain information protected by state and federal medical > privacy statutes. They are intended only for the use of the addressee. If > you are not the intended recipient, any disclosure, copying, or > distribution of this information is strictly prohibited. If you received > this transmission in error, please accept our apologies and notify the > sender. Thank you. >
