Knowledge Base Article

Archiving Exchange Server 2013 with Enterprise Vault 10

Hello all,

In this article I want to cover the steps of configuring Enterprise Vault for Exchange Server 2013 archiving. In fact I prepared a personal configuration guide and I want to share it. If you have any recommendation, it would be nice for me to update the guide. Anyway, let`s rock :)

Firstly I want to explain my test environment.

VMware Fusion as virtualization software

One Domain Controller (Windows Server 2012 Datacenter)

One Exchange Server 2013 installed on Windows Server 2012 Domain Controller

One Certificate Authority installed on Domain Controller

One SQL Server 2008 R2 (I will install Enterprise Vault on this server)

One Windows 7 Client with MS Office Pro Plus 2013 installed

FQDN of exchange server and domain controller:

FQDN of sql server and enterprise vault:

Let`s configure the server which we want to install Enterprise Vault 10.

At this stage I assume that;

- SQL Server is properly configured

- Vault Admin Account is properly created and configured with sufficient permissions

Log on to EV server with Vault Admin Account. I will explicitly warn you when you need to log on to Exchange Server.

1- To improve server performance, change the TEMP folder location.

a. image

b. Q:\ drive is for TEMP,CACHE,MSMQ,INDEX and VSG locations for my test server.

c. At production you should use several partitions for best practice.

2- To improve server performance change default msmq path.

a. image

b. You should take MQ offline before changing path. And be sure about sufficient NTFS permissions for new path(in this scenario the system{for example you can use everyone account } has to have sufficient ntfs permission on Q:\msmq folder)

c. Do not forget to take MQ online after path operation!

3- Install .Net 3.5 SP1 feature

4- Install IIS role

5- Open IIS management console and obtain an SSL certificate. Bind it to Default Web Site

a. Note: If you have a wild card ssl certificate you can use it

6- Install MS Outlook 2007 , Install SP3 ,Install KB2596598

7- Log on to Exchange Server .There are two PowerShell scripts those are located on EV installation media. Copy them to exchange server and run these scripts in exchange management shell. You can find the instructions about how to run these scripts in EV Installing and Configuring pdf document(this is also in EV media)

a. SetEVExchangePermissions.ps1

b. SetEVThrottlingPolicy.ps1

8- Log on to Exchange Server. Give “Send As” permission to Vault Admin Account on Vault System Mailbox. You can use either Exchange Admin Center or Exchange Management Shell

a. image

b. Add-adpermission –identity evsysmbx –user domain\vault_admin_account –accessright extendedright “send as”

9- Log on back to EV Server with Vault Admin Account

10- Configure EV system mailbox MS Outlook profile.

11- Keep in mind à Exchange Server 2013 Outlook Anywhere configuration will probably be needed!!!

12- Be sure you can open EV system mailbox outlook profile with EV vault admin account.

13- Run Symantec EV setup.

14- image

15- “Prepare my system” is very important. Because if you have a problem, you will be aware of it before it is too late.

16- image

17- Deployment Scanner is very important too.

18- image

19- A proper example is as shown above

20- image

21- Hit the install

22- After installation and reboot phases, log on to EV server with Vault Admin Account again and go on…

23- You need to run Enterprise Vault Configuration wizard.

24- With this initial configuration you will have Directory DB, EV Alias, Monitoring DB, VAC configuration etc…

25- For mailbox (enable, disable, pst etc..) messages copy “C:\Program Files (x86)\Enterprise Vault\Languages\Mailbox Messages\en\EnableMailboxMessage.msg” to “C:\Program Files (x86)\Enterprise Vault” directory. Of course the language selection is up to you

26- Open IIS management console

27- image

28- Set the value as shown above

29- OPTIONAL: If you have Exchange Server 2010 CAS role, install EV OWA 2010 add-in on CAS server

30- Create ExchangeServers.txt and write Exchange Server CAS IP address in it.

31- Run owauser.wsf script --> cscript owauser.wsf /domain:myDomain /user:evowausr /password:P5ssword

32- Restart Enterprise Vault Admin Service.

33- Open EV Admin Console.

34- Create Vault Store Group, Vault Store, Vault Store Partition

a. image

35- Add Domain and Exchange Server

a. image

36- Configure Mailbox Policy and Desktop Policy

a. image

37- Configure Retention

a. image

38- Set task properties according to your design or environment.

a. image

b. image

39- If you run the mailbox archiving task, EV functionality begins.


40- Now, time to open archived items. You need to do few more steps. You can configure some settings from Desktop Policy

a. image

b. image

41- For Office 2013 and OWA 2013 users you need to deploy a mail application either to an individual or to whole organization.

a. $Mbx = get-mailbox "baris"

b. New-App -mailbox $Mbx.LegacyExchangeDN -Url ("" + $Mbx.LegacyExchangeDN)

c. You can use two lines above in one PS script obviously

d. This script will deploy mail application to

e. For more information you can see Setting up exchange server archiving pdf document.(in installation media)

42- For Office 2013 users you can also install an add-in as you have already known from previous versions. (You can find the proper add-in from EV installation media)

43- For Office 2010 users you need to install an add-in. (You can find the proper add-in from EV installation media)

44- image

45- As you can see from above, EV add-in is deployed and EV Mail Application is deployed too. If you do not deploy mail application to a user, that user cannot see the Enterprise Vault Mail Application but that user can use Enterprise Vault add-in!!!

46- image

47- As a result if you have Office 2013 users and Internet Explorer 9 or newer users and only have Exchange Server 2013 organization, you need only EV Mail Application. No need to install add-in :)

This is the end. I hope this is informative for you.

Published 12 years ago
Version 1.0

Was this article helpful?