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 ?
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.
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.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
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.
ASKER
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 ?
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 ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Cool. thanks
ASKER