Enterprise Vault. For Microsoft Exchange Server. Installing and Configuring Version 5.0

Transcription

1 Enterprise Vault For Microsoft Exchange Server Installing and Configuring Version 5.0

2 March 2005 This publication and the software it describes are the intellectual property of kvault Software Ltd (KVS). Possession, use, disclosure or copying of this publication or the described software, in whole or part, is allowed only under the terms of a valid KVS Software Licence Agreement or KVS Training and Consultancy Agreement. While kvault Software Ltd believes the information included in this publication is correct as of the date of publication, it is subject to change without notice. kvault Software Ltd makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Copyright 2002, 2005 kvault Software Ltd Trademarks KVS is a business unit of VERITAS Software AltaVista is a registered trademark of AltaVista Company. Adobe is a trademark of Adobe Systems Incorporated. EMC is a registered trademark and Centera is a trademark of EMC Corporation Microsoft SQL Server, and Windows 95 are trademarks and Microsoft, Windows, Windows NT, and Active Directory are registered trademarks of Microsoft Corporation. Netscape is a registered trademark of Netscape Communications Corporation. Outside In is a registered trademark of Stellent Inc. QuickTime is a trademark of Apple Computer, Inc. RealPlayer is a trademark of Real Networks, Inc. Enterprise Vault is a registered trademark of kvault Software Ltd at the US Patent and Trademark Office All other trademarks and registered trademarks are the property of their respective owners. Enterprise Vault uses the ZLIB compression library which is Jean-Loup Gailly and Mark Adler. Enterprise Vault includes the following components that are covered by end-user license agreements for Microsoft Software: Microsoft Data Access Components; Microsoft Management Console; Microsoft Active Template Library; DCOM for Windows 95; HTML Help. The end-user licence agreements for these components are included in the Enterprise Vault kit in the file EULAS.TXT. Please read the terms and conditions of these agreements before using the software.

3 Contents About the documentation About this book Enterprise Vault documentation Terms used in this book Conventions Before installing Operating system requirements Basic hardware requirements Storage requirements Disk space requirements Installation order Notes on Windows Server 2003 and Windows 2000 installation Installing MSMQ MSMQ settings when Enterprise Vault is on Active Directory controller Configuring.NET Framework and Active Server Pages on Windows Server Allowing HTML items larger than 4MB to be downloaded Installing Outlook 2000 on the Enterprise Vault computer Exchange System Manager on Enterprise Vault servers Configuring Application Pool accounts The Vault Service account The Vault Site alias The service mailbox MSXML Requirement for Enterprise Vault servers MSXML for Windows NT MSXML for Windows Server 2003 and Windows Requirements for the Enterprise Vault OWA Extensions Requirements for users computers User Extensions for Outlook What next?

4 Preinstallation tasks on Windows NT Creating the Vault Service account Assigning Microsoft Exchange Server permissions Creating a SQL login Setting up MSMQ Configuring Microsoft Message Queue security Creating the Vault Site alias What next? Preinstallation tasks on Windows Server 2003 and Windows 2000 Creating the Vault Service account Assigning Microsoft Exchange Server permissions On Microsoft Exchange Server 2003: On Microsoft Exchange 2000 Server: Creating a SQL login Creating the Vault Site alias What next? Installing Enterprise Vault Server installation What next? Postinstallation tasks on Windows NT Setting up security for the Web Access application Setting up the default authentication Customizing security for the Web Access application Using a default domain with basic authentication Setting up a default domain in IIS Setting up a default domain in the Web Access application Customizing security on the client computers Using the proxy bypass list Explicitly naming the Web Access application computer Enabling remote access to the Web Access application computer Distributing the Microsoft Exchange forms Creating a folder

5 Installing the forms Customizing users desktop settings and security Japanese fonts What next? Postinstallation tasks on Windows Server 2003 and Windows 2000 Setting up security for the Web Access application Setting up the default authentication Customizing security for the Web Access application Using a default domain with basic authentication Setting up a default domain in IIS Setting up a default domain in the Web Access application Customizing security on the client computers Using the proxy bypass list Explicitly naming the Web Access application computer Enabling remote access to the Web Access Application computer Distributing the Microsoft Exchange forms Creating a folder Installing the forms Customizing users desktop settings and security Japanese fonts What next? Running the Configuration Program Introduction Preparation Running the Configuration Program What next? Installing and configuring the OWA Extensions Planning the OWA Extensions Installing Enterprise Vault OWA Extensions Configuring the OWA Extensions Configuring back-end Exchange servers Configuring front-end Exchange servers

6 6 Configuring OWA on the Enterprise Vault server Configuring WinHTTP for OWA Direct access, without a proxy HTTP server Using a proxy HTTP server WinHTTP configuration problems Links for more information on Proxycfg Running the Administration Console Preparation Introduction Starting the Administration Console Adding services Adding an Indexing Service Adding a Storage Service Adding a Shopping Service Creating Retention Categories Additional configuration tasks Reviewing Site settings Supporting secure web server connections What next? Setting up archiving from mailboxes Adding an Archiving Service Adding a Retrieval Service Reviewing Site settings Mailbox rules Mailbox actions Shortcut options Defining custom shortcut content Layout of ShortcutText.txt Controlling the appearance of desktops Creating Retention Categories Creating a vault store Editing the Welcome message Editing the PST migration message Editing Archive usage limit messages Enabling mailboxes for archiving

7 Installing the User Extensions on a server Users tasks What next? Setting up users desktops Introduction User Extension kits User Extensions Self-installing User Extensions Distributing the User Extensions Sending a shortcut Performing a silent installation Distributing the User Extensions using SMS Making the Self-Installing User Extensions available Copying the files Editing the archived item form Testing the edited form Publishing the edited form Publishing in Active Directory Preparation Publishing Outlook Getting users started Documentation What next? Setting up archiving from public folders Adding a Public Folder Service Configuring the new Public Folder Service Creating Retention Categories Editing the message class list Controlling public folder archiving Applying archiving settings to public folders Scheduling the Public Folder Service

8 Setting up archiving of journaled messages Preparation Creating a vault store Creating an archive Adding a Journaling Service Configuring the Journaling Service What next? Setting up file system archiving Introduction Installing the File Placeholder Service Configuring the File Placeholder Service Setting file permissions Editing the configuration file What Next? Tips Licenses and license keys Overview Obtaining license keys Installing license keys What next?

9 About the documentation About this book What it does This book gives an introduction to KVS Enterprise Vault. This edition of Enterprise Vault is for Microsoft Exchange Server. This book explains how to install and configure Enterprise Vault for Microsoft Exchange Server. Structure How to use it Prerequisite knowledge Read this book through sequentially, section by section. You should have a working knowledge of Microsoft Exchange Server and the administrative tasks in Windows Server 2003, Windows 2000 or Windows NT. You should also have an understanding of Microsoft SQL Server. It will also help you to be familiar with Microsoft Message Queue Server (MSMQ), Microsoft Outlook, and IIS. Available online This book is available online in PDF format in the EVBook.pdf file in the Enterprise Vault Program folder. You can view this book online with the Adobe Acrobat Reader, which you can install from the Enterprise Vault CD-ROM. 9

10 Enterprise Vault documentation Enterprise Vault documentation If you need to install Acrobat Reader, there is a copy on the Enterprise Vault CD-ROM, in the Redistributable Software folder. The Enterprise Vault documentation is provided in the Documentation folder on the CD-ROM and, after installation, in the Administration Console help and the in the Enterprise Vault installation folder. Table 1 lists the documentation that is supplied. Before you install Enterprise Vault you can also display all the documentation by double-clicking the Admin Documentation link in the top-level folder of the Enterprise Vault CD-ROM. Table 1 Enterprise Vault documentation Item ReadMeFirst Administration ReadMe Introduction and Planning for Enterprise Vault for Microsoft Exchange Installing and Configuring for Enterprise Vault for Microsoft Exchange (this book) Administrator s Guide for Enterprise Vault for Microsoft SharePoint Portal Server Formats ReadMeFirst.htm in Enterprise Vault program folder In the Administration Console help EVPlanExchange.pdf EVPlanExchange.chm In the Administration Console help EVConfigExchange.pdf EVConfigExchange.chm In the Administration Console help EVSPS.pdf EVSPS.chm In the Administration Console help Additional documentation The Enterprise Vault Operations Guide, which is available to KVS customers, discusses backup procedures, database maintenance, and disaster recovery 10 About the documentation

11 Terms used in this book in detail. The Operations Guide is available from the customer support web site. Web page There is an Enterprise Vault web page at: Terms used in this book Consult this for the latest information about Enterprise Vault. Within this book, the following terms are used. Term Enterprise Vault A Microsoft Exchange Server computer You User Meaning Short form of the product name, KVS Enterprise Vault for Microsoft Exchange Server. Refers to a server computer running Microsoft Exchange Server. Applies to the Enterprise Vault administrator. Applies to anyone who is using Enterprise Vault to archive items from Microsoft Outlook. About the documentation 11

12 Conventions Conventions Within this book, the following conventions are used: Convention Planning Decision Meaning Indicates that you need to make a planning decision. This typeface This typeface Indicates a new term, or emphasizes a term. Indicates screen text or instructions, for example, Click OK. 12 About the documentation

13 Getting Started with Enterprise Vault This part describes the tasks that you need to do to install and set up Enterprise Vault so that your users can start to use Enterprise Vault. There are eight chapters in this part: Before installing This chapter lists the prerequisites needed to install Enterprise Vault and the preinstallation tasks that you must do before installing Enterprise Vault. Preinstallation tasks on Windows NT This chapter describes tasks that you must carry out on Windows NT before you can install Enterprise Vault. Preinstallation tasks on Windows Server 2003 and Windows 2000 This chapter describes tasks that you must carry out on Windows Server 2003 and Windows 2000 before you can install Enterprise Vault. Installing Enterprise Vault This chapter describes how to install Enterprise Vault. Postinstallation tasks on Windows NT This chapter describes tasks that you must carry out on Windows NT after you have completed the 13

14 installation. Postinstallation tasks on Windows Server 2003 and Windows 2000 This chapter describes tasks that you must carry out on Windows Server 2003 and Windows 2000 after you have completed the installation. Running the Configuration Program This chapter describes how to set up Enterprise Vault. Licenses and license keys This chapter describes how to obtain and install Enterprise Vault license keys. 14

15 Before installing Read this chapter to find out: The prerequisites needed before you can install Enterprise Vault: Operating system requirements Requirements for users computers Disk space requirements Operating system requirements The order in which to install pre-requisite software before installing Enterprise Vault For full details of all the supported versions of prerequisite software, see the Enterprise Vault Certification Tables in the Customer Support Knowledge Base. Not all the components of Enterprise Vault can be installed on all types of operating system, as follows: You can install all the components of Enterprise Vault on Windows Server 2003 Standard Edition Windows Server 2003 Enterprise Edition Windows 2000 Server Windows 2000 Advanced Server Windows 2000 Datacenter Server 15

16 Basic hardware requirements Windows NT Server: Basic hardware requirements On Windows XP Professional, Windows 2000 Professional or Windows NT Workstation you can install: Administration Console User Extensions Microsoft Exchange Forms On Windows 95, Windows 98 or Windows Millennium Edition you can install: User Extensions Microsoft Exchange Forms Note that Enterprise Vault Archive Explorer feature requires that the Enterprise Vault server is running Windows 2000 or later. To install Enterprise Vault, a computer with TCP/IP installed and configured is required. The computer must have a registered IP address with DNS (Domain Name System) properties for the TCP/IP protocol set up. The minimum physical memory required for Enterprise Vault servers running a production system is 512MB. If performance is not an issue, it is possible to run demonstrations using less memory. Note that systems with less than 512MB of memory must be configured to have at least 512MB of page file space. Enterprise Vault requires access to a SQL server and, for mailbox archiving, an Exchange server. In most configurations, Enterprise Vault, SQL server and Exchange server will each be installed on separate computers. However, for pilot or demonstration configurations, some or all of the servers can be installed on the same computer. 16 Before installing

17 Storage requirements Disk space requirements Storage requirements You are not restricted to any particular storage product for use with Enterprise Vault. Enterprise Vault is designed to operate with various types of storage solution provided by third party software and hardware products. Archived data can be directed to: An NTFS volume A Network Share that appears on the network as an NTFS volume An EMC Centera device A NetApp SnapLock (WORM) device Data may in turn be migrated to secondary and tertiary storage systems that are managed by third party hierarchical storage management (HSM) software, for example. During installation you will require 70MB of disk space to install all the Enterprise Vault components. After installation you will need disk space to accommodate the following data: The Vault Directory Database The Vault Directory database requires 10MB for the data device and 25MB for the Transaction log device, making a total disk space requirement of 35MB. This space is required on the Vault Directory computer. The vault store databases Each vault store database requires 100MB for the data device and 80MB for the Transaction log device, making a total disk space requirement of 180MB for each vault store database. Before installing 17

18 Installation order Installation order This space is required on the Storage Service computer. The vault stores This space is required on the Storage Service computer. The indexes This space is required on the Indexing Service computer. The shopping baskets This space is required on the Shopping Service computer The order in which you install prerequisite software sometimes causes problems. The general rule is that it is best to install products in the order in which they were released. Table 2, Table 3, Table 4, and Table 5 show examples of the installation order when you are setting up different Enterprise Vault installations. In the following tables, it is assumed that Enterprise Vault, SQL server and Exchange server are installed on separate computers. Notes are included to cover pilot or demonstration configurations, where some or all of the servers are installed on the same computer. Table 2 Typical installation order for an Enterprise Vault server system on Windows NT Step Software to install Notes 1 Windows NT 4 Server 2 Windows NT 4 Service Pack 6a Also any required hardware drivers 18 Before installing

19 Installation order Table 2 Typical installation order for an Enterprise Vault server system on Windows NT Step Software to install Notes 3 Internet Explorer 4.01 Service Pack 1 4 Outlook 2000 with CDO components Needed if the computer does not have Exchange Server installed 5 Exchange Server 5.5 If required for a demonstration. Enterprise Vault services are usually installed remotely from Microsoft Exchange Server. 6 SQL Server 7 or SQL Server SQL Server 7 Service Pack 1 if you installed SQL Server 7 in step 6 This must be a case-insensitive SQL installation. Case-sensitive SQL installations are not supported. You must register your SQL Server and start the SQL services (SQLServer Agent and MSSQLServer) before configuring Enterprise Vault. 8 Windows NT Options Pack For IIS and MSMQ. If the Storage Service computer is not going to run the Web Access application, then IIS must be installed on the Storage Service computer. 9 Windows NT 4 Service Pack 6a 10 Exchange Server 5.5 Service Pack 3 Reapply the service pack. If required. 11 Message Queue Hotfix The problem that this hotfix corrects is described in Microsoft Knowledge Base article Before installing 19

20 Installation order Table 2 Typical installation order for an Enterprise Vault server system on Windows NT Step Software to install Notes 12 MDAC 2.6 Supplied in the Redistributable Software folder on the Enterprise Vault CD-ROM. Double-click mdac_nts.exe to install the components. Note that this is a later version than the version that is provided with the NT Option Pack. 13 MSXML Supplied in the Redistributable Software folder on the Enterprise Vault CD-ROM. Alternatively, install Internet Explorer 6, which includes MSXML. Table 3 Typical installation order for a standalone Administration Console on Windows NT Step Software to install Notes 1 Windows NT4 Workstation 2 Windows NT4 Service Pack 6a 3 Internet Explorer 4.01 Service Pack 1 4 MMC Outlook 2000 With CDO components. 6 Windows NT4 Service Pack 6a 7 Microsoft Data Access Components (MDAC) Version 2.6. Supplied in the Redistributable Software folder on the Enterprise Vault CD-ROM. 20 Before installing

21 Installation order Table 4 Typical installation order for an Enterprise Vault server system on Windows Server 2003 and Windows 2000 communicating with Exchange Server 2003 or Exchange 2000 Server Step Software to install Notes 1 Windows Server 2003 or Windows 2000 (with Service pack 3) Any suitable version: Windows Server 2003 Standard Edition or Enterprise Edition. Windows 2000 Server or Windows 2000 Advanced Server or Windows 2000 DataCenter Server. Notes on Windows Server 2003 and Windows 2000 installation on page 25 3 Outlook 2000 Also needs CDO components if the computer will not have Exchange Server installed. Installing Outlook 2000 on the Enterprise Vault computer on page 30 4 SQL Server 2000 or SQL Server 7 (SQL server will usually be installed on a separate computer) Note if both Enterprise Vault and SQL server are installed on the same Windows Server 2003 computer, you will need at least SQL Server 2000 with Service Pack 3. Enterprise Vault works with Windows Authentication mode and with Mixed Mode Authentication. This must be a case-insensitive SQL installation. Case-sensitive SQL installations are not supported. Before installing 21

22 Installation order Table 4 Typical installation order for an Enterprise Vault server system on Windows Server 2003 and Windows 2000 communicating with Exchange Server 2003 or Exchange 2000 Server Step Software to install Notes 5 SQL Server 7 Service Pack 1, if you installed SQL Server 7 in step 3. You must register your SQL Server and start the SQL services (SQLServerAgent and MSSQLServer) before configuring Enterprise Vault. 6 On Windows 2000 only, install Service Pack 3 7 Server Manager for Exchange Server 2003 or Exchange 2000 Note that if both Enterprise Vault and Exchange server are to be on the same computer a, you would also install Exchange Server 2003 or Exchange 2000 Server. The version you require depends on the operating system running on the Enterprise Vault computer and the version of Exchange Server being processed. To find out which version to install, see Exchange System Manager on Enterprise Vault servers on page 30. You must install Exchange Server 2003 Server Manager on a Windows Server 2003 computer. Do not install Server Manager for Exchange 2000 on an Enterprise Vault server that is running Windows Server Before installing

23 Installation order Table 4 Typical installation order for an Enterprise Vault server system on Windows Server 2003 and Windows 2000 communicating with Exchange Server 2003 or Exchange 2000 Server Step Software to install Notes 8 MSXML Supplied in the Redistributable Software folder on the Enterprise Vault CD-ROM. Alternatively, install Internet Explorer 6, which includes MSXML. MSXML Requirement for Enterprise Vault servers on page Microsoft Data Access Components (MDAC) 10 Microsoft.NET Framework v1.1 or later Use version 2.6 or later. Supplied in the Redistributable Software folder on the Enterprise Vault CD-ROM. A suitable version is installed automatically with Windows Server 2003 Redistributable Software folder on the Enterprise Vault CD-ROM. To install, double-click dotnetredist.exe, which unpacks the file dotnetfx.exe. Then double-click dotnetfx.exe. A suitable version is installed automatically with Windows Server Notes on Windows Server 2003 and Windows 2000 installation on page 25. a. If the Enterprise Vault Server and Exchange Server are on the same computer, the NNTP and SMTP services need to be installed. Before installing 23

24 Installation order Table 5 Typical installation order for a standalone Administration Console for administering Enterprise Vault on Windows 2000 or later Step Software to install Notes 1 One of: Windows Server 2003 Windows 2000 Server (with Service pack 3) Windows XP Professional Windows 2000 Professional Windows Millennium Edition 2 Outlook 2003, Outlook 2002 or Outlook 2000 with CDO components 3 Administration Tools for Windows Server 2003 or Windows Server Manager for Exchange 2000 or Exchange Server 2003 Installing Outlook 2000 on the Enterprise Vault computer on page 30 These are not required if you have installed Windows Server 2003 or Windows 2000 Server on the standalone console computer. The Administration Tools for Windows Server 2003 require Windows XP Professional or later. The version you require depends on the operating system running on the Enterprise Vault computer and the version of Exchange Server being processed. To find out which version to install, see Exchange System Manager on Enterprise Vault servers on page Before installing

25 Installation order Table 5 Typical installation order for a standalone Administration Console for administering Enterprise Vault on Windows 2000 or later Step Software to install Notes 6 Microsoft Data Access Components (MDAC) 7 Microsoft.NET Framework v1.1 or later Use version 2.6 or later. Supplied in the Redistributable Software folder on the Enterprise Vault CD-ROM. A suitable version is installed automatically with Windows Server Redistributable Software folder on the Enterprise Vault CD-ROM. To install, double-click dotnetredist.exe, which unpacks the file dotnetfx.exe. Then double-click dotnetfx.exe. A suitable version is installed automatically with Windows Server Make sure ASP.NET is selected, as described in Notes on Windows Server 2003 and Windows 2000 installation Notes on Windows Server 2003 and Windows 2000 installation Install Windows with the following options: NTFS file system Message Queuing Services. Installing MSMQ on page 26 and MSMQ settings when Enterprise Vault is on Active Directory controller on page 27..NET Framework IIS with Active Server Pages enabled. On Windows Server 2003, additional steps are needed to enable ASP.NET and configure Active Server Pages - see Configuring.NET Framework and Active Server Pages on Windows Server 2003 on page 28. Before installing 25

26 Installation order Installing MSMQ If you want to install Enterprise Vault services on more than one computer in the network, you must set up MSMQ on each computer. There can be more than one MSMQ site in an MSMQ organization. The Archiving, Public Folder, Retrieval, and Journaling Services all use MSMQ to communicate with the Storage Service. You can install these services all on the same computer or on separate computers. The steps for installing MSMQ on Windows Server 2003 and Windows 2000 are different. Follow the instructions below for your operating system. For more information about how to set up MSMQ, see the Windows Help. To install MSMQ on Windows Server 2003: 1. In the Windows Control Panel, double-click Add/Remove Programs. 2. Click Add/Remove Windows Components. The Windows Components wizard starts. 3. Select Application Server and then click Details to open the Application Server window. 4. Select Message Queuing checkbox, and then click Details to display the Message Queuing dialog. 5. Active Directory Integration should not be enabled, even when installing on a Domain Controller, so clear the Active Directory Integration checkbox in the Message Queuing dialog. 26 Before installing

27 Installation order 6. Click OK twice to return to the Windows Components wizard. 7. Follow the remaining instructions in the wizard. To install MSMQ on Windows Server 2000: 1. In the Windows Control Panel, double-click Add/Remove Programs. 2. Click Add/Remove Windows Components. The Windows Components wizard starts. 3. Click Next. 4. Select the Message Queuing Services checkbox, and then click Next. The Message Queuing Installation wizard starts. 5. In the Message Queuing Installation wizard, click Message Queuing server. 6. If the computer is a Domain Controller, click Next to complete the installation. If the computer is not a Domain Controller, you get the following prompts: Select the Manually select access mode to Active Directory checkbox and click Next. Select Message Queuing will not access a directory service and click Next. 7. Follow the remaining instructions in the wizard. MSMQ settings when Enterprise Vault is on Active Directory controller Note: You do not need to perform these steps if Enterprise Vault is not installed on the Domain Controller. If the Enterprise Vault server is to be installed on the Domain Controller, you must perform the following steps to configure Microsoft Message Queue Security to give permissions to the Administrators group. This enables the Vault Service account to access the queues that it needs. You need administration privileges in order to do this. Before installing 27

28 Installation order 1. Click Start, Programs, Administrative Tools, Computer Management. 2. In the left-hand pane, double-click Computer Management, Services and Applications. 3. Right-click Message Queuing and, on the shortcut menu, click Properties. The Message Queuing Properties window appears. 4. Click Add. The Select Users, Computers, or Groups window appears. 5. Next to Look In, select Entire Directory. 6. In the list, click Administrators and then Add. 7. Click OK to go back to the Message Queuing Properties window. 8. Click Administrators. 9. Under Permissions, click the Allow checkbox next to Full Control. 10.Click OK. 11.Close Computer Management. Configuring.NET Framework and Active Server Pages on Windows Server 2003 On Windows 2000, when you install IIS and.net Framework, Active Server Pages and ASP.NET are enabled by default. However, on Windows Server 2003, you need to enable these manually as follows: 1. Open Add/Remove Programs and select Add/Remove Windows Components. 2. Ensure Message Queuing Services and ASP.NET are 28 Before installing

29 Installation order selected. 3. To install required components and enable Active Server Pages, select Application Server and click Details. 4. Select Information Services (IIS) and click Details. 5. Scroll down to World Wide Web Service. Click this and then Details. 6. Select Active Server Pages and click OK. 7. Click OK to close the dialog boxes until you get back to the Windows component list. 8. Click Next to install the additional components. 9. Click Finish To check that Active Server Page scripts can run: 1. Start the IIS Manager by clicking Start, Programs, Administrative Tools, IIS Manager 2. Click Web Service Extensions 3. Check that Active Server Pages are Allowed Allowing HTML items larger than 4MB to be downloaded By default, IIS 6 on Windows Server 2003 prevents any file larger than 4MB from being downloaded. When users view archived items in their browser using OWA, Enterprise Vault web access application or customized shortcuts, an HTML version of the item is downloaded to their browser. This limit will prevent users from viewing any HTML items that exceed 4 MB. For details on how to change this limit: 1. Open Internet Services Manager 2. Click Help 3. Search for AspBufferingLimit 4. You want the occurrence found in the Troubleshooting section Before installing 29

30 Installation order Installing Outlook 2000 on the Enterprise Vault computer When you install Outlook on the Enterprise Vault server, you must create a profile and connect to an Exchange server mailbox before you install Enterprise Vault. Outlook may display an error message about a conflicting program. If Outlook offers to fix the problem, click Yes and then follow the instructions given. See the Administrator help topic MAPISVC.INF Problems. Exchange System Manager on Enterprise Vault servers Enterprise Vault servers with an Archiving Service, Journaling Service, or Storage Service must have the Exchange System Manager tools and fixes shown below. This ensures that the Enterprise Vault server has more resilient MAPI software than is supplied by default. The software you need to install is shown in Table 6. Please check the ReadMeFirst file on your Enterprise Vault release CD-ROM for any late updates to this information. 30 Before installing

31 Installation order Table 6 Required Exchange System Manager versions Operating system on Enterprise Vault server Exchange Server version Windows Server 2003 Exchange Server 2003 Exchange System Manager Exchange Server 2003 Exchange System Manager Exchange Server 2003 Exchange System Manager Windows 2000 Server Exchange Server 2000 Exchange System Manager. If archiving from a computer that is running Exchange Server 5.5, include support for Exchange Server 5.5 Exchange 2000 Server Service Pack 3 Exchange Server 2000 Exchange System Manager. Exchange 2000 Server Service Pack 3 Exchange 2000 Post-Service Pack 3 (SP3) Rollup Patch Exchange Server 2000 Exchange System Manager. Exchange 2000 Server Service Pack 3. Exchange 2000 Post- Service Pack 3 (SP3) Rollup Patch Exchange 2000 Post-Service Pack 3 (SP3) Rollup Patch Windows NT4 Exchange 5.5 Administrator Exchange Server 5.5 Service Pack 4 MAPI Hotfixes and Configuring Application Pool accounts In IIS, you can configure the level of isolation for particular web applications. For shopping baskets in the Enterprise Vault web access application to be created Before installing 31

32 The Vault Service account The Vault Service account correctly, the application needs to run under the predefined Local System account. The configuration program will automatically set the correct isolation and account settings. You do not need to configure this. If you have IIS 6.0 installed, the configuration program will create a new Application Pool, EnterpriseVaultAppPool, for the web access application and assign the Local System account to that pool. Purpose The Vault Service account is used by Enterprise Vault processes to access the Windows server operating system. The Enterprise Vault services, which are Windows services, run under this account. The Vault Service account is shared by all the Enterprise Vault computers in the Enterprise Vault Directory. If you are managing multiple Enterprise Vault sites, you can use the same Vault Service account for more than one Enterprise Vault site. If you are using Exchange Server 2003 or Exchange 2000 Server, the Vault Service account must be a member of the Active Directory domain. Creating the Vault Service account on page 48 for details on how to set up this account. You are recommended to be logged in to the Vault Service account when you install and administer Enterprise Vault. The Vault Service account must be a domain-based Windows security account that belongs to the local Administrators group on all computers in the Directory. The account password must not be blank. 32 Before installing

33 The Vault Site alias The Vault Site alias We recommend that you do not make this account a Domain Administrator. It is better to assign Exchange permissions explicitly, as described in Assigning Microsoft Exchange Server permissions on page 49. The account does not need a mailbox, but you may want to create one and use it for the service mailbox, described in The service mailbox on page 34. If possible, create the account so that it is in the same domain as the Enterprise Vault computers. If it is necessary for the Vault Service account and the Enterprise Vault computers to be in different domains, create the account so that it is in a domain that is trusted by the Enterprise Vault computers domain. During configuration, you are asked to provide the name and password of the Vault Service account. Enterprise Vault automatically grants the Vault Service account the following advanced user rights: Log On As a Service Act As Part Of The Operating System Debug programs What it is The Vault Site alias is a DNS entry for an Enterprise Vault site. Each Enterprise Vault site should have a Vault Site alias, which is used by the Enterprise Vault software to refer to the Enterprise Vault site by name. The DNS entry is an alias whose value is the name of the computer that runs the Vault Directory Service for the site. Creating the Vault Site alias on page 52 for more information on how to set up this alias. Purpose Using a DNS alias serves two purposes: If the Vault Directory is shared between more than Before installing 33

34 The service mailbox one Enterprise Vault site, it allows the configuration information for each of the Enterprise Vault sites to be distinguished. It allows future flexibility if you change the computer that is running the Vault Directory Service. Recommendation If you are setting up Enterprise Vault as a pilot system, to avoid the need of creating a temporary DNS entry you can configure Enterprise Vault without a Vault Site alias. Instead, you must supply a full and valid DNS name of the Directory Service computer when prompted for the Vault Site alias. In all other situations use a Vault Site alias for the site. The service mailbox To use a DNS alias, you must set it up before starting the configuration. If you do not have access to the DNS Server in your organization you may need to request a DNS alias from your network manager. What it is Requirements The service mailbox is a mailbox that is used by the Archiving, Journaling, Public Folder, and Retrieval Services. The services require exclusive use of this mailbox, so it must not be used for any other purpose. The mailbox must not be hidden from address lists and, on Windows Server 2003 and Windows 2000, the account must not be disabled. Creating the mailbox If you have the privileges to create new mailboxes, then the Enterprise Vault configuration program can create the mailbox automatically when you are running the configuration program. If you do not want the configuration program to create the mailbox, you can create the mailbox before running the configuration program and then, when prompted for a mailbox, select the mailbox you created. 34 Before installing

35 MSXML Requirement for Enterprise Vault servers MSXML Requirement for Enterprise Vault servers MSXML for Windows NT 4 All Enterprise Vault server computers require MSXML. All Enterprise Vault server computers require MSXML, which you can obtain by installing one of the following: Internet Explorer 6.0. You need only 'Internet Explorer 6 Web Browser', which you can select from a Customized installation. All the following software: Internet Explorer You need only Internet Explorer 5 Web Browser, which you can select from a Customized installation. Windows Installer. This is required in order to install MSXML version 3.0 SP2. This is supplied as file InstMsi.exe in the Redistributable Software folder on the Enterprise Vault CD-ROM. MSXML version 3.0 SP2. This is supplied as file msxml3sp2setup.exe in the Redistributable Software folder on the Enterprise Vault CD-ROM. If your computer does not have the correct prerequisite software, then install the extra software that you need. MSXML for Windows Server 2003 and Windows 2000 All Enterprise Vault server computers require MSXML, which you can obtain by installing one of the following: Internet Explorer 6.0 You need only Internet Explorer 6 Web Browser. This comes as the default with Windows Server On Before installing 35

36 Requirements for the Enterprise Vault OWA Extensions Windows 2000 you can select it from a Customized installation. MSXML version 3.0 SP2 This is available as file msxml3sp2setup.exe in the Redistributable Software folder on the Enterprise Vault CD-ROM. Requirements for the Enterprise Vault OWA Extensions You may have already installed MSXML when preparing a computer to be an Enterprise Vault server. However, if you intend to install the Enterprise Vault OWA Extensions on a separate computer, then you must install MSXML as follows: Exchange Server 2003 and Exchange 2000 OWA Extensions (Back-end): Install MSXML as described in MSXML for Windows Server 2003 and Windows 2000 on page 35 Exchange Server 2003 and Exchange 2000 OWA Extensions (Front-end): MSXML is not needed Exchange Server 5.5 OWA Extensions: Install MSXML as described in MSXML for Windows NT 4 on page 35 Requirements for users computers To be able to archive items from a mailbox, users must have User Extensions installed on their computers. However, users can view and restore archived items in archives using any of the following methods: Using Outlook 2003, Outlook 2002 or Outlook 2000 with Enterprise Vault User Extensions or Self- Installing User Extensions.User Extensions for Outlook on page 37. User Extensions enable users to archive items, search an archive, view and restore 36 Before installing

37 Requirements for users computers items. Using Outlook or some other client without Enterprise Vault User Extensions. This uses Enterprise Vault customized shortcuts. The shortcut in an archived message opens a browser window, which enables the user to access the original message, search archive(s), download items to their computer or restore items to an Exchange server mailbox. To support these customized shortcuts, users need a PC or Mac computer with Internet Explorer 5.01 or later installed and Java scripting enabled. The client used to access Exchange mailbox can be any locally installed POP or IMAP client or a web client a. Using the Enterprise Vault web access application. This enables users to search multiple archives using advanced filtering and restore multiple items. To support the Enterprise Vault web access application, users need a PC with Internet Explorer 5.01 or later installed and Java scripting enabled. Using the Enterprise Vault Archive Explorer feature. This gives users an explorer window onto their archive(s). Archived folders can be navigated in the same way as Outlook or file system folders. To support Archive Explorer, users must have Internet Explorer 5.01 or later installed and Java scripting enabled. User Extensions for Outlook Before users can send items to an archive from within their Outlook client, the User Extensions or Self- Installing User Extensions must be installed on their computers. For the normal User Extensions, the computers must be running the following: Operating System one of the following: Before installing 37

38 Requirements for users computers Windows Server 2003, Windows 2000 or Windows NT Server Version 4.0 with Service Pack 6a or later Windows XP Professional, Windows 2000 Professional or Windows NT Workstation Version 4.0 with Service Pack 6a or later. Windows 95 OSR2 or later, Windows 98, or Windows Millennium Edition On Windows 98 computers you need to install Distributed COM or later. You can download this version from: dcom98/dcom1_3.asp On Windows 95 computers, the Enterprise Vault installation procedure checks for Distributed COM for Windows 95. It is available in later versions of Windows 95. If Distributed COM is not available in your version of Windows 95, the Enterprise Vault installation will notify you that it is not present. In this case, you can install it from the Redistributable Software folder on the Enterprise Vault CD-ROM. You may want to make Distributed COM available to users on the network when they install the Enterprise Vault user extensions. If you do this, read the Microsoft End User License Agreement that is provided in EULAS.TXT in the Enterprise Vault Program folder. On Windows 95 and Windows 98 computers, access control must be set to User level access. You need network administration privileges for the Windows 95 or Windows 98 computer to do this. Without this level of access users will not be able to store items in an archive. Mail Client one of the following: 38 Before installing

39 What next? Microsoft Outlook 2003 Microsoft Outlook 2002 (XP) Microsoft Outlook 2000 Microsoft Outlook 98 Microsoft Outlook 97 Note that Internet Explorer must be installed before the mail client is installed. Web browser one of the following. Java scripting must be enabled: Internet Explorer 5.01 or later. This must be installed, even if it is not used. If you intend to make the Self-Installing User Extensions available to users, Internet Explorer must allow them to download signed ActiveX controls. TCP/IP protocol What next? Go to: Preinstallation tasks on Windows NT on page 41 Preinstallation tasks on Windows Server 2003 and Windows 2000 on page 47 Before installing 39