What needs improvement with OpenText EnCase eDiscovery?

Please share with the community what you think needs improvement with OpenText EnCase eDiscovery.

What are its weaknesses? What would you like to see changed in a future version?

22 Answers

author avatar
Top 10Real User

Overall, the features on offer are fine and I don't see a place for improvement in that respect. The technical support on offer needs to be improved. They're quite slow to respond to our enquiries. The reporting is a bit unreliable. It needs to be better. The performance needs to be a bit better than what is on offer. It's lacking a little.

author avatar
Real User

SweepEnterprise where the limit is up to 5 machines to scan. Customised Report that can be obtained as per the user requirement. Like it should omit duplicate machines, able to Filter old machines w.r.t the new one and provide New scannes machines status.We have come across problems with the end-case. We could not find an email discovery type of module and there was not flexibility with the email. So, the moment we came across a parameter or something like that we had to either extract those extensions and then again go for another rule that can be further extracted to a readable format like Outlook. If this was included, we would find this a more useful solution. Secondly, is getting the key word search option. If you go, there are legal options, it's like a deal for file extensions. Every time we have to repeat the process and it is repetitive. Whereas, if you can get research that can be categorized by default based only by an extensions that would be a benefit. Also, if we can also add the timely matched signature that it would be helpful.

Find out what your peers are saying about OpenText, AccessData Group, Nuix and others in eDiscovery. Updated: May 2021.
501,818 professionals have used our research since 2012.