Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Archiving and eDiscovery Community Blog
Showing posts tagged with Tip/How to
Showing posts in English
Joseph Rodgers | 20 Aug 2009 | 6 comments


Unexpected slowness & EV DLLs not register properly


If computer does not have Internet access verify that Internet Explorer security setting “Check Publisher’s Revocation List” is not checked


Client is performing FSA archiving only on VM hosts.  First symptom was an extra lengthy setup time.  Normal setup with file copy, etc takes ~5 minutes.  The setup here took well over 15 minutes to complete and most of that time was Registering services and DLLs.

I initially suspected VMWare as we configured and began working with the Admin console the slowness continued.  Some examples:

Restarting the ev admin service (to restart all services) would result in  Directory service having to retry multiple times (thus delaying other services) before connecting to SQL


Rob.Wilcox | 12 Aug 2009 | 1 comment

Often when troubleshooting Enterprise Vault Outlook client issues we'll see issues related to how Outlook is connecting to Exchange.  There are several ways that people can configure Outlook, and EV needs to know about them.  Here is some information which I use regularly.

Outlook Connection mode often appears in client traces, but at the moment it is just “a number”.  You can decode them as follows :

                        evConnectionUnknown = 0,
                        evConnectionOnline = 1,
                        evConnectionOffline = 2,
                        evConnectionNoExchange = 3,

Rob.Wilcox | 12 Aug 2009 | 1 comment

Several people ask about how Enterprise Vault clears up temporary files, and why it might or might not be working on their system.  Here is how to trace it and see what it is doing :

Create a Dtrace Filter as follows :
Set adminservice v
Clear includes
Include CCleanUptempFiles
Log to a file, and then MON
Once an hour you will get the following :
2465 10:00:44.968 [5104] (AdminService) <2308> EV:M CCleanUpTempFiles::ThreadRoutine - GetTempPath
2466 10:00:45.390 [5104] (AdminService) <2308> EV:M CCleanUpTempFiles::ThreadRoutine - TempPath = C:\DOCUME~1\vsa\LOCALS~1\Temp\
2467 10:00:46.437 [5104] (...
jprknight | 29 Jul 2009 | 0 comments

Enterprise Vault Server Installation

After installing all pre-requisites and running the deployment scanner ASP.NET 2.0 is highlighted as not installed or not configured correctly (Critical). This can occur when .NetFramework 2.0 is installed before IIS. ASP.NET 2.0 has not been correctly registered with IIS.

Although I did not take a screenshot at the time ASP.NET 2.0 was missing from the below. So I was unable to give ASP.NET 2.0 Allow permissions.

imagebrowser image

I then needed to use the aspnet_regiis.exe utility to correct the problem as below:

imagebrowser image


cd windows
cd Microsoft.Net
cd Framework
cd v2.0.50727
aspnet_regiis.exe -i

It took me a little while to find this. Before which I uninstalled and reinstalled to which...

John Chisari | 28 Jul 2009 | 2 comments

This was an interesting one that came up a couple of days ago. Simple, but hope it stops someone pulling their hair out.

EV Provisioning Groups allow you to input a LDAP Query to target users using any AD attribute or a combination of attributes - very flexible solution.

So for example, you setup a 0 day Age based Mailbox policy and you want to target Temp Employees only. You have the AD attribute employeeType populated with 'Temp' for these specific users.

When you add the LDAP query 'employeeType=Temp' - EV will respond back with "The Query did not return any results". Hang on, this query works fine in AD User and Computers and other LDAP query tools, why doesn't EV see it? It is because EV queries a Global Catalog server for this information and by default the employeeType attribute is not replicated from the AD to the GC. The EV tasks also query GC's for information, so this is why Provisioning Group target setup is done the same way....

Maverik | 20 Jul 2009 | 0 comments

So often it is easy and of course important for Administrators to be planning the aspects of a new implemntation in respect of the sizing factors of an install, what they need to ingest perhaps in terms of PST's and how the product will be rolled out, the archiving strategy and some of the finer points of configuration are lost.

Results are six months later the Enterprise Vault Administrator has settings in place that are not fitting to his organization, resulting in warnings in the Enterprise Vault Event Logs, data incorrectly deleted, shortcuts removed incorrectly, archiving not taking place correctly the list goes on and on. Get it right first time and think about each aspect.

The prodcut is huge and highly configurable, however there are some things that once done cannot be easily undone or changed. So here is a check list of what you need to think about to get it right first time and have a long period of happy archiving. ;-)


Age versus...

Maverik | 20 Jul 2009 | 0 comments

Migrating from a third party vendor to Enterprise Vault, you may consider hard and too risky, but to be honest in a huge amount of cases it is not.

I have assisted with Projects such as these in the past so wanted to share my expereinces of these. Companies that I have dealt with have switched to Enterprise Vault because simply they have not received the flexibility, supportability,integration and most importantly end user expereince that other products provide. Enterprise Vault is the market leader in archiving quite simply.

Almost all third party archiving solutions have a mechanisim for restoring the data back to the users mailbox or file system and the only issue here can be storage. Planned properly this can easily be done in stages with groups of users or files. Planning and Project Management is of course the key here for a smooth transition, but this is not technically difficult just apply some common sense and a touch of expereince!! Technically this is...

jprknight | 17 Jul 2009 | 1 comment

Within our organisation we are solely concerned with email archiving. We have six Exchange 2000 active/passive clusters, with a dedicated EV server attached to each split equally across two data centres.

Before our virtualisation adventure took place we were running our EV email archiving servers on end of life hardware (End of life when the project implemented EV), which with ever increasing frequency of hardware failures took place. Typically mirrored disks would go down, raid card battery failures, RSA cards not functioning, the list goes on. It was just one big headache; and that was only the hardware.

For the software we were running on 2007 7.5 SP1, which seemed to give us no end of users complaining about their emails not completely archiving and their mailboxes not decreasing in size. We were also running on Windows 2003 SP1; which Symantec had advised us several times has serious shortcomings with MSMQs. Essentially the outgoing queues did not get processed...

skw234dmsp | 10 Jul 2009 | 2 comments

I created a initialization file that would apply different retention categories based on company policy for certain folders in Outlook. 
I run the script and it does not apply the retention category to the folders I selected.   The script will create the folders listed below
but will not apply the retention categories as expected.  Here is a copy of the script...need assistance and input ASAP... Thnx

;Scope - Custom Retention Categories for the Deleted Items, Business Documents, 180, and 540 Folders in Outlook for all DMSP

DirectoryComputerName = S6245A04
Sitename = S6245A04

;Custom retention categories assigned to the 180, 540, DeletedItems, and Business Documents Folder

DistinguishedName =/o=dmsp-mail/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=swilliams

RetentionCategory = 180

Liam Finn | 23 Jun 2009 | 0 comments

Using Discovery Accelerator you find an item that is failing to export using the export or production features in Discovery Accelerator

So now you need to prove the item exists in the archive.

There are two ways to do this
1. Search in EV and dig through mounts of results to fine the one item
2. Find the item Saveset ID and then search in EV by Saveset

Option one make little sense as the search will be fast but unless your search is very, very targetted chances are you will get back hundreds if not thousands of results which will take you hours to look through to find the one item you need

Option two is the easier way to go as it will get you the saveset and then you just search for the saveset or in the case of a Centera you can extract the saveset direct from the Centera device. (see

/* Run this query against the Discovery Accelerator...