Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Archiving and eDiscovery Community Blog

How to allow a particular user to have particular message classes to be archived

Created: 05 Feb 2013 • Updated: 29 May 2014
Rob.Wilcox's picture
0 0 Votes
Login to vote

 

Some users might have voicemails that need to be archived, but it’s not something that is widely available to all users…  and even if they did have voicemails, they wouldn’t need to be archived.

 

So..  you need …

 

1/ Update the message classes in the directory

 

On the properties of the Directory in the Enterprise Vault Admin Console is the ‘master list’ of message classes.  It’s populated with many common message classes, and if you need to you can add to the list easily.  So  first thing to do is to add the message class for the Voice Mail application that you’re using.  For example: IPM.VoiceMail

 

2/ A new archiving policy, copied from an existing one perhaps, and select the new message class

 

If it is the only thing that you want to change for these particular users then you might copy one of the existing archiving policies, or if you only have the one ‘Default’ policy, make a copy of that.  Once you have the copy, edit the policy, and on the message classes tab you now need to select the particular message class that you added in the previous step.

 

3/ A new provisioning group, and target the particular users that need this facility

 

Since we want to target a single user, or a small group of users, the easiest way to do this in Enterprise Vault is to create a new provisioning group and target the users by their name, a group that they are a member of, or even an OU that they exist in.

 

4/ Raise that provisioning group higher in the list

 

This new provisioning group should appear sooner in the list than the regular groups to ensure that the users are touched by the new policy.

 

5/ Run the provisioning task

 

Of course nothing will actually take effect until the next time the provisioning task runs, or it can be run manually… and then finally ….

 

Next archiving run should see those message classes then being archived.