Exchange Server 2013 built in archiving limitation and caveats ?

Hi All,

May I know if anyone here know what's the limitation and the caveats when using the builtin / native archiving feature in Exchange Server 2013 ?

Does the following statement still applies to the Exchange Server 2013 SP1 ?

To access an archive mailbox in Exchange 2013, two different clients can be used: Outlook and OWA. Exchange ActiveSync is still not supported.

It is important to consider that Outlook 2007 requires the Office 2007 Cumulative Update for February 2011 and, even then, it provides only limited capabilities for archiving. With Outlook 2007, users can access their archive and:

Move or copy messages and folders between their primary mailbox and their archive;
Move or copy messages and folders between PSTs and their archive (as long access to PSTs is not blocked);
Export or import messages to and from the archive;
Use Inbox Rules to automatically move messages to a folder in the archive mailbox.
However, some functionalities are not supported in Outlook 2007, such as:

When a user searches the primary mailbox and selects All Mailbox Items, Outlook does not search the archive mailbox. Similarly, when the user searches the archive mailbox, the primary mailbox is not searched.
Default archive policies for the mailbox continue to be applied but users cannot use personal tags to move items to their archive.

because at the moment I'm currently considering to get Symantec Enterprise Vault v11 but wondering if the Exchange Server 2013 archiving feature is getting better or on par with the other 3rd party archiving tools.

Thanks in advance.
LVL 9
Senior IT System EngineerIT ProfessionalAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

George SasIT EngineerCommented:
Not sure what are you worried about here....
I'm still running exchange 2010 but I have seen and tested the online archive feature in 2013 and seems pretty neat and easy to use.
Why would you want to use Symantec Vault ? That was a good idea back in the time when Exchange 2003-2007 was still alive.
0
Simon Butler (Sembee)ConsultantCommented:
The primary question you have to ask yourself is WHY you want to archive.
 
If it is for regulatory reasons, then I don't consider it a suitable product - despite what Microsoft may say.
To satisfy a lot of regulators you need to journal the email, archiving out of the mailbox is too late, because the message could be modified by the user before archiving takes place.
You would then need to use legal holds etc to ensure the users do not delete the content.

However if you just want to reduce the content of the primary mailboxes and can live with the limitations on the client side, then it does the job very well. Enterprise CALs required of course. Put the archive databases on cheaper high capacity storage and you don't really need to worry about it too much.

Simon.
0
Senior IT System EngineerIT ProfessionalAuthor Commented:
ok, so what are the client limitations that is still around in Exchange Server 2013 SP1 ? or does the client must be using Outlook 2013 Enterprise ?
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

George SasIT EngineerCommented:
To avoid the limitation you mentioned the client should be at least Outlook 2010 standard. The CAL's Simon is talking about are for the Exchange server for the clients that need to use online archive and not for the outlook itself.

Ans as Simon said, this was also my point, Exchange 2010-2013 are intended to work on JBOD storage that is pretty cheap this days. No more expensive SAN installations, just use cheap disks with multiple database copies and you should be safe.
0
Senior IT System EngineerIT ProfessionalAuthor Commented:
Thanks George,

So in this case, I'll need to deploy Outlook 2013 Professional first and then deploy Exchange Server 2013 Enterprise to make sure that I don't experience the problem described in the above statement ?
0
George SasIT EngineerCommented:
Outlook 2010 will do also, but if you need to change the client then yes, go directly to Outlook 2013.
Here are the requirements :
http://office.microsoft.com/en-us/outlook-help/license-requirements-for-personal-archive-and-retention-policies-HA102576659.aspx
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Senior IT System EngineerIT ProfessionalAuthor Commented:
Cool. thanks
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.