Forum Discussion

Cdee's avatar
Cdee
Level 6
14 years ago

Installing Symantec Enterprise Vault OWA extensions

Hi All,

I am planning to install OWA extensions on my Exchange 2010 CAS server in order that users can access Archived mails using OWA.
I was able to plan almost everything i.e

Installing OWA extensions on 2010 CAS box
Creating the ExchangeServer.txt on EV server.
Modifying the Desktop Policy.

But i have an confusion while going througt this Article
http://www.symantec.com/business/support/index?page=content&id=HOWTO38207#v9666766

"

To configure the Data Access account for OWA

  1. Create or select a domain account to be used for anonymous connections to the Enterprise Vault server. This is the Data Access account. The account should be a basic domain account; a local machine account cannot be used. The account should not belong to any administrator group, such as Administrators or Account Operators.

    If you are configuring both Enterprise Vault OWA Extensions and Domino Mailbox Archiving, it is important to use the same account as the Data Access account for both features. If you have already set up Domino Mailbox Archiving, note the details of the account specified on the Data Access Account tab of Directory properties in the Administration Console

Which says to configure the Data Access account.
Is it actually required in my case where i only have Exchange mailbox archiving and no domino mailbox's??

and also do i need to run cscript owauser.wsf /domain:domain /user:username command.

or simply doing above 3 steps should help me get users access to archived emails using OWA

  • You would run the script under the context of the EVAdmin (i.e. RDP to the EV Server and specify the EVAdmin credentials to log on) BUT the user you specify IN the OWAUser.wsf script would be a new EVAnon account.

    So you would create a regular user in AD, nothing special about it, doesn't need Send As/Receive As permissions or anything, just a regular account, and then specify that user... i.e.

    owauser.wsf /domain:myDomain /user:EVAnon /password:myPassword

4 Replies

  • You don't need to run the Data Access Account thing, its not set up on mine, and i have a hybrid Exchange 2003 and 2010 environment and OWA works perfectly

    You will definitely need to run the OWAUser.wsf script, because this creates the EVAnon IIS virtual directory, and also sets EV up so that any calls coming from this EVAnon user account will be authenticated properly against EV

    If you do not run the OWAUser script then you will not be able to archive/retrieve/restore from OWA or be able to launch Archive Explorer or Browser search...in addition if you plan to use Outlook Anywhere (RPC over HTTPS) then this too would also fail

  • oh and after you run the OWAUser.wsf script you will have to restart the "Enterprise Vault Admin Service" (Which will restart all the other EV services in turn) so it can load the new EVAnon acount in to the cache, and then synchronize your users so that it specifies who the EVAnon account is and that the evanon account should have access to their items

  • Can i use the EV service account while running the OWAUser.wsf command line or any other account.

  • You would run the script under the context of the EVAdmin (i.e. RDP to the EV Server and specify the EVAdmin credentials to log on) BUT the user you specify IN the OWAUser.wsf script would be a new EVAnon account.

    So you would create a regular user in AD, nothing special about it, doesn't need Send As/Receive As permissions or anything, just a regular account, and then specify that user... i.e.

    owauser.wsf /domain:myDomain /user:EVAnon /password:myPassword