Enterprise Vault™ Upgrade Instructions
- About this guide
- Before you begin
- Points to note when upgrading
- Installing Outlook on the Enterprise Vault server
- Improved consistency when applying a retention period to items
- Additional points to note when upgrading from Enterprise Vault 11.0 or 11.0.1
- Steps to upgrade your system
- Enterprise Vault server preparation
- Backing up the system
- Single server: upgrading the Enterprise Vault server software
- Multiple servers: upgrading the Enterprise Vault server software
- Veritas Cluster Server: upgrading the Enterprise Vault server software
- Windows Server Failover Clustering: upgrading the Enterprise Vault server software
- Upgrading standalone Administration Consoles
- Upgrading Enterprise Vault Reporting
- Upgrading MOM and SCOM
- Upgrading Exchange Server forms
- Upgrading Domino mailbox archiving
- Upgrading the FSA Agent
- Upgrading Enterprise Vault Office Mail App
- Upgrading OWA Extensions
- Upgrading SharePoint Server components
- Upgrading SMTP archiving
- Checking the SMTP journaling type configuration
- Upgrading your Enterprise Vault sites to use Enterprise Vault Search
- Setting up provisioning groups for Enterprise Vault Search
- Configuring user browsers for Enterprise Vault Search
- Setting up Enterprise Vault Search Mobile edition
- Carrying out preinstallation tasks for Enterprise Vault Search Mobile edition
- Upgrading Enterprise Vault API applications
Securing Enterprise Vault web applications
The Enterprise Vault web applications are configured in the Default Web Site in IIS. By default in a new installation of Enterprise Vault 12.3 or later, Enterprise Vault configures HTTPS on port 443, and enables SSL on each Enterprise Vault virtual directory.
When you upgrade from a version that is earlier than Enterprise Vault 12.3, the existing configuration of the Default Web Site and Enterprise Vault virtual directories remains unchanged. To ensure the security of connections to Enterprise Vault web applications, we strongly recommend that you manually configure an HTTPS binding on the Default Web Site, and enable SSL on the Enterprise Vault virtual directories. The procedure below explains how to do this.
The port and protocol that clients use to access the
EnterpriseVault virtual directory is displayed on the tab of site properties in the Enterprise Vault Administration Console. Before you change this setting, you must first make the required changes to the Default Web Site in IIS for each server in the Enterprise Vault site.
If you change the port or protocol setting in site properties after items have been archived, existing shortcuts will no longer work. Shortcuts in Outlook and Notes can be updated with the new protocol or port information by synchronizing mailboxes in the Enterprise Vault Administration Console, but customized shortcuts, FSA shortcuts and SharePoint shortcuts cannot be updated.
To create a certificate request, and implement SSL in IIS
- Create and submit an SSL certificate request to a trusted certificate authority. Your certificate must include both the short names and fully qualified domain names of the Vault Site alias (that is, the DNS alias for the Enterprise Vault site). For example, EVServer1 and EVServer1.domain.com.
You can use any suitable tool to request the certificate. For example, you can use OpenSSL, which is installed in the Enterprise Vault installation folder. How to create a certificate request using Microsoft Management Console (MMC) is described in the document, https://www.veritas.com/docs/100038186.
- On the Enterprise Vault server, perform the following steps in IIS Manager:
Use the Server Certificates feature to install the new certificate.
In the site bindings for the Default Web Site, add a binding for the HTTPS protocol and link it to the new certificate. Bear in mind, if you change the protocol or port for the Default Web Site, it will affect all virtual directories in the website.
In the SSL Settings pane for each Enterprise Vault virtual directory, select Require SSL.
These tasks are also described in the document, https://www.veritas.com/docs/100038186.
- When you have made the necessary changes in IIS, change the port or protocol setting on the General tab of site properties in the Enterprise Vault Administration Console.