Last updated: 09-Jul-2009
This document describes how to upgrade to Enterprise Vault 2007 Service Pack 6 (SP6) from Enterprise Vault 7.0 or later. For the most up-to-date version of this document, see http://entsupport.symantec.com/docs/308964 on the Symantec Enterprise Support site.
If you are upgrading from a version other than Enterprise Vault 2007, the upgrade applies changes to the Enterprise Vault Directory database schema. It is therefore particularly important that you follow the upgrade instructions carefully when upgrading multiple Enterprise Vault servers that access the same Enterprise Vault Directory.
IMPORTANT: If you plan to upgrade to Symantec Enterprise Vault File System Archiving (FSA) 2007 SP6 from a version of Enterprise Vault other than Enterprise Vault 2007, review the important information in http://entsupport.symantec.com/docs/289557 before upgrading.
If you are performing a new installation of Enterprise Vault, see the Enterprise Vault
2007 ReadMeFirst, the most up-to-date
version of which is at http://entsupport.symantec.com/docs/308964. Then follow
the installation instructions in the Enterprise Vault 2007 Installing and
Configuring manual, which is in the Documentation folder on the
Enterprise Vault 2007 SP6 release media.
Note the following before beginning your upgrade.
This document describes upgrading to Enterprise Vault 2007 SP6 from either of the following starting points:
If you are running Enterprise Vault 6.0, you must first upgrade to Enterprise Vault 7.0 before you upgrade to Enterprise Vault 2007 SP6.
Before starting to upgrade your system:
Documentation folder on
Enterprise Vault 2007 SP6 media.For a list of all the Enterprise Vault documentation, see Enterprise Vault documentation in the ReadMeFirst.
For the latest information on supported software and storage devices, see the Enterprise Vault Compatibility Charts at http://entsupport.symantec.com/docs/276547.
To upgrade to Enterprise Vault 2007 SP6:
See http://entsupport.symantec.com/docs/290725 for instructions on applying the hotfix.
Then perform the following additional steps, as required:
See Upgrading Enterprise Vault 7.0 User Extensions to 2007 Outlook Add-Ins.
Note: On upgraded systems, Outlook is still required on all Enterprise Vault servers that host the Enterprise Vault Storage service, even if Exchange Server archiving is not being performed. This is required in order to access items that were archived using earlier versions of Enterprise Vault.
This section describes the preparations for upgrading an existing Domino archiving installation. For details of how to perform a new installation, see Installing and Configuring.
For Domino journal archiving:
For Domino mailbox archiving:
For the latest information on supported versions of Domino software and the required hotfixes, see the Enterprise Vault Compatibility Charts (http://entsupport.symantec.com/docs/276547).
To support Domino journaling or Domino mailbox archiving you must do the following on every Enterprise Vault server:
This change was introduced in Enterprise Vault 2007 SP1. If you are upgrading from Enterprise Vault 2007 SP1 or later then you have already made the change described in this section.
For more information about the NOTESNTSERVICE system environment variable and how to set it, see the following articles:
If you do not set NOTESNTSERVICE there may be many different errors, such as intermittent failures when restoring archived items, errors when archiving, and errors from the Administration Console.
To prepare for upgrading Domino mailbox archiving:
Note: Since you are replacing the Forms8.nsf, Forms7.nsf, and Forms6.nsf files with the original Lotus Domino versions, any additional (non-Enterprise Vault) customizations to these files will be lost. If you have made any additional customizations to Forms8.nsf, Forms7.nsf, or Forms6.nsf, reapply these changes to the files after you have upgraded to Enterprise Vault 2007 SP6.
C:\Lotus\Domino\Data\ev):
If you are upgrading from the original release of Enterprise Vault 2007 (with no service packs applied), then before upgrading any computer on which Enterprise Vault Reporting is installed, delete the Data Analysis Reports folder from Microsoft SQL Server Reporting Services Report Manager as follows:
http://hostname/reportmgr_webapp_name
where:
hostname is the fully qualified host name of the computer hosting
the Report Manager Web application.reportmgr_webbapp_name is the name of the Report Manager Web
application.For example:
http://myserver/Reports/
Symantec Enterprise Vault > language > Data Analysis Reports
where language is the language in which you installed the reports, for example en-us.
This section describes how to upgrade your Enterprise Vault servers (that is, all servers that are running Enterprise Vault services). If you are upgrading an Enterprise Vault 2007 system that supports Domino mailbox archiving, this includes any Enterprise Vault Domino Gateway servers.
This section also describes how to upgrade computers on which Enterprise Vault Reporting is installed.
To upgrade from any version of Enterprise Vault 2007, the process is as follows:
To upgrade from any version of Enterprise Vault 7.0, the process is as follows:
You need to back up your databases and any changed language files.
Before upgrading your Enterprise Vault environment, back up all Enterprise Vault data in accordance with your normal backup procedures. You need to back up all the following:
See https://forums.symantec.com/syment/blog/article?message.uid=354045 for the latest version of Enterprise Vault Backups Best Practise.
The installation procedure will overwrite the files in your Enterprise Vault server
language folders,
Enterprise Vault\Languages\Mailbox Messages\language
where language indicates the language used.
The installation does not modify the live versions of these files that you have in the
Enterprise Vault folder (normally C:\Program Files\Enterprise Vault).
If you have made changes that you want to keep to the files in the language folders, copy the files to another location.
The Deployment Scanner has been updated for Enterprise Vault 2007 SP6.
Before upgrading to Enterprise Vault 2007 SP6, we strongly recommend that you run the Deployment Scanner to check prerequisite software and settings, even if you are upgrading from an existing Enterprise Vault 2007 service pack.
The Deployment Scanner is included in the Deployment Scanner folder on
the Enterprise Vault 2007 SP6 media.
Use the Vault Service account when running the Deployment Scanner.
To install Deployment Scanner, Windows Installer 3.1 must be installed on the Enterprise Vault server computers. You can download Windows Installer 3.1 from the Microsoft Download Center.
For the period you install and configure Enterprise Vault, the Vault Service account must be the database owner of all Enterprise Vault Databases.
If you changed the database owner after Enterprise Vault was installed, you must make the Vault Service account the owner before you upgrade.
This permission is required to enable to allow database schema and other updates to be carried out with appropriate privileges.
If it is not acceptable to make the Vault Service account the database owner of all Enterprise Vault Databases there is a set of minimum permissions you can apply.
See the following TechNote on the Symantec Support Web site: http://entsupport.symantec.com/docs/316189.
To install the Enterprise Vault 2007 SP6 server software:
The Directory service computer referred to in the following instructions is the computer specified on the Connect tab of the Enterprise Vault container properties in the Administration Console.
If you are upgrading Enterprise Vault in a VCS cluster, use VCS cluster administration tools to bring all the Enterprise Vault service resources offline.
If you are upgrading Enterprise Vault in a Microsoft server cluster, use Microsoft
Cluster Administrator or the command line utility cluster to bring the Admin
service resource offline.
Enterprise Vault Administration Console
Enterprise Vault Accelerator Manager service
Enterprise Vault Placeholder service
Enterprise Vault File Blocking service
Enterprise Vault File Collector service
Windows Event Viewer
If you are upgrading Enterprise Vault in a VCS cluster, use VCSVMMCVIEW
–target MSMQ to check the MSMQ queues.
If you are upgrading Enterprise Vault in a Microsoft server cluster, you can use the
command line utility ClusterCompMgmt to check the MSMQ queues. See 'Viewing
the clustered message queues' in the 'Clustering Enterprise Vault with Microsoft server
clusters' section of the Installing and Configuring guide.
If you are upgrading Enterprise Vault in a VCS cluster, use VCS cluster administration tools to bring the Admin service resource offline.
If you are upgrading Enterprise Vault in a Microsoft server cluster, use Microsoft
Cluster Administrator or the command line utility cluster to bring the Admin
service resource offline.
Note: You need to check that all Enterprise Vault services are stopped including, if appropriate, the Compliance Accelerator and the Discovery Accelerator services.
On 32-bit Windows systems:
cluster resource evserver1-EnterpriseVaultAdminService /removecheck:"Software\KVS\Enterprise Vault"
On 64-bit Windows systems:
cluster resource evserver1-EnterpriseVaultAdminService /removecheck:"Wow6432Node\Software\KVS\Enterprise Vault"
where evserver1 is the name of the virtual server.
cluster resource evserver1-EnterpriseVaultAdminService /check
The output looks similar to the following:
Listing registry checkpoints for resource
'evserver1-EnterpriseVaultAdminService'...
Resource Registry Checkpoint
-------------------- ----------------------------------------------
evserver1-EnterpriseVaultAdminService None
On 32-bit Windows systems:
cluster resource evserver1-EnterpriseVaultServerInstance /addcheck:"Software\KVS\Enterprise Vault"
On 64-bit Windows systems:
cluster resource evserver1-EnterpriseVaultServerInstance /addcheck:"Wow6432Node\Software\KVS\Enterprise Vault"
cluster resource evserver1-EnterpriseVaultServerInstance /check
The output looks similar to the following:
Listing registry checkpoints for resource
'evserver1-EnterpriseVaultServerInstance'...
Resource Registry Checkpoint
-------------------- ----------------------------------------------
evserver1-EnterpriseVaultServerInstance 'Software\KVS\Enterprise Vault'
\Enterprise Vault
2007\Server.Setup.exe to start the installation.Note: If a restart is required on the Directory Service computer at the end of the installation then, after the restart, stop all Enterprise Vault services and then restart the Admin and Directory services on the Directory services computer.
Note: If a restart is required at the end of the installation on any of these other servers then, after the restart, stop all Enterprise Vault services and then start only the Admin service.
The Enterprise Vault software installation is now complete, but you must obtain license keys for any additional services that you intend to run.
After the upgrade installation on the Directory service computer, if it is not already running, you must start the Directory service on the Directory service computer:
If you are upgrading Enterprise Vault in a VCS or MSCS cluster, bring the Directory service resource online using the relevant cluster administration tools.
The Directory service has completed the automatic upgrade of the
EnterpriseVaultDirectory Database
You must run the Configuration wizard if you have upgraded from any version of Enterprise Vault 7.0. You do not need to run the Configuration wizard if you are upgrading from the Enterprise Vault 2007 original release or from an Enterprise Vault 2007 service pack.
Note: You need to run the Configuration wizard only once; it is not necessary to run it on all servers. You are recommended to run it on the Directory service computer.
Do the following before you run the Enterprise Vault Configuration wizard:
To run the Configuration wizard:
UpgradeEVServerToV7.5 date.log where date is the date and time when the file was created._EvAzUtil date.log where date is the date and time when the file was created.FSAReportingWebServiceConfigUtility.logThe Configuration wizard may have started some Enterprise Vault services, such as the Task Controller service. You can now start other Enterprise Vault services. If you stopped the IIS Admin service before the installation, start any services that were stopped by this service.
If the Configuration wizard warned you that there was an error configuring the Monitoring database, you must configure the database manually.
To do this, see the following TechNote on the Symantec Support Web site: http://entsupport.symantec.com/docs/287449.
Note: This section does not apply if you have upgraded from any version of Enterprise Vault 2007.
If the Enterprise Vault Operations Manager component is installed on any server, you must run the Operations Manager Configuration utility on that server.
Do not run the Operations Manager Configuration utility until you have successfully run the Enterprise Vault Configuration wizard on the Directory service computer in your Enterprise Vault system.
To run the Operations Manager Configuration utility:
Perform the above procedure on each server on which the Operations Manager component is installed.
Note: This step is required regardless of which version of Enterprise Vault you have upgraded from.
If the Enterprise Vault Reporting component is installed on any computer, you must run the Reporting Configuration utility on that computer.
If you are upgrading from any version of Enterprise Vault 7.0, do not run the Reporting Configuration utility until you have successfully run the Enterprise Vault configuration wizard on the Directory service computer in your Enterprise Vault system.
To run the Reporting Configuration utility:
Perform the above procedure on each server on which the Enterprise Vault Reporting component is installed.
If the Reporting Configuration utility indicated that there was an error deploying Enterprise Vault reports, see the following TechNote on the Symantec Support Web site: http://entsupport.symantec.com/docs/288139.
Work through this section if you are upgrading Domino mailbox archiving.
To upgrade Domino mailbox archiving:
EVInstall.nsf with the ID of the
user that will be used to run Symantec Enterprise Vault 2007 - Domino Installer
(EVInstall.nsf).EVInstall.nsf.
Note: In order to run EVInstall.nsf you must use the correct Notes client version, as follows:
The application takes several minutes to create the new Enterprise Vault templates.
To run the Designer task, enter the appropriate command in the server console, as follows:
load design -f EVDG_DWA7.ntf
load design -f EV_DWA7.ntf
load design -f EV_iNotes6.ntf
EVInstall.nsf against a Domino Server 7.0.2 target server, deploy the
templates to all Domino Server 7.0.2 mail servers.
Deploy the templates by creating replicas of the Enterprise Vault mail templates and
running Load Design on each mail server.
(It is important that you copy the templates created on the Domino mail server and not those created on the Enterprise Vault Domino Gateway).
Load Design as before, on each mail server.
Note that this command updates all databases on the server. It may be quicker to
restrict the scope of the command so that it updates just those databases that need
changing. In this case, use the Load Design -f switch to update all
Enterprise Vault mail databases that have had any of the following templates applied to
them:
Follow the procedure below if you ran the Configuration wizard and it warned you that there was an error updating the DCOM settings of Enterprise Vault servers. If there was no such warning you can ignore this section.
To update the DCOM settings:
If you have upgraded from Enterprise Vault 2007 you do not need to perform this step.
After upgrading to Enterprise Vault 2007 SP6, add the new Microsoft Office 2007 files to the FSA file group, Office Files, as follows:
On a new Enterprise Vault 2007 SP6 installation, this manual step is not required, as these file types are added automatically.
Enterprise Vault 2007 server requires a cache location to be used when retrieving from Celerra devices. You must define a cache location as described in the File System Archiving chapter in the Administrator's Guide.
If you were using an EMC Celerra device before upgrading to Enterprise Vault 2007 SP6, you must make configuration changes before you can use placeholder shortcuts on the Celerra.
For more information, see the support note at http://entsupport.symantec.com/docs/285860.
Note: Perform these steps only if you applied SP6 to a system running the Enterprise Vault 2007 original release (with no service packs applied), and on which FSA Reporting was configured.
These steps assume that you applied the FSA Reporting .com hotfix before upgrading to SP6, as described in Steps to upgrade your system.
To upgrade the Exchange Server forms, note the points below and then follow the instructions in the Distributing Exchange Server Forms chapter of the Installing and Configuring guide.
Note the following:
You must upgrade the FSA Agent on the NTFS file servers on which it is installed. You can do this by using the Install FSA Agent wizard, or manually.
To use the Install FSA Agent wizard on Windows Server 2008, you must temporarily turn off User Account Control (UAC) and the Windows Firewall on the target file servers. If you prefer not to do this, install the FSA Agent manually.
To configure an FSA cluster for a Windows Server 2008 file server that uses Microsoft server clustering (MSCS), you must run the Enterprise Vault Administration Console on a Windows Server 2008 computer.
To upgrade the FSA Agent using the 'Install FSA Agent' wizard:
To install the FSA Agent manually:
This section describes how you upgrade older versions of the Enterprise Vault OWA and RPC Extensions to Enterprise Vault 2007 SP6.
You must upgrade the Enterprise Vault OWA and RPC Extensions on each OWA and RPC server in your Enterprise Vault environment.
Follow the appropriate instructions for your system:
Note the following if your Exchange Servers are clustered in a VCS or Microsoft server cluster.
When upgrading Enterprise Vault OWA 2003 or OWA 2000 extensions on back-end Exchange Servers that are clustered using VCS, note the following steps:
When upgrading Enterprise Vault OWA 2003 or OWA 2000 extensions on back-end Exchange Servers that are clustered using Microsoft server clusters, note the following steps:
This procedure is only applicable if you are upgrading an Enterprise Vault 2007 system that uses the OWA 2007 extensions.
Enterprise Vault 2007 folder.OWA 2007 Extensions folder.EV_OWA2007_Extensions_x64.msiEV_OWA2007_Extensions_x86.msiNote: Exchange Server 2003 hotfixes may modify OWA control files. If you have installed an Exchange Server 2003 hotfix that has created an unsupported version of the OWA control files folder, or modified any files in the control files folder, a Save file error will be reported when you attempt to install the Enterprise Vault OWA Extensions.
For details of the versions of OWA 2003 control files supported by the Enterprise Vault 2007 OWA Extensions, see the Enterprise Vault Compatibility Charts (http://entsupport.symantec.com/docs/276547).
You do not need to completely remove the extensions using Add/Remove Programs in the Control Panel.
If your Exchange Servers are clustered, there is additional information that you need to read before proceeding.
See Upgrading OWA extensions in a clustered environment.
For installation instructions, see OWA 2003: Installing Enterprise Vault back-end OWA Extensions.
This recreates the Enterprise Vault virtual directories.
See OWA 2003: Configuring OWA Extensions on a back-end Exchange Server.
You do not need to completely remove the extensions using Add/Remove Programs in the Control Panel.
See OWA 2003: Installing Enterprise Vault front-end OWA Extensions.
See OWA 2003: Configuring OWA Extensions on a front-end Exchange Server.
To remove the virtual directories, form registrations and Proxy Bypass List that are created by the Enterprise Vault OWA Extensions configuration wizard, run the following Enterprise Vault scripts from the command line.
On front-end OWA 2003 Servers:
C:\Program Files\Enterprise Vault\OWA>cscript FrontEnd2003Setup.wsf
/removeThis deletes the virtual directory, EnterpriseVaultProxy, and the Proxy Bypass List.
On back-end OWA 2003 Servers, run the following command. In an active/passive OWA 2003 cluster, run this command on the active node first, and then run it on the passive node.
C:\Program Files\Enterprise Vault\OWA>cscript Backend2003Setup.wsf
/removeThis deletes all the Enterprise Vault OWA virtual directories (EnterpriseVaultProxy, EnterpriseVaultPublic, EnterpriseVaultExchange, EVOWA), forms registrations and Proxy Bypass List.
C:\Program Files\Exchsrvr\exchweb \6.5.nnnn.n\Controls-originals copied by Enterprise
Vault
C:\Program Files\Exchsrvr\exchweb\6.5.nnnn.n\ControlsC:\Program
Files\Exchsrvr\exchweb\6.5.nnnn.n \Controls-originals copied by Enterprise
Vault.Enterprise Vault 2007 folder.Server folder.Setup.exe to start the installation.After you have installed the OWA Extensions on back-end Exchange Server 2003 computers, configure the OWA Extensions, as described in this section.
The configuration wizard uses entries in the EVServers.txt file to
create WinHTTP proxy bypass entries for each Exchange server that will connect to the
Enterprise Vault server. Ensure that the entries in this file are correct for your
system. For details of this file, see the Installing
and Configuring guide.
Create at least one public folder before you run the configuration wizard. As Microsoft Exchange installation automatically creates a public folder store, Enterprise Vault will attempt to register forms against public folders.
Press ENTER to end
Enterprise Vault\OWA\BackEnd2003Setup.wsf.logCheck the log file for any configuration errors.
Enterprise Vault 2007 folder.Server folder.Setup.exe to start the installation.After you have installed the OWA Extensions on a front-end Exchange Server 2003 computer, you need to configure the extensions, as described in this section.
Press ENTER to end
Enterprise
Vault\OWA\FrontEnd2003Setup.wsf.log. Check the log file for any configuration
errors.This completes the basic configuration of your Enterprise Vault OWA environment.
If required, the functionality available to OWA 2003 users can be customized by administrators using the Enterprise Vault Administration Console; select OWA settings on the Advanced tab of the appropriate Exchange Server mailbox policy. These settings are described in the Administrator's Guide.
The OWA computer (back end) requires either Windows 2000 SP3 or a Microsoft hotfix because of a problem with IIS 5.0. The problem is described in Microsoft support article 294833. Prior to the release of Windows 2000 SP3 there was a Microsoft hotfix to correct this problem. If you do not want to install Windows 2000 SP3 you may be able to obtain a copy of the hotfix.
Note that the new OWA client functionality available in Enterprise Vault 2007 OWA Extensions is only available when using OWA 2003 clients with Exchange Server 2003.
See OWA 2000: Removing existing OWA extensions.
You do not need to completely remove the extensions using Add/Remove Programs in the Control Panel.
If your Exchange Servers are clustered, there is additional information that you need to read before proceeding.
See Upgrading OWA extensions in a clustered environment.
For installation instructions, see OWA 2000: Installing Enterprise Vault back-end OWA Extensions.
See OWA 2000: Configuring OWA Extensions on a back-end Exchange Server.
See OWA 2000: Installing Enterprise Vault front-end OWA Extensions.
To remove the virtual directories, form registrations, and Proxy Bypass List that are created by the Enterprise Vault OWA Extensions configuration wizard, you need to run the following Enterprise Vault scripts from the command line.
On back-end OWA 2000 Servers, run the following command. In an active/passive OWA 2000 cluster, run this command on the active node first, and then run it on the passive node.
C:\Program
Files\Enterprise Vault\OWA>cscript Backend2000Setup.wsf /remove.As the OWA Extensions are installed but not configured on front-end OWA 2000 Servers, you do not need to run a removal script on these servers.
Enterprise Vault 2007 folder.Server folder.Setup.exe to start the installation.After you have installed the OWA Extensions on back-end Exchange Server 2000 computers, configure the OWA Extensions, as described in this section.
The configuration wizard uses entries in the EVServers.txt file to
create WinHTTP proxy bypass entries for each Exchange server that will connect to the
Enterprise Vault server. Ensure that the entries in this file are correct for your
system. For details of this file, see the Installing
and Configuring guide.
Create at least one public folder before you run the configuration wizard. As Microsoft Exchange installation automatically creates a public folder store, Enterprise Vault will attempt to register forms against public folders.
Press ENTER to end
Enterprise
Vault\OWA\BackEnd2000Setup.wsf.log. Check the log file for any configuration
errors.Enterprise Vault 2007 folder.Server folder.Setup.exe to start the installation.Note: You do not need to configure front-end OWA 2000 Extensions.
This completes the upgrade process for your Enterprise Vault OWA 2000 extensions.
We recommend that you upgrade the Enterprise Vault SharePoint components and Archive Search Web Part on each of your SharePoint Server computers.
To upgrade the Enterprise Vault SharePoint components:
To upgrade the Archive Search Web Parts:
If the language selected for your SharePoint installation is not English, copy the Web
Part package EV_SharepointWebPartsCab.cab from the appropriate language folder
under C:\Program Files\Enterprise Vault\Languages\Windows SharePoint Services Web
Parts to the folder containing the Stsadm.exe tool, which is typically:
C:\Program Files\Common Files\Microsoft Shared\Web Server
Extensions\nn\BIN
where nn is 60 for Windows SharePoint Services 2.0
and SharePoint Portal Server 2003, and 12 for Windows SharePoint Services
3.0 and Office SharePoint Server 2007.
C:\Program Files\Common Files\Microsoft Shared\Web Server
Extensions\nn\BIN
where nn is 60 for Windows SharePoint Services 2.0
and SharePoint Portal Server 2003, and 12 for Windows SharePoint Services
3.0 and Office SharePoint Server 2007.
stsadm.exe -o addwppack -globalinstall -force -filename "ev_sharepointwebpartscab.cab"
You need to reinstall the archived version history link. Failure to do this after an upgrade will result in an error when attempting to view the archived version history.
http://spcomputername/_layouts/versionsadmin.aspx
where spcomputername is the name of your SharePoint server
computer.
Note that you only need to perform this task once for all of the SharePoint virtual servers on a computer.
This section covers upgrading the Enterprise Vault 7.0 User Extensions (Full and Lite clients) and Self-Installing User Extensions, which have been renamed in Enterprise Vault 2007 as the Outlook Add-Ins, HTTP-only Outlook Add-Ins, and HTTP-only Self-Installing Outlook Add-Ins, as described in the ReadMeFirst.
For information on which Enterprise Vault client versions work with which Enterprise Vault server versions, see the Enterprise Vault Compatibility Charts at http://entsupport.symantec.com/docs/276547.
Use the same type of Enterprise Vault user extensions when upgrading:
If you want to upgrade from one type of Enterprise Vault client extensions to another (for example, from Enterprise Vault Outlook Add-In to HTTP-only Outlook Add-In), additional steps are required. For details, see the support note http://entsupport.symantec.com/docs/289949.
If you are upgrading either type of user extensions, we recommend you also upgrade the Exchange Server forms.
Follow the relevant instructions for your system:
For information on how to distribute the new Outlook Add-Ins, see Outlook Add-Ins in the Setting up users' desktops chapter of the Installing and Configuring guide.
If you have users of the self-installing User Extensions, you need to make the new version (HTTP-only Self-Installing Outlook Add-Ins) available to users. Users will then be automatically given the option to install the new version when they click Enterprise Vault shortcuts.
To upgrade to the HTTP-only Self-Installing User Extensions, see Making the HTTP-only Self-Installing Outlook Add-In available in the Setting up users' desktops chapter of the Installing and Configuring manual.
Note: The installation process for the HTTP-only Self-Installing Outlook Add-Ins currently prompts you to restart your computer before the installation complete page is displayed. If you click Yes on the restart prompt, the End Program dialog is displayed for Outlook. This dialog is displayed because Windows is trying to shut down Outlook but the installer is trying to open the installation complete page. You can safely ignore the End Program dialog and click No on the Do you want to save changes? prompt. End users will also encounter this, so you may want to warn them of this behavior. See Upgrading HTTP-only Self-Installing Outlook Add-Ins in the ReadMeFirst.
If necessary, publish the Outlook Add-Ins in Active Directory. The new package will then be installed when each user's computer is restarted. Follow the instructions in Publishing the Add-Ins in Active Directory in the Setting up users' desktops chapter of the Installing and Configuring guide.
Copyright © 2009 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, Veritas, and Enterprise Vault are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This Symantec product contains third party software for which Symantec is required to provide attribution to the third party (“Third Party Programs”). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Please see the Third Party Software file accompanying this Symantec product for more information on the Third Party Programs.
The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.
Symantec Corporation
350 Ellis Street
Mountain View, CA 94043