How to uninstall Enterprise Vault (EV) Outlook Web Access (OWA) Extensions for Exchange 2000/2003 if the normal uninstall procedure fails

Article:TECH48311  |  Created: 2006-01-27  |  Updated: 2013-08-28  |  Article URL http://www.symantec.com/docs/TECH48311
Article Type
Technical Solution

Product(s)


Issue



How to uninstall Enterprise Vault (EV) Outlook Web Access (OWA) Extensions for Exchange 2000/2003 if the normal uninstall procedure fails


Solution



This document describes the how to remove Enterprise Vault OWA 2003 and OWA 2000 Extensions from Exchange Servers if the normal uninstall procedure fails.

Note You cannot manually remove Enterprise Vault OWA 2007 Extensions using the steps described in this document.
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

For Enterprise Vault 8.0 or later, the normal procedure for uninstalling the Enterprise Vault OWA Extensions is documented in the following technical note:  http://www.symantec.com/docs/TECH77119

For earlier releases of Enterprise Vault, the normal procedure for uninstalling the extensions is documented in the Installing and Configuring manual.

The following steps summarize what you need to do if the normal uninstall procedure fails:

1. Remove Enterprise Vault servers from the proxy bypass list.
2. Delete forms registrations.
3. Delete Enterprise Vault OWA virtual directories.
4. Turn off the script access flag on the Exchange mailbox and public folder virtual directories.
5. Exchange Server 2003 only: Restore OWA controls files.
6. Complete the removal of the OWA Extensions.

This document provides detailed instructions for each step.

The instructions given are also valid when removing the OWA Extensions in a clustered environment. In environments where back-end Exchange Servers are clustered, the steps should be performed on each node on which the Exchange Virtual Servers can run.

Removing Enterprise Vault servers from the proxy bypass list

To find out which servers were added to the proxy bypass list by Enterprise Vault, open the appropriate OWA Extensions configuration log file for the Exchange Server:

C:\Program Files\Enterprise Vault\OWA\Frontend2003setup.wsf.log
C:\Program Files\Enterprise Vault\OWA\Backend2003setup.wsf.log
C:\Program Files\Enterprise Vault\OWA\Backend2000setup.wsf.log

Find the proxy bypass list configuration lines are near the end of this log file. For example:

1 28/10/2009 10:59:20 AM : Info : ConfigureProxyBypassList : Configuring proxy bypass list...
2 28/10/2009 10:59:20 AM : Debug : ConfigureProxyBypassList : Added: 192.168.300.110
3 28/10/2009 10:59:20 AM : Debug : ConfigureProxyBypassList : Opening EVServers file: C:\Program Files\Enterprise Vault\OWA\EVServers.txt
4 28/10/2009 10:59:20 AM : Debug : ConfigureProxyBypassList : EVServers file opened
5 28/10/2009 10:59:20 AM : Debug : ConfigureProxyBypassList : Read EVServer from file: alias2003Vault.example.com
6 28/10/2009 10:59:20 AM : Debug : ConfigureProxyBypassList : Closing EVServers file
7 28/10/2009 10:59:20 AM : Debug : CfgProxyBypassList : No current proxy settings found, error: -2147024894 Invalid root in registry key "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\WinHttpSettings".
8 28/10/2009 10:59:20 AM : Debug : CfgProxyBypassList : New bypass list length: 46
9 28/10/2009 10:59:20 AM : Debug : CfgProxyBypassList : New bypass list: 192.168.300.110;<local>;alias2003Vault.example.com
10 28/10/2009 10:59:21 AM : Info  : EVLog::Class_Terminate : Setup finished successfully at: 28/10/2009 10:59:21 AM
From the log file entries you can determine the following information:

 
  • The configuration adds the IP address of the local computer (line 2 in the example file), the servers listed in the EVServers.txt file (line 5 in the example file) and the term "<local>".
  • If servers have been added previously for another application, these are listed under the following registry setting (line 7 in the example file). In the example file, this registry setting is empty, so the proxy bypass list contains Enterprise Vault servers only.

HKEY_LOCAL_MACHINE
\SOFTWARE
 \Microsoft
  \Windows
   \CurrentVersion
    \Internet Settings
     \Connections
      \WinHttpSettings

 
  • The new proxy bypass list, including all the Enterprise Vault servers, is shown in the log file (line 9 in the example file).

To remove the Enterprise Vault servers from the proxy bypass list you can do one of the following:

 
  • Use Regedit to edit the \WinHttpSettings registry setting:
  • If there are additional servers for other applications, then edit the registry setting and remove the Enterprise Vault servers.
  • If there are only Enterprise Vault servers, then you can delete the \WinHttpSettings registry setting.
  • Use the proxycfg utility.
  • If there are additional servers for other applications, then you could use a command line similar to the following to remove all the current servers and restore the servers for the other applications:
proxycfg -p <proxy server> "<proxy bypass list>"
 
  • If there are only Enterprise Vault servers, then you can remove all the entries with the following command line:
proxycfg -d
 

Deleting forms registrations

To remove forms registrations against public folders and mailboxes, you can use a tool, such as Microsoft Exchange Explorer, or Microsoft Exchange Server MAPI Editor (MFCMAPI). The instructions given in this section are for Exchange Explorer.

Exchange Explorer is available as part of the Exchange Software Development Kit (SDK) Development Tools, which you can download from the following address:
 http://www.microsoft.com/downloads/details.aspx?FamilyId=4AFE3504-C209-4A73-AC5D-FF2A4A3B48B7&displaylang=en

Before you use Exchange Explorer to delete the forms registrations for each of the information stores, you will need to know the URL to the information stores in the Exchange store.

To find the URLs to each of the information stores configured by Enterprise Vault, do the following:

 
1. Open the appropriate Enterprise Vault OWA Extensions configuration log file, Backend2003setup.wsf.log or Backend2000setup.wsf.log. This file can be found in the Enterprise Vault installation folder (typically C:\Program Files\Enterprise Vault\OWA) on the back-end Exchange Server.
 

 
2. Work through the file and find the lines containing the following text:
 

 
"ConfigureMailboxInfoStore            : Registering forms using mailbox: ...
 
...
 
ConfigureSchema                      : Connected to:..."
 
or
 
"ConfigurePublicFolderInfoStore       : Registering forms
 
...
 
ConfigureSchema                      : Connected to:..."
 

 
3. For each information store, copy the URL shown after Connected to to a text file. For example:
 
http://EXCHANGESERVER/exadmin/admin/example.com/mbx/SystemMailbox{4E084D74-82B2-48A7-A8BF-A297DA40DE62}/%23%23SchemaURI%23%23/
 

 
4. In the copied URL, change "%23" to "#" as follows:
 
http://EXCHANGESERVER/exadmin/admin/example.com/mbx/SystemMailbox{4E084D74-82B2-48A7-A8BF-A297DA40DE62}/##SchemaURI##
 

 
5. You can now use each of the URLs listed in your text file to connect to the required information stores in the Exchange store, and remove forms registrations, as described below.
 

To use Exchange Explorer to remove the forms registrations created for Enterprise Vault OWA Extensions, do the following on back-end Exchange 2000 and Exchange Server 2003 computers:

 
1. After installing the Exchange SDK Development Tools, click Start > All Programs > Exchange SDK > Exchange SDK Development Tools > Exchange Explorer to start Exchange Explorer.
 

 
2. In the Authorization dialog, enter the username and password of the Exchange administrator.
 
In the Exchange store URL box enter the first URL listed in your text file. For example:
 
http://EXCHANGESERVER/exadmin/admin/example.com/mbx/SystemMailbox{4E084D74-82B2-48A7-A8BF-A297DA40DE62}/##SchemaURI##
 

 
3. Click OK to connect to the Exchange store.
 

 
4. In the Exchange Store Hierarchy pane select the Default container. (Figure 1)
 

 
Figure 1
 


 
5. In the list of properties (bottom right-hand pane), scroll down to the base schema property:
 
urn:schemas-microsoft-com:exch-data:baseschema
 

 
Double-click the property, and click OK to the prompt that the property should be edited under the schema node.
 
The Edit Property window then opens. (Figure 2)
 

 
Figure 2
 




 
6. To find the entry that references the OWA2003Forms directory, select each entry in turn and click Edit, check the value, then click Cancel to close the Edit Property Value dialog.  (Figure 3)
 

 
Figure 3
 


 
7. In the Edit Property dialog, select the value that references the OWA2003Forms directory and click Remove.
 

 
8. Click OK to close the Edit Property dialog.
 

 
9. In the main Exchange Explorer window, right-click the KVS node in the left-hand pane (Exchange Store Hierarchy), and select Delete Folder.
 

 
10. This completes the removal of forms registrations for this information store. You need to repeat the process for each information store that was listed in the Enterprise Vault OWA Extensions configuration log file.
 
To repeat the process for the next information store, click File > Connect to in Exchange Explorer, and enter the URL for the next information store.
 

Deleting Enterprise Vault OWA virtual directories

First delete Enterprise Vault OWA virtual directories from Active Directory as follows:

 
1. On the back-end Exchange Server open Exchange System Manager (ESM).
 
2. Expand Servers > Servername > Protocols > HTTP > Exchange Virtual Server
 
3. Delete the Enterprise Vault virtual directories associated with the Exchange mailbox and public folder virtual directories. If the Exchange virtual directories are called Exchange and Public, then the Enterprise Vault virtual directories are called EnterpriseVaultExchange and EnterpriseVaultPublic.
 
4. Close ESM.
 

On the back-end Exchange Server delete Enterprise Vault OWA virtual directories from IIS as follows:

 
1. On the back-end Exchange Server open IIS Manager.
 
2. Expand Web Sites > Default Web Site.
 
3. Delete the Enterprise Vault virtual directories associated with the Exchange mailbox and public folder virtual directories. (Typically EnterpriseVaultExchange and EnterpriseVaultPublic).
 
4. Delete EnterpriseVaultProxy and EVOWA virtual directories
 

On the front-end Exchange Server, use IIS Manager to delete the Enterprise Vault proxy virtual directory as follows:

 
1. On the front-end Exchange Server open IIS Manager.
 
2. Expand Web Sites > Default Web Site.
 
3. Delete the EnterpriseVaultProxy virtual directory.
 

Turning off the script access flag on the Exchange mailbox and public folder virtual directories.

When Enterprise Vault OWA Extensions are configured, execute permission for scripts is set on Exchange mailbox and public folder virtual directories that provide access to OWA, for example, the Exchange virtual directory. When you have uninstalled the extensions, you may want remove this permission. Before removing the permission, ensure that it is not required by other applications.

To remove script execute permission from Exchange virtual directories, do the following:

 
1. On the back-end Exchange Server open Exchange System Manager (ESM).
 
2. Expand Servers > Servername > Protocols > HTTP > Exchange Virtual Server
 
3. Right-click the Exchange mailbox virtual directory (typically called Exchange), and select Properties.
 
4. On the Access tab, for Execute Permissions select None.
 
5. Click OK to save the change and close the Properties dialog.
 
6. Repeat these steps for any other Exchange virtual directories that provide access to OWA.
 

Exchange Server 2003 only: Restoring OWA controls files

On front-end and back-end Exchange Server 2003 computers:

 
1. Copy the OWA controls files from the following folder:
 
C:\Program Files\Exchsrvr\exchweb\6.5.nnnn.n\Controls-originals copied by Enterprise Vault
 
to their original location:
 
C:\Program Files\Exchsrvr\exchweb\6.5.nnnn.n\Controls
 

 
2. You can then delete the Enterprise Vault controls files folder:
 
C:\Program Files\Exchsrvr\exchweb\6.5.nnnn.n\Controls-originals copied by Enterprise Vault)
 

Completing the removal of the OWA Extensions

On Exchange Server 2003

 
1. When all the Enterprise Vault virtual directories, forms registrations and proxy bypass list configuration have been removed, select and remove the Enterprise Vault OWA Extensions in Add\Remove Programs in the Control Panel. Do this on both front-end and back-end Exchange Server 2003 computers
 

 
2. On front-end Exchange Servers, the following files can then be removed manually:
 
C:\Program Files\Enterprise Vault\OWA\EVfrontend.ini
 
C:\Program Files\Enterprise Vault\OWA\Frontend2003setup.wsf.log
 

 
3. On back-end Exchange Servers the following files can also be removed manually:
 
C:\Program Files\Enterprise Vault\OWA\EVbackend.ini
 
C:\Program Files\Enterprise Vault\OWA\Backend2003setup.wsf.log
 
C:\Program Files\Enterprise Vault\OWA\EVservers.txt
 

On Exchange 2000
 
1. When all the Enterprise Vault virtual directories, forms registrations and proxy bypass list configuration have been removed, select and remove the Enterprise Vault OWA Extensions in Add\Remove Programs in the Control Panel. Do this on front-end and back-end Exchange 2000 computers.
 
On front-end Exchange Servers, this will remove the following folder and its contents:
 
C:\Program Files\Enterprise Vault\OWA
 

 
2. On back-end servers, you can then remove manually the following files:
 
C:\Program Files\Enterprise Vault\OWA\EVbackend.ini
 
C:\Program Files\Enterprise Vault\OWA\Backend2000setup.wsf.log
 
C:\Program Files\Enterprise Vault\OWA\EVservers.txt
 



Legacy ID



284060


Article URL http://www.symantec.com/docs/TECH48311


Terms of use for this information are found in Legal Notices