What can we do in Enterprise Vault to DELIGHT you?

Improved PST Import functionality, specifically with Client driven Migrations.  A bit like Vcare do with the PST Flightdeck.

No The Don.
Leave it this way...   better for us :) :) :)

Conversion to PDF/A in addition to HTML would be great...

Cheers

Add the ability to do NOT searches in Discovery Accelerator

Add a real time monotoring system that provides real time monotoring of the EV environment Like the EV Dashboard system that was created by JPKnight

 Make Service packs updates and no more full binary installs

Add an update option into the GUI where the app goes out and downloads the updates to the local machine for your specific version and then you can choose which to install. 

In the monitoring page, allow ' rightclick'  on tasks and restart them

Live-Update for EV. preferably with the possibility to point to an internal liveupdate server

Monitoring page like JPKnight

Buy VCare ;-))

Applying only SP without the full install and EVPM GUI would be greate.In Client PST Migration ability to strict to specific location where pst resides not just "Documents and Settings".

EVPM UI sucks, most admins that use it want to scrip it and with a UI you cant, just my two cents....

Hello,

I'd like to ask for two small-ish things.

1) Better documentation for and control over Vault Cache in Domino Environments

Vault Cache is an incredibly useful feature, but all I get is the ability to turn it on or off. I'd like to be able to configure when vault cache is used - eg if working on a local replica or the client's IP address is in a specific range it should retrieve everything from cache. At the moment it seems that when the user's mail file is opened for the first time it checks for connectivity to the EVDG. If the client can connect, it works from the server directly. If not it uses vault cache.

This would be very useful for people who are working remotely, or are in an office where we have a Domino server (so they're working on a server copy) but there is no local EV server and a slow link between that office and the EV server.

2) NSF Imports

At the moment, if I import an NSF file it will create a folder in the user's mail file called "NSF Import" or something similar. EV then creates all of the stubs in this folder which can be used for archived email.

If we are importing a user's legacy Notes archive this archive will have a folder structure which matches the user's main mailbox, meaning that when EV migrates the folder hierarchy from the legacy archive we end up this structure in the subfolder which EV creates in the mail file.

Please could we allow EV to import the stubs back into the folders from which the messages were originally archived from?

Thanks for taking the time to ask for suggestions. I hope these make sense.

Phil.

What about a GUI based version for evpm, allowing zapping or permission changes to archives.

Thanks for everyone's input on this.  I certainly think there are  some interesting ideas here. 

Going forward please post your suggestiions using in the IDEAS tab.so we can all score them.

Remember it's about ideas that would DELIGHT YOU!

Cheers,
Mike

Sometimes for various reasons we are required to export emails from a vault into a PST in order to give it to either an external party, or a departed user. It would be nice if we could increase the limit EV imposes on PST files for these types of exports. I realize Microsoft has a best practice reccomendation for PSTs to be under a certain size, but EV seems to be even less than the Microsoft reccomendation. I think the EV limit is 1.4GB? I realize this is most likely set in order to save us from ourselves by not allowing the exported PST file sizes to increase beyond a reasonable size and risk corruption, but it would be great if we could somehow make the decision on our own to risk it and create say 4GB PST files or something. Maybe there is a registry tweak available for this, but it sure would be nice to include it in the PST export GUI as well.

Also, would like to see more concise documentation regarding best practices for vault stores housed on Centera overall, and specifically the device level sharing option and what that gets us vs. EV SIS on NTFS housed Vault stores.

Ability to update the Outlook add-in on a PC that has the VAC installed without un-installing the console

To work without Outlook being in cached mode

Stioll ahve client support for Windows 2000 workstations

@ Parick

1) clarify what you mean with " To work without Outlook being in cached mode" the client does work with cached mode? so what do you mean???
2) "Still have client support for Windows 2000 workstations" I don't think that would "DELIGHT" anyone but yourself..  Windows 2000 is not supported my M$ anymore so why should Symantec have to support a client that is not supported by the manufacture?

--wayne

The ability to import .EDB files (Exchange Databases).

SharePoint use is growing incredibly and it is being used instead of file systems in many cases.  Currently you can only set policies down to the Site level.  It would be great if policies could be set down to the List (llibrary) level.

I would be oh so delighted if there was an option to rebuild deleted shortcuts. We clear out shortcuts and zap leaving users but sometimes they come back!
When they do, I would want to give them back their shortcuts instead of having to export all the original items back to their new inboxes only to be re-vaulted 6 months later. NB we have no size limits on our email mailboxes so we´re working with terabytes here.

The level of control on partition rollover is based around allocating a (NTFS) single volume per partition, or an age based policy. Whats the point of that? Couldnt we have the abilty to limit the partition to a predetermined sized (like XGB) and then rollover.? We can then size the partitions based loosly on the amount of time it takes to back up (or recover) the partition using the backup solution at hand, and not the age of the partition or the size of storage container that holds the partition. 
This would keep partitions to a managable size for backup and recovery purposes.

Cheers
Andy

When will EV (and all its reports) support x64 Windows/SQL? Considering that EV is a resource constrained application, surely running it on a 64 bit platform would boost performance. Also 64bit hardware is now standard on most industry standard server hardware, it seems daft to me to have to downgrade the platform to i386 just to support an application. 

Would be nice to be FULLY 64bit though, wouldn't you agree? the 3 most usefull reports arent available on 64bit SSRS either. 

Some ideas....

Improved index architecture - Altavista works, but it is slow with DA granular searching over a large data set.
Single Admin console - merge EVBAADMIN, Custodian Manager, CA, EV – too many consoles, all  with different look & feel.
Hierarchical policies rather than flat provisioning – Many different options now that can lead to provisioning groups growing exponentially in number.
Change of architecture – move away from 1 EV per MBX server(s) – distributed processing with redundancy and automated failover (not simple clustering)
Improve Enterprise architecture – Directory implications are leading to designs with multiple dispersed directories
Better security controls in DA – cannot restrict ability of Case administrators to certain Archives at present.   Requires Ethical Wall options.
Improved analysers & best practice – input (automatically collect) organisational metrics and propose settings.
Input into Exchange journal settings – automated application of settings based on policy, automated switching.
Move away from mailboxes as collection points for journal messages – not best for larger organisations as it leads to extra traffic & duplication of records.  Provide an SMTP destination & de-duplicate at source.
Monitoring & reporting – We constantly have to write new scripts to monitor EV and DA & to automatically fix ‘unfixable’ issues – integrate into SCOM - EV is a mile behind other apps in this area.
Allow journaling based on message sent date not modified date (specifically for non-email journaling, e.g. bulk submissions of Bloomberg, faxing, IM by email via mailbox)

x64 is a must for the next version
Simpler service packs
MSI install
Some best practice / recommended config for Virtual Vault….

Example scenario would be a Vault implementation that started at 6.0 and has been upgraded over time to 2007.  Symant-Itas-KVS figured out over time that some initial implementation methodology was flawed like not rolling over the index volumes.  They would fix that with newer versions of Vault but there was no system in-place to go back and fix the already existing (i.e. massive) index volumes.  Adopting a system to upgrade "everything" to the latest "improvements" would make sense.

1. Delete calendar items that do not re-occur
2. Search for vaults in the admin console (large companies have several thousand vaults they need to find)
3. EVPM script to create folders does not allow you to move, copy, or rename.
4. 64 bit and allow Indexing to take up more than 4gb. :)
5. How about a Dashboard? If you have 10 or more journal mailboxes you cannot monitor them well with the current tool set.
6. Restrict the users ablility to move archived items out of an EVPM folder.
7. Monitoring for Journal Threasholds instead of using the Perfmon for EV!
8. Active Directory integration when deleting users - Same with CA and DA!
9. Remove the client from CA and DA and go back to the web page.
10. Don't use SQL indexing for Search within a Search
11. Multiple filters for CA databases.

That should keep you busy for a while :)

Love,

-G

A couple of things to the ArchiveExplorerUI would be good.

Previews for image files
Alternative restore location for files

Dan

1.) Client driven PST migrations leave a lot to be desired.

• EV assumes the file is intact and free of corruption before starting the migration, and I've had countless PST files bomb as a result.
• Client driven migrations should not default to "status 900" and instead should default all PST files to "status 100" and wait for intervention from the admin to mark which PST they want to import.  (e.g. I don't want to import SharePoint PST files and I can't always do SQL queries fast enough to set the status to 100 before the client starts uploading).
• I have to leave my migration task set to manual and stopped before I enable clients for migration and then run queries to set them all to "status 100".  That also means that for those that are uploading PST files I don't want, I have to have them restart Outlook, sometimes more than once.  If I can't get in touch with the end user, my logs fill up with "Event ID 8567, Referece: HasPstChunkMigrated".

2.) I would like a way to EASILY bulk delete shortcuts and archived content, but only if the user has permissions to do so.  Or, if the feature could be added to Archive Explorer to allow archived content to be deleted in bulk and then allow the Exchange Policy to delete orphaned shortcuts that would work too.  But I would want a way to assign permissions for people (e.g. power users, admins, etc) to do this so not anyone would be able to.

3.) It would also be nice (and I know this was already mentioned) to rebuild shortcuts for archived content.

Thanks.

I would like to see an EV-aware NetBackup client. I think that EV is a large enough product and that there are enough customers out there using NetBackup that this would be worth developing.

The fact that you have to open the EV server to the outside world to get Archive Explorer and Vault Search to work with Exchange 2007 OWA is KILLING us on Exchange migrations.  I can not sell every client ISA server or an F5 (even though I would like to).

This problem has also caused us numerous headaches when deploying Outlook Anywhere with Exchange 2007 for client that are using EV.

We have also received numerous complaints that the shortcuts in the preview pane no longer work in OWA because they do not contain an externally accessible FQDN and the extensions are no longer able to proxy these through based on the hostname.

I realize OWA is significantly different in Exchange 2007 than in 2003 but for that reason people are using it more heavily and rely on access to Enterprise Vault funcationality through it.

Jeff

Would be nice nice to have exclusions feature when selecting any of the categories eg whole exchange organization, windows group or OU. This will allow us to exclude the system mailbox etc from archiving. Unless i am missing it.

Along with many of the items mentions, some little fixes that would help:

1. A way to sort and search provisioning group targets to quickly find a target I need to remove, say for processing terminations.
2. The same request for any mailbox/user lists similar to the Find function in the Exchange 2007 gui.

As mentioned at the customer forum earlier this week, we're really struggling with Public Folder archiving, largely due to core functionality not being available, such as;

- Cannot synchronise permissions for a specific public folder, in fact, there is no 'synchronise permissions' even available for the Public Folder hierarchy at all. All we can do is do an archive run against our whole PF tree and 'hope' the modified permission is picked up, this can take up to seven days to complete, often the permissions do not sync anyway.

- Archive explorer does not display the complete PF hierarchy, a very frustrating issue. Quite often when we find folders missing in Archive Explorer, they can be successfully searched using Browser Search, or vice-versa.

- Cannot export a Public Folder to psts.

- Cannot 'run now' and archive a specific folder, neither from the VAC, nor the client.

- Continual problems with searches, both in Archive Explorer and Browser Search, we often see 'Failed to perform search' returned.

I would like to  see a way to Exclude sharepoint offline archives from the PST Migrator

also to extract cab's from secondary tape storage (i know it used to be possible)

a way to zap and do evpm via a proper gui

Add the Detail functionality to expired item deletion.  Currently, the auditing features does not capture the vault name, email subject, etc. in plain English.  I would like to be able to have a readable audit log when expired deletions are run.  The lack of this has prevented us from turning on the automated item expiry since we cannot identify what items have expired.

http://seer.entsupport.symantec.com/docs/285115.htm  this article indicates that some of this information is logged, however, it is not logged for deletions.

It would also be good to have a feature where we can run some type of report to be able to get a listing ahead of time of what items, vaults, etc. will be affected on an expiry deletion run.

Thanks
Denise

Here's a small list:

1 - DA Copy and Paste? The DA client does not allow copying of data in various text and table sections in the client. For example, to copy the list of custodians that was in an accepted search. Or the information results of a search (bottom pane). None of that can be simply copied.

2 - DA Reports, more and better reports. Specifically around the individual cases such as errors with a particular search, size of case, size of individual search, etc.

3 - Email shortcuts in EV should contain the FQDN of the archive server and not rely on the hidden message information in the mailbox. I have this issue now where I have two seperate EV sites and a user opens a mailbox in one site and then wants to retrieve an archive from another mailbox that's in the other EV site. The client automatically assumes that the user's mailbox archive is the place to look and therefore fails to find the item.

4 - DA Analytics... I don't even know how this is even possible with a large case. Enabling analytics for one case I have seen destroy a SQL server and a NetApp filer. 10,000 IOPs to the NetApp and completely ate a 2008 SQL server with 64 GBs of RAM and 4 quad cores. Insane. It doesn't work for any case over 100,000 items.

5 - DA in general. Please assume that there are some cases that can be over 1 million holds. Maybe even 5 million. Every time I called Symantec support, I get a shocked tech who thinks the number is insanely high and claims they have never seen that before. That's extremely frustrating and pretty much confirms that #4 is not possible.

6 - For EV, we use a clustered environment for Exchange that contains only a single CAS. Because of this, I can only use 1 EV server for mailbox archiving. I would love to be able to incorporate multiple EV servers based on mailbox stores instead. Basically, it would be nice to have some additional deployment/scope options for mailbox archiving in Exchange.

I'll keep adding as I think of them.

Hi

"3 - Email shortcuts in EV should contain the FQDN of the archive server and not rely on the hidden message information in the mailbox. I have this issue now where I have two seperate EV sites and a user opens a mailbox in one site and then wants to retrieve an archive from another mailbox that's in the other EV site. The client automatically assumes that the user's mailbox archive is the place to look and therefore fails to find the item."

Do you mean EV sites or you actually mean seperate EV directory databases?

Also for DA Analytics comment have you reviewed the DA 8 best practise guide? http://seer.entsupport.symantec.com/docs/326055.htm

 Logging. Logging. LOGGING! The event log is practically useless as far as determining what an EV server is doing at any time. If I run archiving in report mode againsta specific Exchange server and no report file is generated, I want to know why it's failed. I had no choice but to restart the server to get it working again when I could have done something else.

So yes, I want to see lots more logging of activity in the event log for troubleshooting and general day to day monitoring.

Better monitoring of running tasks / processes, view status of processes / tasks, etc.  This has been discussed.

One thing that would be very useful, at least for me, is the ability to have more control over contents of archives.  Two things in this regard that I'd like to see are:

- Ability to change retention categories on exiting items in the archive.  For example, when we have an employee leave the company, I usually archive all their items in EV (both files and e-mail).  However, we are required by law to only save that information for 4 years.  It would be nice if I could change the retention category on ALL items in a person's archive to 4 years, or whatever I choose.  It would also be nice to set an expiration date on an archive so it gets completely removed from the system after a certain date.

- Ability to move items around in folders after they're archived.  For example, if e-mail items are archived with NO shortcuts in Outlook, you can't go into the browser view and move them into another folder.  This is one of my users biggest complaints and rightly so.  It severely limits EV's flexibility and inhibits people from organizing their data post-archive.