Deprecated
-
This agent is deprecated in this release. You must transition to OnePass for Exchange Mailbox (Classic) as described in Transitioning from Exchange Mailbox Archiver Agent to OnePass for Exchange Mailbox (Classic).
-
New installations of this agent are not supported in this release.
-
You must deconfigure this agent before you upgrade the client.
-
You can perform recovery operations only with the deconfigured agent.
-
You cannot perform archive jobs with this agent.
See End-of-Life, Deprecated and Extended Support - Products for information about deprecated products.
If you want to continue to use the Exchange Mailbox Archiver Agent for archiving and recovery operations, you cannot upgrade the client.
Recall fails with "Could Not Connect to EVMGRC" error
Problem 1
If Outlook Add-In users are trying to recall items that are not available in Offline cache and they do not have connectivity to the Exchange Server.
Solution 1
It is recommended for Outlook Add-In users to connect to the Exchange Server in order to recall items not available in Offline cache.
Problem 2
In a DAG configuration if the home server is unavailable during a recall operation.
Solution 2
By default in DAG configuration, recall requests are directed to the Home server, which never changes even if the server hosting the active copy changes.
If the home server is unavailable to process recall request it is recommended to place uselocalcasforrecall web.config key on the CAS server. This will enable the CAS server to process the recall request locally.
Usage
<add key="CVOWA:UseLocalCASForRecall" value="true" />User credentials are not acknowledged during a stub recall
Problem
I keep getting prompted for my credentials over and over again when trying to do a stub recall.
Solution
-
Ensure that .NET 3.5 is installed on the computer, which has OWA Proxy Enabler installed on it.
-
Log on to the IIS server installed on the computer, which has OWA Proxy Enabler installed. Navigate to the virtual directory cvwebrecall and ensure that Basic and Integration authentication is enabled.
Unable to access OWA server when recalling from message stubs
Problem
The end-user is unable to access OWA server through the web as there could be a proxy or a load balance OWA server available through which the recall request are being routed to the mail OWA server.
Solution
Places the CVOWA:CASProxyExternalUrl key in the web.config file located in <Exchange_Install_Path>\ClientAccess\OWA. This key allows the end-user to access OWA server available behind a proxy or a load balance OWA server.
Usage
<add key ="CVOWA:CASProxyExternalUrl“ value= "https://webmail.aaa.com” />Where
Value - The name of the proxy or the load balancing server. For example there is a load balance server named “webmail.aaa.com” available in front of OWA servers. The end-user access OWA through the URL “https://webmail.aaa.com”. In this case the value of this key should be set to “https://webmail.aaa.com”.
Unable to access OWA server when recalling from the Universal Stub Link
Problem
An end-user doing Universal recall is unable to access OWA server through the web.
Solution
Places the CV:OwaRoot key in the web.config file located in <Exchange_Install_Path>\ClientAccess\OWA. This key provides an alternative OWA URL to be used for auto open when a load balance server is available with the OWA server. In such cases the OWA URL returned by the auto discover service may not accessible from outside.
Usage
<add key ="CV:OwaRoot“ value="https://webmail.aaa.com” />Where
Value - Is the name of the proxy or the load balancing server. For example there is a load balance server named “webmail.aaa.com” available in front of OWA servers. The end-user access OWA through url “https://webmail.aaa.com”. In this case the value of this key should be set to “https://webmail.aaa.com”.
Auto discover services are not available during OWA recalls when recalling from message stubs
Problem
For an end-user Exchange auto discover services on ‘serverA’ is not available when he is accessing OWA through ‘serverA’.
Solution
Places the CVOWA:AutoDiscoverUrl key in the web.config file located in <Exchange_Install_Path>\ClientAccess\OWA. If auto discover URL on the server is inaccessible, the following web setting key can be used to provide an alternative auto discover URL.
Usage
<add key ="CVOWA:AutoDiscoverUrl" value ="https://serverB/autodiscover/autodiscover.xml"/>Where
Value - Is the set to Server B on which the Exchange auto discover services are available.
Auto discover services are not available during OWA recalls when recalling from the Universal Stub Link
Problem
For an end-user doing Universal recall, Exchange auto discover services on ‘serverA’ is not available.
Solution
Places the CV:AutoDiscoverUrl key in the web.config file located in <Exchange_Install_Path>\ClientAccess\OWA. If auto discover URL on the server is inaccessible, the following web setting key can be used to provide an alternative auto discover URL.
Usage
<add key ="CV:AutoDiscoverUrl" value ="https://serverB/autodiscover/autodiscover.xml" />Where
Value - Is the set to Server B on which the Exchange auto discover services are available.
Unable to select an Alternate Active Directory server during OWA recalls to retrieve mailbox information when recalling from message stubs
Problem
By default OWA recall use the Active Directory server selected by Active Directory Domain Service on OWA server to get the details of the current OWA logged on user through the Active Directory query. This process would not be functional in case the user wants to use an alternate Active Directory server.
Solution
Places the CVOWA:LdapPath key in the web.config file located in <Exchange_Install_Path>\ClientAccess\OWA. Add the name of the alternate Active Directory server as the value for the key to get the details of the current OWA logged on user.
Usage
<add key="CVOWA:LdapPath" value="dc.domain.com" />Where
Value - Is the AD alternate server name. For example if the user wants OWA recalls to use "dc.domain.com" as the Active Directory server to retrieve mailbox information.
Unable to select an alternate Active Directory server during OWA recalls to retrieve mailbox information when recalling from the Universal Stub Link
Problem
Universal recall utilize Exchange auto discover service to retrieve mailbox information. By default the Active Directory query generates the auto discover URL but the user is not able to retrieve auto discover URL information by using any other AD server.
Solution
Places the CV:LdapPath key in the web.config file located in <Exchange_Install_Path>\ClientAccess\OWA if the user wants to use a specific Active Directory server to retrieve the Exchange auto discovery URL.
Usage
<add key="CV:LdapPath" value="dc.domain.com" />Where
Value - Is the AD alternate server name. For example if the user wants OWA recalls to use "dc.domain.com" as the Active Directory server to retrieve mailbox information.
OWA recall fails with permission error in a multiple site exchange environment
Problem
By default OWA recalls use the account of the current log on OWA user to communicate with EWS. If there are multiple sites involved, OWA request may be redirect to a CAS or mailbox Role server located in another site.
This may lead to loss of user account information during the OWA redirection and therefore the EWS call may fail.
Solution
Places the CVOWA:UseArchiverAccount key in the web.config file located in <Exchange_Install_Path>\ClientAccess\OWA. This key provides a way to use Commvault archiver account instead of current OWA log on user account to communicate with EWS.
Usage
<add key =”CVOWA:UseArchiverAccount” value=”true” />For Exchange 2010
When using CVOWA:UseArchiverAccount key run the following power shell command on the Client Access Server against the account specified on the properties of the Exchange Archiver account:
New-ManagementRoleAssignment –Name:impersonationAssignmentName –Role:ApplicationImpersonation –User:ArchiverUser
For Exchange 2007
When using CVOWA:UseArchiverAccount key run the following power shell commands on the Mailbox Role server against the account specified on the properties of the Exchange Archiver account:
Get-ExchangeServer | where {$_.IsClientAccessServer -eq $TRUE} | ForEach-Object {Add-ADPermission -Identity $_.distinguishedname -User (Get-User -Identity ArchiverUser | select-object).identity -extendedRight ms-Exch-EPI-Impersonation}
Get-MailboxDatabase | ForEach-Object {Add-ADPermission -Identity $_.DistinguishedName -User ArchiverUser -ExtendedRights ms-Exch-EPI-May-Impersonate}
OWA recall failing with LDAP permission error
Problem
By default OWA recall does impersonation to do Active Directory query, but in case the logged on user does not have the permissions to run an Active Directory query the recalls will fail with LDAP permission errors.
Solution
Places the CVOWA:ImpersonateUser key in the web.config file located in <Exchange_Install_Path>\ClientAccess\OWA. This key controls whether to impersonate the current OWA logged in user to query mailbox information from AD.
Usage
<add key =”CVOWA:UseArchiverAccount” value=”true” />Where
Value - can be set to False when the user does not have the correct LDAP permissions.
OWA is attempting to recall from a server that does not have Exchange Web Service (EWS)
Problem
Recalls from OWA are failing when the user is trying to accesses OWA through server A from which the Exchange Web Service (EWS) is blocked. Where as the EWS is accessible from server B.
Solution
By default OWA recall uses the same host server as that of Exchange Web Service (EWS). In case the user has the EWS configured on another server, they would require an alternate EWS host server name to complete the recall process.
This can be done by placing the CVOWA:NameResolution key in the web.config file located in <Exchange_Install_Path>\ClientAccess\OWA.
Usage
<add key="CVOWA:NameResolution" value="Excforrecall" />Where
Value- Is the EWS host server name.
Exchange Web Service (EWS) is not configured as SSL site for end-user
Problem
By default OWA recalls communicates with EWS with SSL http protocol. In case EWS is not configured as an SSL site, the end-user would not be able to recall from OWA.
Solution
Place CVOWA:UseNonSSLForEwskey in the web.config file located in <Exchange_Install_Path>\ClientAccess\OWA.
Usage
<add key="CVOWA:UseNonSSLForEws"/>Unable to view OWA recall logs
Problem
You are unable to view the OWA recall logs from 'CvDiagnostics.
Solution
Places the CVOWA:EventLog key in the web.config file located in <Exchange_Install_Path>\ClientAccess\OWA. If this key is enabled, the OWA recall logs will be written to 'CvDiagnostics' event entry.
Usage
<add key ="CVOWA:EventLog" value="true"/>Permission restrictions for end-user to run Active Directory query
Problem
For end-users the permissions set to run Active Directory query are restricted and therefore retrieving complete mailbox information is not possible for the end-user.
Solution
Places the CVOWA:UseAutoDiscover key in the web.config file located in <Exchange_Install_Path>\ClientAccess\OWA. This key allows to modify the end-user environment and allows him to retrieve complete mailbox information by replacing the Active Directory look up service with the Exchange auto discovery service.
Usage
<add key ="CVOWA:UseAutoDiscover" value="true"/>The stubs are not getting deleted after recalls
Problem
The stubs still appear after a stub recovery operation.
Solution
Places the CVOWA:DeleteStub key in the web.config file located in <Exchange_Install_Path>\ClientAccess\OWA. This key is used to set delete stub option globally. If the setting is set to 'true', the stub will be deleted after recovering. If the setting is set to 'false', the stub will not be deleted after recovering.
Usage
<add key ="CVOWA:DeleteStub" value="true"/>