Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Enterprise Vault 6.0 SP5 -- Outlook Add-in 7.5 SP3

Updated: 21 May 2010 | 2 comments
RVD's picture
0 0 Votes
Login to vote
Hi,
 
One of my customers ordered Enterprise Vault recently, but needs to 'downgrade' to version 6.0 SP5 because he still has Exchange 5.5 servers (yes, yes, even in 2008 ... :smileywink: )
 
Can anyone tell me if the current EV 7.5 SP3 Outlook Add-ins are compatible with this old version of EV?
 
One of the reasons for asking is that this would avoid the need to install the EV forms on the Exchange servers , right? ... as they are now included in the new Outlook Add-in itself.
 
My main goal is to work with the 7.5 SP3 Oulook http-only add-in together with EV 6.0 SP3.
 
Is this possible?
 
Thx,
 
R.
 
discussion Filed Under:

Comments

sym_se_support01's picture
13
Jun
2008
0 Votes 0
Login to vote

You will still need to publish the Forms in Exchange for full functionality in Enterprise Vault 6.0.  The option to use the forms locally is only part of Enterprise Vault 2007 (Deploy Forms Locally).

As for using the http client with 6.0.sp4 you can set the Policy for Outlook Add-In behavior (UseSelfInstallFunct) as HTTP-only.  In 6.0 I believe this selection option was called Lite and Full.

The Enterrpise Vault 2007 SP3 Full (Normal) client extentions are not compatible with Enterprise Vault 6.0.  The Full client extentions are only one version compatible, so the 7.0 extentions (Full) would work with 6.0 but not the two version difference as you had described.

Again, this said, if you want to use the HTTP (Lite) client extions you can set the Policy accordingly but you will still need to register the forms on Exchange.

Maquiladoras's picture
13
Jun
2008
0 Votes 0
Login to vote

That is not exactly the Case
EV6 extensions will work with EV6, EV7 and EV2007
EV2007 extensions will work with EV2007, EV7 and EV6
 
This is referenced on Page 10 of the Compatibility guide, which can be found here