Solved

microsoft exchange 2010

Posted on 2016-11-10
3
58 Views
Last Modified: 2016-11-15
Dear Experts,

We current host Microsoft Exchange 2010. We are thinking of upgrading it to Exchange 2016 (or replacing if no upgrade path).
We have about 25 users and use the group email as well as the calendar features. We have the standard version and I see our biggest problem is not having the ability to archive mail on the servers. Archiving to an individual pc is not reliable enough for us. We have a requirement to keep email for a long period for compliance so really need quick access to old mail.

My question is if we implement Exchange 2016, will it help with our archiving issue? Is there an add-on if feature not available in standard version. Is there anything we can do now within exchange 2010?  Are there better alternatives out there now for a small team predominately using mail and calendar features.

Thank you.
0
Comment
Question by:sunny-j
3 Comments
 
LVL 16

Accepted Solution

by:
Ivan earned 250 total points
ID: 41881839
Hi,

there is a feature called archive mailbox, both on 2010/ 2013 and 2016 Exchange. What that is, is secondary mailbox that is used for archiving purpose, but email is not stored on user computer (as .pst), but is rather located in mailbox on Exchange server.

Benefit is that all your email is located on Exchange, so you don't need to worry about user computer. Archive mailbox can be located in some other database, which can be located on some other drives (some high capacity, low speed).

It comes with Standard edition of Exchange, BUT users that should have that archive mailbox need to have Enterprise User Exchange CAL.
So your can get those CAL only for users that require archive mailbox. If all your users require that...then you would need to buy CAL for all of them.
One thing to know, you can activate that feature even without buying enterprise cal, but you wont be covered with license..and that is not legal.

I personally use GFI Archiver, which is archiving all email, and store it in SQL. It cost per mailbox.

More about Exchange 2010 Archive mailbox: http://exchangeserverpro.com/create-archive-mailbox-exchange-server-2010/
More about GFI Archiver: http://www.gfi.com/products-and-solutions/email-and-messaging-solutions/gfi-mailarchiver

PS: There is a direct migration path, from Exchange 2010 to 2016. You do need to get new VM or server, since you cannot do in-place upgrade on same machine.

Regards,
Ivan.
1
 
LVL 39

Assisted Solution

by:Adam Brown
Adam Brown earned 250 total points
ID: 41881904
We have a requirement to keep email for a long period for compliance so really need quick access to old mail

This requirement can most easily (and inexpensively) be met with a Journaling mailbox. https://technet.microsoft.com/en-us/library/bb124985(v=exchg.141).aspx has instructions for setting this up. Essentially, a Journal mailbox captures a copy of every email in the environment and stores it in a single mailbox. In the event that a message is erased or needed for compliance purposes, a search through the mailbox in OWA or after connecting it to Outlook can be done quickly and efficiently by anyone with the necessary permissions on the mailbox. The advantage to this is that it doesn't require an Enterprise CAL to use a Journaling mailbox, and as long as access to the mailbox is tightly controlled, there is no chance that important compliance data will be erased by users. The disadvantage, however, is that using a Journaling mailbox will quickly increase the size of your mailbox database, as it ends up doubling all messages in Exchange 2010. Exchange 2016 has very capable data deduplication features that reduce the impact of this, but 2010 is not *quite* as capable in this regard. In addition, searches through a large archive mailbox can occasionally fail, so it's best to create a new journal mailbox and file away the previous one on a regular basis.
1
 
LVL 42

Expert Comment

by:Amit
ID: 41882215
For such small set of users, just set the mailbox size unlimited. Don't need to do anything else. As far as migrating to Exchange 2016. It is right time for your to move to 2016. You can Exchange deployment assistant tool.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

821 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question