Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Exchange 2010 - no evault icons OWA

Created: 24 Oct 2012 • Updated: 24 Oct 2012 | 15 comments
This issue has been solved. See solution.

I have Exchange 2010 and using Outlook 2010 and there are no evault icons in OWA, we use the premium version. Even if I view the message options and expand conversation or right click on the message I just see the regular message options such as, forward, move, reply etc - no evault icons. According to a symantec tech article I edited the webconfig file on the Exchaneg server in the specified directory and added the key that didnt exist: <add key="EnterpriseVault_EnableExtensionsInOwaAuthClient" value="true"/> restarted the Exchange Server and still cannot see any evault icons in OWA. The icons appear in Outloook 2007 and 2010 no problem and whether I'm remote or local on the LAN it's th esame problem, no icons in OWA.

Comments 15 CommentsJump to latest comment

JesusWept3's picture

can you set the web.config to enable client logging?
My guess is that it cannot read the hidden message from webdav

tolinrome1's picture

sure, can you show me how to set the web.config to enable client logging? What should I do once enabled?

JesusWept3's picture

Here is a technote regarding the EV options for the web.config

http://www.symantec.com/business/support/index?page=content&id=TECH141519

Note that editing the web.config does not require a restart of IIS or Exchange or anything, you can make them on the fly, just make sure to log out of your OWA Session then log back in

When testing this, make sure that you go directly to the CAS address and not a load balancer
Because if you make the change on say "casServerA.mydomain.com" and you're going to mail.myDomain.com, you may be redirected to a different CAS Server where the changes don't exist

Enable logging and set to log only your mailbox
then log back in to OWA and then look at the log file, you will see in there that it will attempt to read the hidden message, and if the hidden message date comes back with something crazy like 01/01/0001 , then it means that it can't be found.

JesusWept3's picture

so you want this to be in your web.config (note, logEnabled already exists in the config, but is set to false)

<add key="EnterpriseVault_LogEnabled" value="true"/>
<add key="EnterpriseVault_LogMailboxes" value=yourAddress@yourDomain.com/>

Make sure to add the log mailboxes line, otherwise it logs everyone

tolinrome1's picture

I added those keys you mentioned. Here is the webconfig settings. The first three lines are the ones I had to add.

<appSettings>
        <add key="EnterpriseVault_EnableExtensionsInOwaAuthClient" value="true" />
        <add key="EnterpriseVault_LogEnabled" value="true"/>
        <add key="EnterpriseVault_LogMailboxes" value="hrice@domain.com" />
        <add key="ConnectionCacheSize" value="100" />
        <add key="MaximumIdentityArraySize" value="100" />
        <add key="ShowDebugInformation" value="true" />
        <add key="EnableEmailReports" value="false" />
        <add key="PushNotificationsEnabled" value="1" />
        <add key="PullNotificationsEnabled" value="0" />
        <add key="MaxItemsInConversationExpansion" value="499" />
        <add key="MaxItemsInConversationReadingPane" value="100" />

I exited and logged back into OWA, where is the logfile location, what should look for? Thanks.

JesusWept3's picture

log location would be where the EV extensions are installed.
So most likely C:\Program Files\Enterprise Vault\

tolinrome1's picture

the strange this is in C:\Program Files\Enterprise Vault\ - I have two folders that are "OWA 2000 Extensions" and another "OWA 2003 Extensions". I dont see anything for OWA 2010. On the clients we are using the HTTP-only Outlook Add-In (en) Build 9.0.1.1073

JesusWept3's picture

You're looking on the CAS Server right?
So in my environment with everything as default they are under

C:\Program Files\Enterprise Vault\OWA 2010\logs

The OWA 2000 Extensions and OWA 2003 Extensions would be under the install directory on the EV Server, not the CAS Server

tolinrome1's picture

On the CAS server I dont even have an "Enterprise Vault" directory. Did I miss an install of something perhaps?

Rob.Wilcox's picture

Sounds like you haven't got the OWA extensions installed at all on the CAS - that's your next step IMHO.

SOLUTION
Rob.Wilcox's picture

For what it's worth -- the Enterprise Vault Outlook Add-in version is not relevant.  It is not involved in the Outlook Web App side of things.

What you should have on disk on your CAS is:

* Logs will be created, when enabled, in the C:\Program Files\Enterprise Vault\OWA 2010\logs folder

* The web.config file is in c:\program files\microsoft\exchange server\v14\clientaccess\owa

Earlier you mentioned you had to add the lines to the web.config file:

<appSettings>
        <add key="EnterpriseVault_EnableExtensionsInOwaAuthClient" value="true" />
        <add key="EnterpriseVault_LogEnabled" value="true"/>
        <add key="EnterpriseVault_LogMailboxes" value="hrice@domain.com" />

That seems odd, because LogEnabled for sure should be there, but set to false.  You should also in the location mentioned above, have a file called web.Config.backup by EV.1

tolinrome1's picture

Thanks, I probably didnt have those files since I dont have the OWA extensions installed on the CAS. So that leads to the question - which OWA extensions do I install on the CAS? Do I download them from Symantec?

Rob.Wilcox's picture

They are on your EV Media kit, ISO, or whatever you have.  And you'll see a folder for OWA 2010.. that's what you'll need for Exchange 2010.

JesusWept3's picture

Its part of the main installation package

\Symantec Enterprise Vault 10.0\OWA Extensions\OWA 2010 Extensions\Symantec Enterprise Vault OWA 2010 Extensions x64.msi

JesusWept3's picture

And agreed with Rob, the Client extensions for Outlook shouldn't matter, however it can be an indicator, for instance if the user doesn't see icons in Outlook (for example they are not enabled for archiving) then you wouldn't expect them to be seen in OWA

But just because you can see icons in Outlook doesn't mean that you'd necessarily see them in OWA if the extensions haven't been installed, or you need to change parts of the config file so that webdav requests use https instead of http etc

So your best bet is to install the OWA 2010 extensions on one cas server and then use that CAS servers URL to test that it works, then when that one works, install it on the other CAS servers in your environment and use those CAS servers URLs to verify that its working