Due to a mistake made with policies in a customer's environment, their Outlook 2007 install on their EV 220.127.116.111 server has been upgraded with Office 2010 Pro Plus.
Means the Outlook client on the EV server is now 2010 SP1 Oct12-CU (14.0.6...
I'm not sure if it was something I read, or was advised on a support call in the past, but is there some recommendation that collections should NOT be enabled on journal partitions?
I've had a skim through various documents I have, googled and ...
Have an intermittent issue that seems to be occuring a few times a week, no services stop, but a restart of the services or server gets things running.
Seems to be 3 Enterprise Vault events (all with a Task Category of Web Application WP) on t...
Spent most of the day reading through the multiple discussions around Leavers processes.
Still having an issue with how I would like to deal with Leavers accounts.
If all my users are EV enabled and being successfully archived by EV, when it ...
Looking at a customer's EV setup.
BE2010 R2 Win 2008 R2 installed on the EV server, SQL DB's also locally on the same server
EV incrementals during the week, full backup at the weekend, job uses the EV agent
Job fails with "Final e...
It's looking like that's my only option!
I understand the MAPI profile won't be happy as it has been upgraded/tagged as an Outlook 2010 one in the rgeistry.
Should the safe process be to stop EV, disable the services, uninstall Outlook 2010.
Having previously looked at the compatibility charts, I've only just spotted the 'Microsoft Outlook on the Enterprise Vault server' section!
Outlook 2010 not supported on EV 9 to 11, so presuming EV 8 will be the same.
Just not sure what is broken ...
It's just on standard SAN storage.
The journal also rarely gets searched and performance wouldn't be a big concern.
The backups would see the biggest benefit from enabling collections, so it makes sense for me to enable them then.
Had almost forgotten about this thread, still having intermittent issues with EV though, the previous fixes did nothing.
Do believe Symantec Support have now given us the root cause of the issue though, and it does tie in with your fi...
I'm to apply http://www.symantec.com/docs/TECH35691 (AV exceptions were already in place, so just the MSMQ reg key) and rerun the EV Exchange permissions script tonight, will see what happens after that.