The Enterprise Vault team is always looking to improve our products based upon customer feedback. Some changes you want would be new features, some times it's just improvments in an existing feature etc.
So I have a question for you. What changes should we make which would not just please you but actually delight you about Enterprise Vault (apart from an ability to print money :-)?. The kind of feature that excites you, puts a smile on your face and you say I can't wait to use that, it's going to help us so much... One example for me is Virtual Vault in V8 sp3.
We have the ideas system on Symantec Connect but a lot of them seem focused on improvements to existing features (which isn't a bad thing!) and I'm just wondering what else there is out there... At the moment if I looked at that list, there are probably 4 suggestions that have 10 or more votes. I'm sure it would take more than those 4 product changes to make every customer delighted to use our product!
So some examples I can think of based upon discussions/issues on this forum
Perhaps videos on how's to etc,
Perhaps best practise document
Easier OWA setup
Very interested to hear your feedback!
Director, Enterprise Vault Engineering
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.
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
Some best practice / recommended config for Virtual Vault….