Search <product_name> all support & community content...

How to uninstall and reinstall the Accelerators

Article: 100038339

Last Published: 2025-02-10

Ratings: 4 0

Product(s): Enterprise Vault

Description

The steps below are designed to completely uninstall and reinstall the main server components of Compliance Accelerator (CA) or Discovery Accelerator (DA), including the Enterprise Vault (EV) binaries and IIS.

It is strongly recommended that all CA/DA databases and transaction logs are backed up prior to performing these steps.

Important Notes

1. This article covers CA/DA version 12.x and higher.

2. Part of the steps include uninstalling/reinstalling IIS. In Windows Server 2012 and prior, this can be done without affecting .NET. In Windows Server 2016 and higher, uninstalling IIS will uninstall .NET. This means any Windows applications that use .NET will no longer function after uninstalling IIS. Such applications include Windows Server Manager, which is needed to reinstall IIS. Uninstalling/reinstalling IIS is therefore optional - if it is uninstalled, please be sure to follow the correct installation steps for the applicable Windows Server OS version.

3. When uninstalling EV/CA/DA, be sure to uninstall in the correct sequence. Any installed cumulative hotfixes or release updates should be uninstalled before uninstalling the major version. For example, if 12.5.2 is currently installed, uninstall 12.5.2 before uninstalling 12.5.0.

4. Similarly, when installing EV/CA/DA, be sure to install in the correct sequence. Any installed cumulative hotfixes or release updates should be installed after installing the major version. For example, if 12.5.2 is the current version, install 12.5.0 before installing 12.5.2.

This article is divided into two sections:

How to uninstall and reinstall Discovery Accelerator, EV Binaries and IIS

How to uninstall and reinstall Compliance Accelerator, EV Binaries and IIS

How to uninstall and reinstall Discovery Accelerator, EV Binaries and IIS

Step 1 - Capture the current DA information from the DA server

1.1. Copy the DA License from the \Program Files\Enterprise Vault Business Accelerator\Installed Licenses\ folder to a safe location. Also review the %ProgramData%\Symantec Shared\Licenses\ (and %ProgramData%\Veritas Shared\Licenses\ for 14.x and higher) folder for any installed licenses.
Note - This is an important step. A valid Accelerator license is required to run Searches, Exports, Random Sampling (CA only), Analytics (DA only), and Legal Holds (DA only with a valid DA license also needed on all EV servers). Without a valid license, the Accelerator Customer will essentially be in read-only mode. For example, items in the Review set can be previewed but cannot be Exported, Searches can be created and submitted but will not run.

1.2. Make a copy of the configuration files (*.config) from the existing Accelerator installation folder on the Accelerator server.

1.2.1. Open PowerShell and navigate to the Accelerator Server installation folder on the Accelerator server.

1.2.2. Run the following PowerShell command to list all the .config files:

Get-ChildItem *.config -Recurse | Select-Object FullName

Alternately, if the Accelerator Server installation path is known, edit the path in the following command and run the command in PowerShell:

Get-ChildItem "C:\Program Files (x86)\Enterprise Vault Business Accelerator" *.config -Recurse | Select-Object FullName

To output the list of .config files to a text file, append >> <path>\<filename> to the end of the command. Note the path must exist. For example:

Get-ChildItem *.config -Recurse | Select-Object FullName >> C:\Temp\ConfigFilesList.txt

Get-ChildItem "C:\Program Files (x86)\Enterprise Vault Business Accelerator" *.config -Recurse | Select-Object FullName >> C:\Temp\ConfigFilesList.txt

1.2.3. Make a copy of each .config file, being sure to note its folder location. It is recommended to create a folder in which to store the .config files, then recreate the Accelerator folder structure as listed in the output and store the .config files in that folder structure. For example, the web.config file may be listed in multiple locations and each file can have different content, therefore it is important not to over-write one web.config with another.

Important Note

The .config files can contain valuable information regarding any customised ports in use in the environment. These ports will need to be edited in the same files after the reinstall, using the backed up .config files' data as references. Not editing any customised ports can lead to issues connecting to the EVBAAdmin administration website and/or issues with Client connectivity. Here are some examples of port locations with default port numbers:

AcceleratorManager.exe.config:

<add key="Remoting Channel Configuration" value="name=Client Port, port=8085,suppressChannelData=false, machineName=, priority=1, secure=true, protectionLevel=EncryptAndSign, useIpAddress=true, bindTo=0.0.0.0, rejectRemoteRequests=false, exclusiveAddressUse=true, impersonate=false, authorizationModule=, typeFilterLevel=Full" />

AcceleratorAdminWeb\web.config:

<add key="RemotePort" value="8085" />

1.3. Go to the EVBAAdmin page and make a note of all of the DA Customers' information. Take screenshots of all of the configuration settings for each Customer (Discovery and Custodian). Be sure to include the following:
- Customer Type
- Name
- Directory DNS Aliases
- Administrator User or Group
- Enable Customer's Tasks (checked or unchecked)
- IIS Virtual Directory
- IIS server
- SQL server (note the details of any Always On information if present)
- Database
- Database Location For Analytics

1.4. Run SQL backups of all DA Configuration/Customer/Custodian databases.

1.5. Verify the installation media for DA and EV (matching the version and release update of EV on the EV servers) is available on the DA server.

Step 2 - Uninstall DA, EV Binaries and IIS (optional) from the DA server

2.1. Stop the Enterprise Vault Accelerator Manager Service (EVAMS) and wait at least 10-15 minutes to allow all background processing to complete.

2.2. Uninstall DA (reboot as prompted). This is best done using the Add or Remove Programs, or the Programs and Features application within the Control Panel. Be sure to uninstall in the correct sequence. Any installed cumulative hotfixes or release updates should be uninstalled before uninstalling the major version.

2.3. Open IIS Manager (Start | Windows Administrative Tools | Internet Information Services (IIS) Manager). Remove any DA websites under the Default Web Site, such as EVBAAdmin, any Customer and/or Custodian Manager websites, DAReporting. Then remove any DA Application Pools, such as EVAcceleratorAppPool. If an AppPool cannot be deleted because there are associated applications (under View Applications), Stop the AppPool first, then delete it.

2.4. Open the Registry (Start | regedit). Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\KVS\ and delete the Discovery Accelerator key. Note - Do not delete the key Enterprise Vault Discovery Accelerator if present as this is for a DA Client installation if installed on the DA server for troubleshooting purposes.

2.5. Uninstall the EV Binaries on the DA server. This is best done using the Add or Remove Programs, or the Programs and Features application within the Control Panel. Be sure to uninstall in the correct sequence. Any installed cumulative hotfixes or release updates should be uninstalled before uninstalling the major version.

2.6. Reboot the DA server.

2.7. If the DA installation folder is still present post-reboot, rename the DA installation folder.

2.8. (Optional) Uninstall IIS. Note this is an optional step that should only be done with the agreement or under the direction of Veritas Technical Support. Uninstalling IIS on Windows Server 2016 and higher can uninstall .NET. If uninstalling IIS, please be sure to follow the applicable steps below.

Step 3 - Verify/Install the prerequisites

3.1. Verify the VSA permissions on the MSDB database.

3.1.1. In SQL Server Management Studio, browse to Databases | System Databases | msdb | Security | Users. Verify the VSA is listed. If it exists, proceed to the next step. If not, right-click Users | New User | enter the VSA user name in the Login name box, entering the domain and user name of the VSA in the format of domain\user_name | OK.

3.1.2. Create the EVScheduledSearchOperator role with the required securables in the msdb system database (this role is required to support scheduled searches) and assign the Vault Service Account to the EVScheduledSearchOperator role. Edit DOMAIN\vsa to the VSA credentials in the following query and execute the query in SQL Server Management Studio (SSMS).

USE [MSDB];
GO
IF NOT EXISTS (
SELECT * FROM dbo.sysusers
WHERE Name = N'EVScheduledSearchOperator')
BEGIN;
CREATE ROLE EVScheduledSearchOperator Authorization dbo;
END;
GO
GRANT SELECT ON syscategories TO EVScheduledSearchOperator;
GRANT SELECT ON sysjobhistory TO EVScheduledSearchOperator;
GRANT SELECT ON sysjobs TO EVScheduledSearchOperator;
GRANT SELECT ON sysjobschedules TO EVScheduledSearchOperator;
GRANT SELECT ON sysjobservers TO EVScheduledSearchOperator;
GRANT SELECT ON sysjobsteps TO EVScheduledSearchOperator;
GRANT SELECT ON sysschedules TO EVScheduledSearchOperator;
GRANT EXECUTE ON sp_add_category TO EVScheduledSearchOperator;
GRANT EXECUTE ON sp_add_job TO EVScheduledSearchOperator;
GRANT EXECUTE ON sp_add_jobschedule TO EVScheduledSearchOperator;
GRANT EXECUTE ON sp_add_jobserver TO EVScheduledSearchOperator;
GRANT EXECUTE ON sp_add_jobstep TO EVScheduledSearchOperator;
GRANT EXECUTE ON sp_delete_job TO EVScheduledSearchOperator;
GRANT EXECUTE ON sp_update_job TO EVScheduledSearchOperator;
GRANT EXECUTE ON sp_update_schedule TO EVScheduledSearchOperator;
EXEC sp_addrolemember SQLAgentUserRole, EVScheduledSearchOperator;
EXEC sp_addrolemember [EVScheduledSearchOperator], N'DOMAIN\vsa'; -- Edit VSA credentials here
GO

3.2. Verify Authenticated Users have Full Control permissions to the Temporary ASP.NET Files. Open File Explorer | browse to each of the following locations | right-click the folder | Properties | Security. Verify Authenticated users have Full Control. If it exists, continue to the next step. If not, click Edit | Add Authenticated Users | Select Full Control | Save the changes.
C:\Windows\Temp\
C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\

3.3. Install IIS if it is uninstalled or confirm all prerequisites for IIS have been installed..
3.3.1. Windows Server 2012 and prior:

Ensure the installation of all the required IIS Roles and Features using the following steps.

- Go to Server Management | Roles | Add Roles | Add, if re-installing, or select, if missing, Web Server (IIS) with the following options:
-- Roles:
--- Web Server | Common HTTP Features: Default Document, Directory Browsing, HTTP Errors, Static Content, HTTP Redirection.
--- Web Server | Health and Diagnostics: HTTP Logging, Logging Tools, Request Monitor, Tracing.
--- Web Server | Performance: Static Content Compression.
--- Web Server | Security: Request Filtering, Basic Authentication, IP and Domain Restrictions, URL Authorization, Windows Authentication.
--- Web Server | Application Development: .NET Extensibility 3.X, .NET Extensibility 4.X, ASP, ASP.NET 3.X, ASP.NET 4.X, CGI, ISAPI Extensions, ISAPI Filters.
--- Management Tools | IIS Management Console: all.
--- Management Tools | IIS 6 Management Compatibility: all options.
--- Management Tools | IIS Management Scripts and Tools: all options.
--- Management Tools | Management Service: all options.
-- Features:
--- .NET Framework 3.X Features: all, including HTTP Activation and Non-HTTP Activation.
--- .NET Framework 4.X Features: .NET Framework 4.X, ASP.NET 4.X, WCF Services HTTP Activation, WCF Services Named Pipe Activation, WCF Services TCP Activation, WCF Services TCP Port Sharing.
--- IIS Hostable Web Core.

3.3.2. Windows Server 2016 and newer:

If IIS was not fully uninstalled, follow the steps below using Server Manager on the DA server to verify all the required Roles and Features are installed. If IIS was fully uninstalled, follow the steps below using Server Manager on another server in the environment to reinstall IIS with the required Roles and Features.

To connect to the DA server using Server Manager on another server:

- Start Server Manager on another server.
- Click on Add other servers to manage, or click on Manage | Add Servers.
- Search for the DA server | Add it to the Selected pane | OK.

To connect to Server Manager on the DA server:

- Go to Server Manager.
- Click on Add roles and features.
-- Before you begin: Next.
-- Installation Type: Select installation type: Role-based or feature-based installation | Next.
-- Server Selection: Select a server from the server pool | Select the Accelerator Server | Next.
-- Server Roles: Roles | Web Server (IIS) | Add features that are required for Web Server (IIS) | Select Include management tools (if applicable) | Add Features | Next.
-- Features: Select all .NET Framework options | Select Include management tools (if applicable) for any pop-up panes.
--- Expand .NET Framework 3.X Features | Select all features.
--- Expand .NET Framework 4.X Features | Select all features.
--- Select IIS Hostable Web Core.
--- Next.
-- Web Server Role (IIS): Next.
-- Web Server Role (IIS) | Role Services:
--- Common HTTP Features: Default Document, Directory Browsing, HTTP Errors, Static Content, HTTP Redirection.
--- Health and Diagnostics: HTTP Logging, Logging Tools, Request Monitor, Tracing.
--- Performance: Static Content Compression.
--- Security: Request Filtering, Basic Authentication, IP and Domain Restrictions, URL Authorization, Windows Authentication.
--- Application Development: .NET Extensibility 3.X, .NET Extensibility 4.X, ASP, ASP.NET 3.X, ASP.NET 4.X, CGI, ISAPI Extensions, ISAPI Filters.
--- Management Tools | IIS Management Console.
--- Management Tools | IIS 6 Management Compatibility | Select all.
--- Management Tools | IIS Management Scripts and Tools.
--- Management Tools | Management Service.
--- Next.
- Finish.

3.4. Note: For DA 14.2 and higher:
- Verify the IP and Domain Restrictions role is installed under Web Server (IIS) | Web Server | Security.
- Verify the .NET Core Hosting Bundle 2.2.8 is installed. This can be downloaded here: https://download.visualstudio.microsoft.com/download/pr/ba001109-03c6-45ef-832c-c4dbfdb36e00/e3413f9e47e13f1e4b1b9cf2998bc613/dotnet-hosting-2.2.8-win.exe
- For 14.3 and higher, verify Node.js is installed as required. This can be downloaded here: https://nodejs.org/dist/v14.17.3/node-v14.17.3-x64.msi

Step 4 - Install the EV Binaries (preferred) or EV API using the same version as is installed on the EV server(s).

4.1. Run the EV Server installation for the major version of EV on the DA server.

4.2. At the "Installation complete. The InstallShield Wizard has successfully installed Enterprise Vault. Click Finish to exit the wizard." screen, uncheck the Show configuration information or Show information on configuring installed components box, and then click on Finish.

4.3. Reboot as prompted.

4.4. Repeat to install any applicable cumulative hotfixes or release updates.

Step 5 - Install DA

5.1. Run the DA server installation for the major version of DA.

5.2. Reboot as prompted.

5.3. Repeat to install any applicable cumulative hotfixes or release updates.

Note - Installing the cumulative hotfix or release update for some versions may edit the .config files to list a state of Upgraded instead of Uninstalled (see note below). Additionally, the EVBAAdmin website will list the prompt to upgrade the database but clicking the OK button will have no effect. To avoid this, before installing the cumulative hotfix or release update and when at the base version (major version), connect to the EVBAAdmin website, click on the Use Existing Database option, enter the remaining information for the Configuration database, and save the change. At the The update is complete. Restart the Accelerator Manager Service and then click 'OK' prompt, close the browser, reboot the Accelerator server and then proceed with installing the cumulative hotfix or release update.

5.4. When the installation has completed, connect to the EVBAAdmin website.

5.4.1. Click on the Use Existing Database option.

Note - If this option is not seen, it is usually due to installing the base version and then immediately installing a release update before connecting to the existing Configuration database when at the base version. To remedy this, search for all .config files with the following line: <add key="State" value="Upgraded" />. The number of files will vary from version to version. Edit this line in each of these lines to change the word Upgraded to Uninstalled, as follows: <add key="State" value="Uninstalled" />. Restart the EVAMS and IIS, then connect to the EVBAAdmin website.

5.4.2. Enter the remaining information. The SQL server and Configuration database name can be determined by reviewing the following line from the previous installation's AcceleratorManager.exe.config file - in this example, the SQL server name is SQLserver1 and the Configuration database name is EVDAConfiguration:
<add key="DSNConfiguration" value="server='SQLserver1';Integrated Security=true;Initial Catalog='EVDAConfiguration';Connection Timeout=100;Connection Lifetime=30;Max Pool Size=200" />

5.4.3. If the Configuration database is a member of a SQL Always On Availability Group, enter the Always On listener information.

5.4.4. Click Browse, navigate to the DA License File location, select the DA License File, and click Open.

5.4.5. Verify all settings are correct and save the changes. If the Configuration database is a member of a SQL Always On Availability Group, verify the information before proceeding.

5.4.6. At the The update is complete. Restart the Accelerator Manager Service and then click 'OK' prompt, please be sure to Restart the EVAMS before clicking on the OK button.
If the prompt states The update is complete. Restart the Accelerator Manager Service and Internet Information Service (IIS). Click 'OK' to continue., please be sure to stop the EVAMS, run the iisreset command in an administrative (elevated) command prompt, then start the EVAMS before clicking on the OK button.

5.5. At this point, the EVBAAdmin website should show the previously existing DA Customers. If not, proceed to Step 6.

5.6. Right-click each DA Customer and click on the Check Virtual Directory option to create the required IIS virtual directories.

Step 6 - Add the DA Customers (only perform this step if the DA Customers are not seen in EVBAAdmin)

6.1. Refer to the screenshots and data from Step 1.

6.2. Right-click the DA server and click on New Customer.

6.2.1. Select the Customer Type: Discovery or Custodian. Note: there can only be one Custodian Customer per DA server.

6.2.2. Select the "Use Existing Database" option.

6.2.3. From the screenshots and/or data from Step 1, enter the following for the appropriate DA Customer as previously configured:
- Name
- Directory DNS Aliases
- Administrator User or Group
- Enable Customer's Tasks (checked or unchecked)
- IIS Virtual Directory
- IIS Server
- SQL Server (be sure to use the Always On information if previously configured)
- Database
- Database Location For Analytics
- Note: it is not required to enter a DSN - this will be configured by the system

6.2.4. Click OK to save the customer.

6.3. Click on the DA Customer and monitor the Current Status. Once complete, right-click the DA Customer and click on the Check Virtual Directory option to create the required IIS virtual directories.

6.4. Repeat for any additional DA Customers.

How to uninstall and reinstall Compliance Accelerator, EV Binaries and IIS

Step 1 - Capture the current CA information from the CA server

1.1. Copy the CA License from the \Program Files\Enterprise Vault Business Accelerator\Installed Licenses folder to a safe location. Also review the %ProgramData%\Symantec Shared\Licenses\ (and %ProgramData%\Veritas Shared\Licenses\ for 14.x and higher) folder for any installed licenses.
Note - This is an important step. A valid Accelerator license is required to run Searches, Exports, Random Sampling (CA only), Analytics (DA only), and Legal Holds (DA only with a valid DA license also needed on all EV servers). Without a valid license, the Accelerator Customer will essentially be in read-only mode. For example, items in the Review set can be previewed but cannot be Exported, Searches can be created and submitted but will not run.