J
Jake
Hello -
we are getting ready to deploy an archiving tool called Symantec Enterprise
Vault. This application takes email older than x years and puts it in a
specialized compressed vault. Users then see that email in their email with a
special 'vault' icon next to it with no preview. In order to view the email
the users double click on it. (no preview available by design)
Having said that, the only way this works in Outlook is to have Visual Basic
Scritping support enabled / installed with the Outlook installation.
Problem: Office does not install this when installing on a terminal server.
There are some articles from MS relating to this, and I have tried them
(specifically copying the OUTLVBS.DLL from a working install see:
http://support.microsoft.com/default.aspx?scid=kb;en-us;302003 ) and I would
still get Scripting Support Not Enabled Errors.
I resolved this by removing Office, modifying the MST to force Office not to
detect if the destination host is a terminal server (option 2 in above
article), and reinstalling. The scripting support is installed under the
Outlook options, and the Enterprise Vault client works great. (this is all
done in a dev environment)
The questions are:
1. how much of a security risk / hole did I create by adding the Visual
Basic Scripting Support for Outlook?
2. Does anyone know of another way to get this to work effectively or has
anyone had experience working with this product /scenario?
Thanks,
we are getting ready to deploy an archiving tool called Symantec Enterprise
Vault. This application takes email older than x years and puts it in a
specialized compressed vault. Users then see that email in their email with a
special 'vault' icon next to it with no preview. In order to view the email
the users double click on it. (no preview available by design)
Having said that, the only way this works in Outlook is to have Visual Basic
Scritping support enabled / installed with the Outlook installation.
Problem: Office does not install this when installing on a terminal server.
There are some articles from MS relating to this, and I have tried them
(specifically copying the OUTLVBS.DLL from a working install see:
http://support.microsoft.com/default.aspx?scid=kb;en-us;302003 ) and I would
still get Scripting Support Not Enabled Errors.
I resolved this by removing Office, modifying the MST to force Office not to
detect if the destination host is a terminal server (option 2 in above
article), and reinstalling. The scripting support is installed under the
Outlook options, and the Enterprise Vault client works great. (this is all
done in a dev environment)
The questions are:
1. how much of a security risk / hole did I create by adding the Visual
Basic Scripting Support for Outlook?
2. Does anyone know of another way to get this to work effectively or has
anyone had experience working with this product /scenario?
Thanks,