FORTIS INSTALLATION GUIDE

FORTIS INSTALLATION GUIDE JUNE 2009 EDITION: RELEASE 2.4.1 SERVICE PACK 4 Westbrook Technologies, Inc. 22 Summit Place Branford, CT 06405 USA Toll free: 800 949 3453 Outside U.S.: (+1) 203 483 6666 Fax: 203 483 3350 e mail: Info@westbrooktech.com

Fortis Installation Guide Page 2 COPYRIGHTS, LEGAL NOTICES, TRADEMARKS AND SERVICEMARKS Copyright 1998-2009 Westbrook Technologies Incorporated. All rights reserved. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including but not limited to photocopy and recording, or by any information storage or retrieval system, without the prior agreement and written permission of Westbrook Technologies, Incorporated unless such copying is expressly permitted by federal copyright law. Address inquiries to info@westbrooktech.com June 2009 Edition: Release 2.4.1 Service Pack 4 Publication is subject to change without notice. Westbrook Technologies, Incorporated assumes no liability for any damages incurred directly or indirectly from errors, omissions, or discrepancies between the actual software you install and / or the contents of this publication or any other accompanying publication. Fortis, Fortis SE, Fortis Web, Fortis Office and Fortis CDExpress are trademarks of Westbrook Technologies, Incorporated. Enterprise Document Management for the Mid- Market, The Most Powerful Name in Document Management Software, The Power of Document Management on the World Wide Web, and Document Management Solutions Made Easy are service marks of Westbrook Technologies Incorporated. All other products and devices listed in this document are trademarks or registered trademarks of their respective companies and are hereby acknowledged.

Fortis Installation Guide Page 3 CONTENTS Welcome to Fortis... 8 Installation Overview... 9 Upgrading to Fortis 2.4.1... 11 Introduction... 11 Before Beginning the Upgrade to 2.4.1... 11 SYSADM User Default Password Change... 11 Fortis CDExpress Customers... 12 Fortis ApproveIt Customers... 12 Installing Inflo or Script Manager as a Windows Service... 12 Installing Solidworks edrawings Viewer (AutoCAD)... 13 Upgrade Fortis... 14 Upgrade to Fortis Version 2.4.1:... 14 Upgrade the Fortis Workstations... 14 Upgrade Fortis Web... 15 Upgrade Fortis Inflo... 16 Installing Fortis SE... 17 Introduction... 17

Fortis Installation Guide Page 4 Installing SQL Server 2005 Express... 18 Install and Configure Fortis SE Database and Application Servers... 18 Installing Fortis Web IIS Server... 20 Installing Fortis SE Workstation Software... 20 Installing Fortis Embedded SQL Server... 21 Introduction... 21 Installing the Fortis Database Server Software... 22 Installing Fortis Shared-Client Software... 22 Installing Fortis Workstation Software... 23 Installing Fortis Options... 23 Modifying Fortis Database Paths... 23 To Change the Storage Path for New Fortis Databases:... 23 Modifying the Fortis Database Backup Storage Location:... 24 Installing Fortis for Microsoft SQL Server... 25 Introduction... 25 Installing Fortis Shared-Client Software... 26 Installing Fortis Workstation Software... 26 Installing Fortis Options... 26 Helpful Hints... 26

Fortis Installation Guide Page 5 Installing Fortis for Oracle... 27 Introduction... 27 Installing Fortis Shared-Client Software... 28 Installing Fortis Workstation Software... 28 Installing Fortis Options... 28 Helpful Hints... 28 Installing Fortis Shared-Client Software... 29 To Setup and Configure Your Fortis Shared-Client Software:... 29 Installing Fortis Workstation Software... 31 Workstation Setup... 31 Important Information about Microsoft Data Access Components (MDAC)... 31 Important Information About Windows Vista User Access Control (UAC)... 31 Important Information About Fortis Oracle on Windows Vista... 31 To Install Fortis Client Software on a Workstation:... 32 Silent Workstation Setup... 33 How to Configure a Silent Workstation Setup... 34 Configuring Group Policy to Perform a Push Install... 38 Create Fortis Preferences INI... 38 Steps To Create a Preferences INI... 38

Fortis Installation Guide Page 6 CDExpress Workstation Setup... 39 Installing Fortis Options... 39 To Install Options for Your Fortis Client Software:... 39 To Install a Second Component for Your Fortis Client Software:... 40 To Increase the User Count for Your Fortis Installation:... 41 Installing the Fortis Web Server... 42 Installing the Fortis Web Client ActiveX Control... 44 Fortis Web Client ActiveX Security Settings... 44 Print-To-MAG Driver... 45 Installation... 45 Distribution... 45 Uninstalling Print-To-MAG Windows 2000... 46 Installing Fortis 2.4.1 Service Pack 4... 47 Important Information for Spanish Localization... 48 Fortis Workstation Regional Settings for Spanish... 48 Microsoft SQL Server 2005 Express Installation... 48 Fortis Web Server Templates for Spanish... 49 Configuring Fortis ecopy SSOP for Spanish... 49 Uninstalling Fortis Office Send to Fortis Buttons... 50

Fortis Installation Guide Page 7 Office 2000, XP, 2003... 50 Word:... 50 Excel, PowerPoint, and Outlook:... 52 Office 2007... 53 Word, Excel, and PowerPoint:... 53 Outlook:... 53

Fortis Installation Guide Page 8 WELCOME TO FORTIS Welcome to Fortis, Westbrook Technologies client/server document management software product. At Westbrook Technologies, we continually strive to produce the most robust and reliable document management products on the market. We have been actively developing our product lines for more than ten years. With each release, we add features and functionality, address customer-related issues, and update hardware and software components as they relate to our products and technology platforms. Due to the technical nature of our products, we require that all installations and upgrades be performed by highly-trained personnel. These individuals can include our Consulting Services staff, a certified Business Partner, or an end user with the appropriate experience and administration training from Westbrook Technologies University. The information contained in this manual is intended for use by qualified personnel. The concepts, techniques, and knowledge necessary to perform an installation or upgrade are beyond the scope of this manual. That is, this manual only contains a basic overview of the necessary steps. Our certified Business Partners receive significant education so that they can perform installations and upgrades properly. Therefore, we discourage others from attempting to perform such operations unless they have been properly trained and/or certified by Westbrook Technologies, Inc. We are committed to getting the job done right and ask that you protect your investment in our products by taking the appropriate action. With today's fast-paced technology, it is more important than ever to keep your system up-to-date and functioning properly. If you have questions or concerns, please contact your authorized Westbrook Technologies Partner or one of our Regional Sales Managers.

Fortis Installation Guide Page 9 INSTALLATION OVERVIEW Fortis operates as a client/server system. The database engine is installed on a dedicated database server and the client software is installed on a shared network drive. Client workstations running Windows 2000 Professional SP4, Windows XP Professional SP2 or Windows Vista Ultimate, Enterprise or Business Edition are then configured to run Fortis. Fortis supports several different types of installations: Fortis Upgrade Fortis SE Fortis Embedded Microsoft SQL Server Fortis for Microsoft SQL Server Fortis for Oracle NOTE: For information about any other ODBC-compliant database engine, please contact our Software Support department. Workstations are defined as one or more of the following: System Administration, Database Administration, Scan, Edit and View Stations. Fortis systems also include Fortis Script Manager, a program used to monitor scheduled Scripts. A System Administration Station provides the functionality of the system administrator, including such tasks as creating system users and passwords, assigning users to Groups, and granting users database access. In addition, you can set up public and private In Baskets, where Scan and Edit Station users can store documents before indexing them to a database. A Database Administration Station provides the database administrator with all the tools necessary to design, create, and maintain a Fortis database. The database administrator defines the basic components of a database, such as the database Folder hierarchy and the index fields for various Document Types, and runs database performance tools. A Scan Station provides the user with all the functionality of the Fortis product with the exception of administration tools. Users can scan, import, or fax documents into the system, index and edit scanned or imported documents, perform searches, and view documents.

Fortis Installation Guide Page 10 An Edit Station lets users index and edit documents, import or fax documents into the system, perform searches, and view documents. A user of an Edit Station cannot scan documents. A View Station lets users perform searches and view documents. A user of a View Station cannot index, edit, scan, import, or fax in documents. NOTE: If your installation has the View Station with Annotations option installed, View Station users can also annotate documents. The View Station with Annotations option does not allow users to apply AutoNumber stamps nor can a user modify an existing AutoNumber stamp or Searchable Annotation from the View Station Client. Script Manager monitors scheduled database-related Scripts (i.e., Scripts that send documents to a database Folder) and non-database Scripts (i.e., Scripts that send documents to an In Basket). Fortis ERM (Electronic Report Management) has three additional components: Fortis ERM Setup users can define the layout of ERM documents so that Fortis can automatically extract information from the documents. Setup users can also define new ERM Applications using a simple point and click interface. Fortis ERM Process users can add documents to the Fortis ERM document warehouse. Process imports production documents from the Fortis ERM import folder. Fortis ERM System Monitor automates Fortis ERM Process. It resides in the background, watching for new files that have been written to the Fortis ERM import folder.

Fortis Installation Guide Page 11 UPGRADING TO FORTIS 2.4.1 INTRODUCTION The following instructions are for customers currently running version 2.3.0 or 2.4.0 of Fortis Embedded SQL Server, Fortis for SQL Server, Fortis for Oracle or Fortis SE. Following the procedures below will update your Fortis installation to version 2.4.1. IMPORTANT: If you are currently running a Fortis version older than 2.3.0, you must first upgrade to 2.3.0 and follow all steps as documented in the Fortis 2.3.0 Installation Guide before you can upgrade to 2.4.1. Please contact our Software Support department if you have questions about upgrading. Failure to upgrade to Fortis 2.3.0 and follow all instructions before upgrading to Fortis 2.4.1 may result in corruption of the Fortis application and/or permanent data loss. BEFORE BEGINNING THE UPGRADE TO 2.4.1 Fortis version 2.4.1 contains significant changes and improvements. Before you upgrade, you should carefully review the instructions in this document. If you have any concerns, perform a demo installation of Fortis so you can evaluate these changes. IMPORTANT: Before you upgrade, make sure you've backed up your entire Fortis system, including the application itself and all related data folders and databases. Version 2.3.0 installs of Fortis Embedded SQL Server and Fortis SE will also be upgrading the database server from Embedded SQL Server 2000 or MSDE to Embedded SQL Server 2005 or SQL Server 2005 Express. To minimize risk of downtime customers may wish to run the upgrade install from a new database server instead of upgrading the original database server. Once the new database server install and the Fortis 2.4.1 Upgrade is complete the Fortis databases can be moved to the new database server by first detaching them from the original database server and then copying the files to the new database server and attaching them to the new SQL Server 2005 database server. See Microsoft SQL Server books online for more information on how to detach and attach databases. SYSADM USER DEFAULT PASSWORD CHANGE IMPORTANT: The Fortis SYSADM user default password has been changed for all new installs of Fortis 2.4.1. The new default SYSADM password is now: westtech#1 The SYSADM user password will UNOTU be changed on existing Fortis installations that upgrade to Fortis 2.4.1. It is strongly recommended that all Fortis customers change the SYSADM user password to a strong password immediately after installation of Fortis 2.4.1 to make the SYSADM login is more secure. It is especially important that customers using CDExpress update their SYSADM password to be a strong password that complies with SQL Server 2005 Express password policies. Please see the topics Fortis CDExpress Customers located on page 12 and CDExpress Workstation Setup on page 39 for more information.

Fortis Installation Guide Page 12 FORTIS CDEXPRESS CUSTOMERS Fortis 2.4.1 now uses SQL Server 2005 Express to support CDExpress workstations and the CDExpress View Station client. In order for CDExpress recordings to install and run correctly on the end user PC it is required that both the Fortis Database Owner username and password and the SA account password is synchronized between the Fortis database server and the CDExpress Workstation s instance of SQL Server 2005 Express. Failure to do so may result in users being unable to open a CDExpress database after it is installed. FORTIS APPROVEIT CUSTOMERS The Fortis 2.4.1 upgrade process will install new template files and overwrite existing files, including configuration settings specified in the Default.ini file. We strongly recommend that you make a complete backup of your ApproveIt template files and configuration files (C:\Fortis\PWSites_Approve) to avoid overwriting modified template files and any ApproveIt profiles you have created. When you ve completed the entire upgrade process, contact Westbrook Technologies Professional Services with any questions on integrating any existing modifications into the new Fortis ApproveIt templates. INSTALLING INFLO OR SCRIPT MANAGER AS A WINDOWS SERVICE IMPORTANT: If you are installing either Fortis Inflo or Fortis Script Manager as a Windows Service there are several important caveats that you must follow. 1) The path to the executable in the Windows Service configuration must be a UNC path. The MSI installer will always use a UNC path or will attempt to convert a path containing a mapped drive into a UNC path. Please do not modify the UNC path to use a mapped drive, failure of the Windows Service will likely result. Microsoft best practices state that Windows Services path to executable must use UNC. Please refer to this MSDN Article for more information: http://msdn.microsoft.com/en-us/library/ms685143(vs.85).aspx 2) By default most Windows Services are configured to log on using the Local System account. In the case of a Fortis Inflo Server or Fortis Script Manager Server running as a service and accessing the Fortis Shared Client directory across the network via UNC you will need to change the Log On to use a specific account that has network access to the Fortis Shared Client directory.

Fortis Installation Guide Page 13 INSTALLING SOLIDWORKS EDRAWINGS VIEWER (AUTOCAD) Fortis 2.4.1 includes a new feature to support viewing of additional AutoCAD file formats for users that install a free viewer from SolidWorks Corporation called edrawings. The steps to download and install edrawings on a Fortis Workstation are included below. 1) Download edrawings from here: Be sure to select edrawings Viewer Only. Click Next. http://www.edrawingsviewer.com/pages/programs/download/index.html 2) The default language for the download is English, you can also optionally choose to include the feature Yes, I want to view 3D XML and PRO/E files using edrawings viewer. Click Download. 3) Read and Accept the License agreement to begin the download. 4) Once edrawings is downloaded install it on each Fortis Workstation that will use the enhanced AutoCAD feature. You may be prompted to enter a license key to enable advanced features, skip this screen and continue with the install. 5) Before opening Fortis, launch the edrawings software and complete the brief product registration process as required by SolidWorks Corporation. 6) Launch Fortis and enable the setting under General Preferences > View called View CAD format files with edrawings. Once that preference is enabled you will be able to open supported CAD file formats in the Fortis document viewer using the installed edrawings viewer.

Fortis Installation Guide Page 14 UPGRADE FORTIS UPGRADE TO FORTIS VERSION 2.4.1: 1) Insert the Fortis 2.4.1 upgrade CD into the CD drive of a client machine that has access to the previously installed Fortis shared-client software. If AutoPlay should fail to run, select Run from the Start menu and type X:\SETUP (where X: is the drive letter of your CD drive). Click OK. IMPORTANT: If you are using Fortis SE, begin the upgrade procedure by inserting the upgrade CD into the CD drive of the database server. IMPORTANT: If you are using Fortis Embedded SQL Server begin the upgrade procedure by installing Microsoft SQL Server 2005 using the provided Microsoft SQL Server 2005 CD and then insert the upgrade CD into the CD drive of the database server. 2) Setup displays a Welcome dialog box, urging you to close any Windows programs and disable any antivirus software that may be running. Follow the instructions, and then click Next. 3) Setup displays a Software License Agreement. To accept the terms of the agreement, click Yes. 4) Setup will then ask for the Fortis shared-client software location defaulting to X:\Fortis, where X is your shared network drive. To accept this location, click Next. Next. If you installed to a different location, click Browse and select that folder and then click 5) Setup displays a message indicating that installing the 2.4.1 Upgrade will remove access to Fortis Office Sentry if it is installed as this option is no longer supported. 6) Select Continue Setup and click Next if you wish to proceed. If you do not wish to proceed with the upgrade then click Cancel. 7) If you elected to continue, Setup completes the upgrade. You should now proceed to upgrade the Fortis workstations. NOTE: If you have other Fortis server options such as Fortis Web or Fortis Inflo, you will need to perform an upgrade on those servers as well. See the appropriate sections of this document for detailed instructions. UPGRADE THE FORTIS WORKSTATIONS To complete the 2.4.1 upgrade procedure, you should also upgrade each Fortis workstation. This process distributes the appropriate files to the local workstation. Please refer to XInstalling Fortis Workstation SoftwareX located Xon page 31X.

Fortis Installation Guide Page 15 UPGRADE FORTIS WEB Before upgrading from previous versions of Fortis PowerWeb or Fortis Web, you must upgrade your Fortis installation to version 2.4.1, as described previously in this document. To prevent any loss of data, we strongly recommend that you make a complete backup of your Fortis website before beginning this procedure. If you have modified your template files, prior to upgrading to Fortis Web rename your Fortis Web Virtual directory in IIS to avoid overwriting your modified files. The upgrade procedure will create a new Fortis Web Virtual Directory that you can review for changes. IMPORTANT: Fortis Web minimum system requirements are Windows Server 2003 SP2 with Internet Information Services (IIS) 6.0. NOTE: The following steps must be performed from the Fortis PowerWeb server machine. 1) Confirm Windows Scripting Host is installed. (This is part of the default IIS installation.) 2) Confirm that ASP.NET 2.0 in installed and enabled for the Fortis Web virtual directory. 3) Make sure that all users have exited Fortis. 4) Make sure that all connections between the web server and the shared-client server have been terminated. 5) Open Internet Information Services (IIS) Manager and stop the IIS Server. 6) Back up your Fortis program folder (e.g., X:\FORTIS). 7) Insert the Fortis 2.4.1 upgrade CD into your CD drive. If AutoPlay is enabled, exit the startup screen. Run Setup from the Fortis Web folder on the CD, (e.g. E:\FORTISWEB\SETUP.EXE). 8) Setup asks you to enter the existing Fortis shared-client software folder on your network (e.g. X:\FORTIS). 9) Setup also asks for the PowerWeb website folder (e.g., C:\PWSITES). 10) Follow the remaining on-screen instructions to complete the upgrade. 11) Configure IIS to allow access to the Fortis Web Extension DLL. In the IIS Manager, locate the Fortis Web folder under Default Web Site. Right-click the Dll folder and select Properties. The Dll Properties dialog box displays. Click Create, and then enter Dll as the Application name. From the Execute permissions list, select Scripts and Executables.

Fortis Installation Guide Page 16 Click OK on the Dll Properties dialog box. In the IIS Manager, select the Web Service Extensions folder. Click Add a new Web service extension. The New Web Service Extension dialog box displays. In the Extension name box, type FortisWeb. Click Add, and browse to the location of the PwrWbExt.dll file. Select the Set extension status to Allowed check box, and click OK. 12) Open Internet Information Services (IIS) Manager and restart the IIS Server. 13) To confirm that the upgrade to Fortis Web executed successfully, type the address for the Fortis Web home page in Internet Explorer on your IIS server to verify access to the Fortis Web home page. NOTE: On the IIS Server hosting Fortis Web the default Fortis Web page is HHUhttp://localhost/FortisWebU 14) Users with existing Internet Explorer Favorites may need to update them to reflect the new address for Fortis Web instead of PowerWeb. 15) Please refer to the new Fortis Web Admin Help and Fortis Web User Help for more information on configuring and using Fortis Web. UPGRADE FORTIS INFLO Before upgrading Fortis Inflo, you must upgrade your Fortis installation to version 2.4.1, as described previously in this document. 1) Make sure that all users have exited Fortis. 2) Make sure that all database monitoring on the Fortis Inflo Server has been terminated and the Fortis Inflo server is shut down. 3) Back up your Fortis program directory (e.g., X:\FORTIS). 4) Insert the Fortis 2.4.1 upgrade CD into your CD drive. If AutoPlay is enabled, exit the startup screen. Run Setup from the Inflo folder on the CD, (e.g. E:\INFLO\SETUP.EXE). 5) Setup asks you to enter the existing Fortis shared-client software folder on your network (e.g. X:\FORTIS). 6) Follow the remaining on-screen instructions to complete the upgrade. 7) Restart the Inflo Server and start Inflo. Resume all database monitoring as normal.

Fortis Installation Guide Page 17 INSTALLING FORTIS SE INTRODUCTION Prior to installation, refer to the Westbrook Technologies Web page at HHUhttp://www.westbrooktech.com/products/fortis/fortis_specifications.htmUH for a list of recommended minimum system specifications. Fortis SE operates as a true client/server system and requires a minimum of two servers. Our browser based document management solution; Fortis Web is available as a purchased option. Fortis Web should be installed on a dedicated web server which would bring the recommended configuration to a total of three servers. The database engine is Microsoft SQL Server 2005 Express and is installed on a dedicated database server running Windows 2000 Server SP4 or Windows Server 2003 SP2. The Fortis SE shared-client application software is installed on a shared network location and then a setup program is run at the Windows 2000 Professional SP4, Windows XP Professional SP2 or Windows Vista Ultimate, Enterprise or Business Edition LAN client workstations. Document Management LAN workstations are defined as the following: System Administration Station, Database Administration Station, Scan Station, Edit Station and View Station. The Fortis Web Server is installed to a dedicated Web Server running Windows 2003 Server SP2 and Internet Information Services (IIS) 6.0. Fortis Web provides thin-client access to intranet/internet users via an ActiveX control installed to each user s web browser, Internet Explorer (IE) version 6.0 and above. Document Management thin-client workstations are defined as Edit Station and View Station. System installation is therefore in five parts: 1) Microsoft SQL Server 2005 Express is installed on your Windows 2000 Server SP4 or Windows Server 2003 SP2 dedicated server. 2) The Fortis SE shared-client application software is installed to a network shared location on the application server that can be accessed by all your client workstations. 3) The Fortis Web Server is installed to a dedicated web server running Windows Server 2003 SP2 and Internet Information Services (IIS) 6.0. 4) The Fortis SE LAN client workstations are then configured to access both the client software and database server using a Setup program run at the workstation from the shared-client location.

Fortis Installation Guide Page 18 5) The Fortis Web thin-client web browser workstations will automatically be prompted to load the ActiveX control the first time they connect to the Fortis Web Server. The machine designated as the database server must be running Windows 2000 Server SP4 or Windows Server 2003 SP2. The server machine must be able to communicate over your network with the machines designated as the client workstation machines. These client workstations must be running Windows 2000 Professional SP4, Windows XP Professional SP2 or Windows Vista Ultimate, Enterprise or Business Edition. Your network must also be set up and configured with the TCP/IP communications protocol before you can configure your Fortis SE database server. To use TCP/IP, you must have TCP/IP properly installed on all of your servers and on all your client workstations. Check with your network administrator if you re unsure about the status of your network protocols. INSTALLING SQL SERVER 2005 EXPRESS INSTALL AND CONFIGURE FORTIS SE DATABASE AND APPLICATION SERVERS NOTE: If you are enabling Fortis Web with your Fortis installation, all paths will be set using UNC (Universal Naming Convention) not with a mapped drive letter. 1) On the SQL Server 2005 Express database server, map a drive letter to the network shared location on the application server that will contain the Fortis SE software. It is recommended but not required that you use the same drive letter mapping. NOTE: The Microsoft SQL Server 2005 Express database engine cannot be installed to a network share. This is only required for the Fortis SE application portion of the install. The network shared location that you map to for the install of Fortis SE must reside on a separate application server. Microsoft SQL Server 2005 Express must be installed on a dedicated database server. 2) Insert the Fortis SE installation CD into the CD drive of the server where Fortis SE will be installed. (If AutoPlay should fail to run, select Run from the Start menu and type X:\SETUP (where X: is the proper drive letter for your CD drive). Click OK. 3) Setup displays a Welcome dialog box, urging you to close any Windows programs and disable any antivirus software that may be running. Follow the instructions and then click Next. 4) Setup displays a Software License Agreement. To accept the terms of the agreement, click Yes. 5) Setup asks you for some information about yourself. Type your name, your company name, and the serial number of your copy of Fortis SE. Click Next.

Fortis Installation Guide Page 19 6) Setup now asks you if you want to register your copy of Fortis SE. To register, make sure the Register product now check box is selected and click Next. 7) If you don't register Fortis SE now, you can only use it 25 more times before you must register it. However, you can choose to register next time you launch the program. If you selected to register your copy of Fortis SE now, the Registration Information dialog box displays. Call Westbrook Technologies at 1-203-483-6666 to obtain your registration number, or fax your registration card and Machine ID to 1-203-483-3350 and your registration number will be faxed back to you. 8) Once you've obtained your registration number, type your number in the box provided and click Next. 9) Setup asks you for the folder where you wish to install Microsoft SQL Server 2005 Express. The default is C:\WTI\SQL2005. To accept this folder, click Next. To install SQL SERVER 2005 Express in a different folder, click Browse and select another folder, and then click Next. 10) You must specify a location where the Fortis SE databases will be stored. If you chose the default above, Setup will create a C:\WTI\DBS folder. To create a different database folder, click Browse and select another folder, and then click Next. 11) You must specify a location where the Fortis SE database backups will be stored. If you chose the default above, Setup will create a C:\WTI\Backups folder. To create a different database backup folder, click Browse and select another folder, and then click Next. 12) Setup will install the Fortis SE shared-client application software into a new folder called X:\Fortis, where X: is your shared network location. To accept this folder, click Next. To install Fortis SE in a different location, click Browse and select a different folder, and then click Next. 13) You must specify a location in which to store Fortis SE system files. Setup will create an X:\FORTISDT\SYSDATA folder, where X: is your shared network location. This folder is the default location for system and database related files that users need to access. The folder will be created at the same level in the folder tree as your Fortis SE application files folder. To accept this folder, click Next. To create a different data folder, click Browse and select another folder, and then click Next. 14) You must specify a default In Basket location. Setup will create an X:\FOR- TISDT\INBASKET folder, where X: is your shared network location. To accept this folder, click Next. To create a different INBASKET folder, click Browse and select another folder, and then click Next.

Fortis Installation Guide Page 20 NOTE: For your In Basket folder, be certain to select a network folder that is accessible by any input devices, such as scanners and fax machines, you plan to use. 15) Setup displays a list of Fortis SE options. The options you have purchased are indicated with a plus sign and selected with a check mark. Clear a check box if you don t want to install an option at this time. (You can install options at another time, if necessary, by running Setup from the X:\Fortis\Setup folder.) Click Next. NOTE: If you are installing the OCR Languages option, an additional dialog box displays where you can select the languages to install. 1) Setup displays all the information you ve entered. To make any changes, click Back to return to the previous steps, where you can modify settings. When the information is correct, click Next. 2) When the SQL SERVER 2005 EXPRESS and Fortis SE application software installation is complete, you will be prompted to restart the database server. You must restart the database server before you can proceed with the remainder of the installation. You can choose to restart your computer now or later. Click Yes to exit Setup and restart your machine. INSTALLING FORTIS WEB IIS SERVER Please refer to XInstalling the Fortis Web ServerX located Xon page 42X. INSTALLING FORTIS SE WORKSTATION SOFTWARE Once you have installed the Fortis SE database server software on your database server machine and installed the Fortis SE shared-client software to a network shared location, you can begin the process of installing the Fortis SE client software on each workstation that you plan to use to access the Fortis SE database server. Please refer to XInstalling Fortis Workstation SoftwareX located on page 31X.

Fortis Installation Guide Page 21 INSTALLING FORTIS EMBEDDED SQL SERVER INTRODUCTION Prior to installing Fortis Embedded SQL Server please refer to the Westbrook Technologies Web page at HHUhttp://www.westbrooktech.com/products/fortis/fortis_specifications.htmUH for a list of recommended minimum system specifications. You must also make certain your database server and client stations are communicating using the appropriate communications protocol for your network configuration. Fortis operates as a true client/server system which requires a minimum of two servers. The database engine is Embedded Microsoft SQL Server 2005 and is installed on a dedicated database server running Windows 2000 Server SP4 or Windows Server 2003 SP2. The client software is installed on a shared network location and then a setup program is run at the Windows 2000/XP Professional or Windows Vista client workstations. Document Management workstations are defined as the following: System Administration Station, Database Administration Station, Scan Station, Edit Station and View Station. ERM workstations are defined as the following: ERM Setup Station, ERM Process Station and ERM System Monitor Station. System installation is therefore in three parts: 1) The Fortis Embedded SQL Server software is installed on your Windows 2000 Server SP4 or Windows Server 2003 SP2 dedicated server. 2) The Fortis shared-client software is installed to a network shared location that can be accessed by all your client workstations. 3) The Fortis client workstations are then configured to access both the client software and database server using a Setup program run at the workstation from the sharedclient location. The machine designated as the database server must be running Windows 2000 Server SP4 or Windows Server 2003 SP2. The server machine must be able to communicate over your network with the machines designated as the client or workstation machines. These client workstations must be running Windows 2000 Professional SP4, Windows XP Professional SP2 or Windows Vista Ultimate, Enterprise or Business Edition.

Fortis Installation Guide Page 22 INSTALLING THE FORTIS DATABASE SERVER SOFTWARE To set up and configure your Fortis database server using Embedded SQL Server 2005: Insert the Microsoft SQL Server 2005 installation CD into the CD drive of the database server. (If AutoPlay should fail to run, select Run from the Start menu and type X:\SETUP (where X: is the drive letter of your CD drive). Click OK. Setup displays a Welcome dialog box, urging you to close any Windows programs and disable any antivirus software that may be running. Follow the instructions and then click Next. Setup displays a Software License Agreement. To accept the terms of the agreement, click Yes. Setup will install Microsoft SQL Server 2005 into the following folder: C:\Program Files\Microsoft SQL Server NOTE: Because Microsoft installs SQL Server 2005 to the C:\ partition on the database server, you should make certain that you have a significant amount of available storage space on the C:\ partition. SQL Server databases containing large numbers of records can grow to be several gigabytes in size and larger. It is possible to change the path to the database storage and backup folders to another volume with sufficient disk space. See Modifying Fortis Database Paths on page 6 for instructions. Setup has successfully installed the Microsoft SQL Server 2005 database server software. You must restart your database server machine so that Service Pack 2 for Microsoft SQL Server 2005 may be installed. Click Finish to exit Setup and restart the computer now. Once the database server has restarted and you have logged in to it, the install of Service Pack 2 for Microsoft SQL Server 2005 will automatically begin. Once Service Pack 2 for Microsoft SQL Server 2005 has been successfully installed, click Finish to exit Setup and restart the computer. Once the database server has restarted, you may now log in to the database server to begin the Fortis shared-client software install. INSTALLING FORTIS SHARED-CLIENT SOFTWARE Please refer to XInstalling Fortis Shared-Client SoftwareX located Xon page 29X

Fortis Installation Guide Page 23 INSTALLING FORTIS WORKSTATION SOFTWARE Once you have installed the Fortis database server software on your database server machine and installed the Fortis shared-client software to a network shared location, you can begin the process of installing the Fortis client software on each workstation that you plan to use to access Fortis. Please refer to XInstalling Fortis Workstation SoftwareX located Xon page 31X. INSTALLING FORTIS OPTIONS Please refer to XInstalling Fortis OptionsX located Xon page 39X. MODIFYING FORTIS DATABASE PATHS As discussed in XXInstalling the Fortis Database Server SoftwareX the Microsoft Embedded SQL Server is installed to C:\Program Files\Microsoft SQL Server. When a new Fortis database is created or backed up, they are also stored by default under subfolders of C:\Program Files\Microsoft SQL Server. It may be necessary or desirable for a Fortis administrator to specify a different storage location for the SQL Server databases and/ or backup files. An example of such an occurrence would be if the C:\ disk partition did not have enough free disk space to store the SQL Server databases created by Fortis. NOTE: The instructions below apply to changing the path for the creation of new databases and new backups only. For instructions on relocating existing databases and backups, please refer to Microsoft SQL Server Books Online which is installed on the Fortis database server. TO CHANGE THE STORAGE PATH FOR NEW FORTIS DATABASES: 1) Using Windows Explorer, browse to X:\FortisDT\SYSDATA (where X:\ is the network shared location of the Fortis shared-client server software.) 2) Open the DBS.INI file using Notepad and look for the following entry under the [DBSetup] section: DBDIR=C:\Program Files\Microsoft SQL Server\MSSQL$DBSERVER\DATA

Fortis Installation Guide Page 24 3) Replace the default path with the desired new path. This path must be entered relative to how the database server would see the path, NOT the Fortis shared-client server. For Example to change the path for newly created databases to F:\SQL_DATA you would make the following change: DBDIR=F:\SQL_DATA F:\SQL_DATA must be a valid path as seen by the database server. 4) Save the changes to DBS.INI and close the file. MODIFYING THE FORTIS DATABASE BACKUP STORAGE LOCATION: 1) Using Windows Explorer, browse to X:\FortisDT\SYSDATA (where X:\ is the network shared location of the Fortis shared-client server software.) 2) Open the DBS.INI file using Notepad and look for the following entry under the [DBSetup] section: DBBACKUPDIR=E:\Program Files\Microsoft SQL Server\MSSQL$DBSERVER\BACKUP 3) Replace the default path with the desired new path. This path must be entered relative to how the database server would see the path, NOT the Fortis shared-client server. For example, to change the path where database backups will be stored to E:\SQL_BACKUP you would make the following change: DBBACKUPDIR=E:\SQL_BACKUP E:\SQL_BACKUP must be a valid path as seen by the database server. 4) Save the changes to DBS.INI and close the file.

Fortis Installation Guide Page 25 INSTALLING FORTIS FOR MICROSOFT SQL SERVER INTRODUCTION Prior to installing Fortis for Microsoft SQL Server, refer to the Westbrook Technologies Web page at HHUhttp://www.westbrooktech.com/products/fortis/fortis_specifications.htmUH for a list of recommended minimum system specifications. You must also make certain that your network is set up and configured correctly. Be certain your database server and client stations are communicating using the appropriate communications protocol for your network configuration. The machine designated as the database server must be running Microsoft SQL Server 2000 or 2005. The server machine must be able to communicate over your network with the machines designated as the client or workstation machines. These workstations must be running Windows 2000 Professional SP4, Windows XP Professional SP 2 or Windows Vista Ultimate, Enterprise or Business Edition. The ODBC driver for Microsoft SQL Server must be installed on each workstation. Refer to your Microsoft SQL Server Installation Guide for instructions on installing this ODBC driver. Once the Microsoft SQL Server ODBC driver has been set up, always check the connectivity with the machine designated as the database server before proceeding. NOTE: If Fortis displays a message stating that your ODBC driver is too old, check the Fortis CERTDRV.INI file in the System Data folder for the minimum ODBC driver revision required. NOTE that this file contains a revision level for both the 16-bit driver and the 32-bit driver. The Fortis for SQL Server installation is in two parts: 1) The Fortis shared-client software is installed on a network drive that can be accessed by all your client workstations. 2) The Fortis client workstations are then configured to access both the client software and database server using a setup program run at the workstation from the shared network drive. NOTE: If you re using Fortis for SQL Server, you do not have an exclusive lock on a database. Make certain that all users have logged out of a database before performing any Database Administration functions, such as modifying or deleting Document Types, users, permissions, etc. Failure to do so may result in errors as well as data loss. The database administrator must have a minimum of create table privileges to perform many Fortis Database Administration functions.

Fortis Installation Guide Page 26 INSTALLING FORTIS SHARED-CLIENT SOFTWARE Please refer to XInstalling Fortis Shared-Client SoftwareX located Xon page 29X. INSTALLING FORTIS WORKSTATION SOFTWARE Once you have installed the Fortis database server software on your database server machine and installed the Fortis shared-client software to a network shared location, you can begin the process of installing the Fortis client software on each workstation that you plan to use to access Fortis. Please refer to XInstalling Fortis Workstation SoftwareX located Xon page 31X. INSTALLING FORTIS OPTIONS Please refer to XInstalling Fortis OptionsX located Xon page 39X. HELPFUL HINTS You only need to create a SQL Server logon for the owner of each Fortis database. You then must create a Fortis user account for that Fortis database owner. Always create the Fortis database owner s SQL Server user logon first before defining that user as a Fortis user. NOTE: The SQL Server username does not need to be set as the DB Owner in SQL Server. Once you add a user to the database, you maintain all user permissions within Fortis. The size of your Master Database should be at least 50 MB. By default, the size of your SQL Server Temporary Database (tempdb) is 2 MB, which is far too small to handle any production data. You should expand the size of the Temporary Database to at least 50 100 MB. If you do not back up the Transaction Logs on a regular schedule, be sure to set the Truncate Log on Checkpoint option to On. Before setting up any client workstations, be sure you can connect to the database server using the tools provided with SQL Server on a client. If you have a problem with a particular workstation, be sure you can connect using these tools on the workstation in question to be certain that your ODBC connection is set up properly.

Fortis Installation Guide Page 27 INSTALLING FORTIS FOR ORACLE INTRODUCTION Prior to installing Fortis for Oracle, refer to the Westbrook Technologies Web page at HHUhttp://www.westbrooktech.com/products/fortis/fortis_specifications.htmUH for a list of recommended minimum system specifications. You also must make certain that your network is set up and configured correctly. Be certain your database server and client stations are communicating using the appropriate communications protocol for your network configuration. The machine designated as the database server must be running Oracle 9i or 10g. The server machine must be able to communicate over your network with the machines designated as the client or workstation machines. These workstations must be running Windows 2000 Professional SP4, Windows XP Professional SP2 or Windows Vista Ultimate, Enterprise or Business Edition. Before you install Fortis, you must perform a connectivity test with the machine designated as the database server. Use TNSNAMES.ORA to verify the Service name. If you re using TCP/ IP, you can use SQL NET or SQL NET Easy Configuration to verify Service names. The Fortis for Oracle installation is in two parts: The Fortis shared-client software is installed on a shared network location that can be accessed by all your client workstations. The Fortis client workstations are then configured to access both the client software and database server using a setup program run at the workstation from the shared-client location. NOTE: If you re using Fortis with Oracle, you do not have an exclusive lock on a database. Make certain that all users have logged out of a database before performing any Database Administration functions, such as modifying or deleting Document Types, users, permissions, etc. Failure to do so may result in errors as well as data loss. The database administrator must have create table privileges to perform many Fortis Database Administration functions.

Fortis Installation Guide Page 28 INSTALLING FORTIS SHARED-CLIENT SOFTWARE Please refer to XInstalling Fortis Shared-Client SoftwareX located Xon page 29X. INSTALLING FORTIS WORKSTATION SOFTWARE Once you have installed the Fortis database server software on your database server machine and installed the Fortis shared-client software to a network shared location, you can begin the process of installing the Fortis client software on each workstation that you plan to use to access Fortis. Please refer to XInstalling Fortis Workstation SoftwareX located Xon page 31X. INSTALLING FORTIS OPTIONS Please refer to XInstalling Fortis OptionsX located Xon page 39X. HELPFUL HINTS Default and temporary table space size, as well as auto extents size, should be determined according to the needs and use of each Fortis database. Any user created in the Fortis System Administration Station that will become an owner of a Fortis database (a database administrator) MUST be created using all UPPERCASE characters because of case-sensitivity issues encountered in Oracle. The database administrator username created in Oracle must be unique for each Fortis database. You must create another user account in Oracle for each Fortis database administrator you want to create. Customers using Oracle 9i or 10g may wish to take advantage of a more efficient means of data access called scrollable cursors. To do this there are several changes that need to be made to a file located in the FortisDT\SYSDATA directory named CERTDRV.INI. The changes to the CERTDRV.INI file need to be made under the heading [Oracle in *]. Default CERTDRV.INI settings to be changed UseCursorLibrary=Y UseForUpdateClause=Y SetConnectOptions=6,3;7,4 New CERTDRV.INI settings to enable Scrollable Cursors support UseCursorLibrary=N UseForUpdateClause=N SetConnectOptions=6,1;7,3

Fortis Installation Guide Page 29 INSTALLING FORTIS SHARED-CLIENT SOFTWARE Before you install the shared-client software to a network shared location, make certain that the database server and all the client workstations you intend to use as Fortis workstations can access this network shared location. NOTE: If you are enabling Fortis Web with your Fortis installation, all paths will be set using UNC (Universal Naming Convention) instead of the mapped drive letter. TO SETUP AND CONFIGURE YOUR FORTIS SHARED-CLIENT SOFTWARE: 1) Insert the Fortis installation CD into the CD drive of the network machine you intend to use to access the shared network location. You will access this location to install the Fortis client software onto your Fortis client workstations. (If AutoPlay should fail to run, select Run from the Start menu and type D:\SETUP (where D: is the drive letter for your CD drive). Click OK. Setup displays a Welcome dialog box, urging you to close any Windows programs and disable any antivirus software that may be running. Follow the instructions and then click Next. IMPORTANT: Fortis Embedded SQL Server and Fortis SE shared-client installs must be run from the database server. The database server needs to have a drive mapped to the shared network location where the Fortis Shared-Client Software will be installed. 2) Setup displays a Welcome dialog box, urging you to close any Windows programs and disable any antivirus software that may be running. Follow the instructions and then click Next. 3) Setup displays a Software License Agreement. To accept the terms of the agreement, click Yes. 4) Setup asks you for some information about your installation. Type your name, your company name, and the serial number of your copy of Fortis. Click Next. 5) Setup now asks you if you want to register your copy of Fortis. To register, make sure the Register product now check box is selected and click Next. If you don't register Fortis now, you can only use it 25 more times before you must register it. However, you can choose to register the next time you launch the program. If you selected to register your copy of Fortis now, the Registration Information dialog box displays. Call Westbrook Technologies at 1-203-483-6666 to obtain your registration number, or fax your registration card and Machine ID to 1-203-483-3350 and your registration number will be faxed back to you. Once you've obtained your registration number, type your number in the box provided and click Next.

Fortis Installation Guide Page 30 6) Setup will install the Fortis shared-client software in a new location called X:\Fortis, where X: is your shared network drive. To accept this location, click Next. To install Fortis in a different location, click Browse and select a different folder, and then click Next. 7) You must specify a location to store Fortis system files. Setup will create an X:\FortisDT\SYSDATA folder, where X: is your shared network drive. This folder is the default location for system and database-related files that users read and write to. The folder will be created at the same level in the folder tree as your Fortis program files location. To accept this folder, click Next. To create a different data location, click Browse and select a different folder, and then click Next. 8) You must specify a default In Basket location. Setup will create an X:\FortisDT\INBASKET folder, where X: is your shared network drive. To accept this location, click Next. To create a different In Basket location, click Browse and select a different folder, and then click Next. 9) Setup asks you to select which components you want to install: Document Management and/or ERM. The component(s) you have purchased are indicated with a plus sign and selected with a check mark. Select the component(s) you want to install. Clear a check box if you don t want to install a component at this time. (You can install a component at another time, if necessary, by running Setup from the X:\Fortis\Setup folder.) Click Next. NOTE: The component dialog mentioned in Step 8 above does not appear on a Fortis SE install. ERM is not available with Fortis SE. 10) Setup displays a list of Fortis options. All of the options you have purchased are indicated with a plus sign and selected with a check mark. Clear a check box if you don't want to install an option at this time. (You can install options at another time, if necessary, by running Setup from the X:\Fortis\Setup folder.) Click Next. Note: If you are installing the OCR Languages option, an additional window displays where you can select the languages to install. 11) Setup displays a list of Fortis add-ons. All the add-ons you have purchased are indicated with a plus sign and selected with a check mark. Clear a check box if you don t want to install an add-on at this time. (You can install add-ons at another time, if necessary, by running Setup from the X:\Fortis\Setup folder.) Click Next. NOTE: Fortis Embedded SQL Server users will be prompted to specify the location of their Microsoft SQL Server installation before proceeding to Step 12. 12) Setup displays all the information you ve entered. Click Install to proceed with the installation. 13) The Fortis shared-client software install will proceed. A message displays when the installation is complete.

Fortis Installation Guide Page 31 NOTE: Fortis Embedded SQL Server and Fortis SE shared-client installs should disconnect the drive mapping to the Fortis shared-client server from the Fortis database server when the install is complete. INSTALLING FORTIS WORKSTATION SOFTWARE WORKSTATION SETUP IMPORTANT: All workstation installs should be run from the new \WkSetup directory only NOT from \Setup. IMPORTANT INFORMATION ABOUT MICROSOFT DATA ACCESS COMPONENTS (MDAC) The Fortis client software installation includes a version check of Microsoft Data Access Components (MDAC). If the Fortis client software install detects an older version of MDAC than what the Fortis workstation requires, it will install an updated version of MDAC. If you have any other services or programs running on the workstation that are dependent on any part of the MDAC library, you must verify that those services and programs are compatible with the updated version of MDAC before proceeding with the installation of the Fortis client software. Visit www.microsoft.com for more information on MDAC. IMPORTANT INFORMATION ABOUT WINDOWS VISTA USER ACCESS CONTROL (UAC) Windows Installer version 4.0 (MSI) complies with Windows Vista User Account Control (UAC). If a Windows Vista user chooses to do an All Users install it will only be performed if Administrator credentials are provided to the UAC dialog box. If UAC is enabled and valid Administrator credentials are not provided, the installation fails with an error stating that administrator privileges are required. If UAC is disabled by the registry key, group policy, or the control panel, the UAC dialog box is not displayed and the installation fails with an error stating that administrator privileges are required. If the user is a member of the local machine Administrators group then another option is to run the MSI install using the Run as administrator command. IMPORTANT INFORMATION ABOUT FORTIS ORACLE ON WINDOWS VISTA We have discovered an issue with the Oracle client installer on Windows Vista that may cause users problems with using OCR in Fortis. The Oracle client installer adds the location of the Bin directory to the beginning of the value string of the Windows Path Environment Variable. This information needs to be moved from the beginning of the Path value to the end of the string in order to ensure that the Fortis client will function normally.

Fortis Installation Guide Page 32 TO INSTALL FORTIS CLIENT SOFTWARE ON A WORKSTATION: 1) From the client workstation, access the shared network drive where you installed the Fortis shared-client software. Run SETUP.EXE from X:\Fortis\WkSetup where X: is your shared network drive and Fortis is your program folder. NOTE: Fortis Workstation Setup installs several prerequisites including Sun Java which is required to support the Fortis Document Viewer. It also installs several Microsoft supporting file components required for the Fortis Workstation to function properly. 2) Setup displays a Welcome dialog box, click Next. 3) Setup displays a list of features to select for installation based on what you have purchased. System Administration Administrators set up access to the Fortis software within System Administration. Database Administration Administrators create, design, and maintain Fortis databases within Database Administration. Scan Users can scan, import, or fax documents into the system, edit and index documents, perform searches, and view documents. Edit Users can edit and index documents, import and fax documents into the system, perform searches, and view documents. Users cannot scan documents. View Users can perform searches and view documents. Users cannot scan, edit or index documents. Script Manager Administrators use the Script Manager program to monitor scheduled Scripts. ERM Setup ERM Setup users define the layout of ERM documents and define new ERM Applications. (Not available in Fortis SE) ERM Process ERM Process users add documents to the Fortis ERM document warehouse. If ERM Process is selected, ERM System Monitor is also installed. (Not available in Fortis SE) Fortis Ascent - Installs supporting files and the Fortis Ascent Release Script if Kofax Ascent Capture is installed on the workstation. OCR- Supporting files needed for running OCR on a Scan or Edit Station.

F F install F and Fortis Installation Guide Page 33 4) Select the features you want to install. All of the options you have purchased are enabled for install by default. Choose the option This feature will not be available on any features you don t want to install at this time. (You can install options at another time, if necessary, by running Setup from the X:\Fortis\WkSetup folder.) Click Next. 5) Setup prompts you to click Install to begin the installation. To make any changes, click Back to return to the previous steps, where you can modify any settings. When you are satisfied that the information is correct, click Install. 6) If there are any files open by other applications that Setup needs to update a dialog will appear prompting you to either automatically close and restart the applications during Setup or you can choose to leave the applications open and Setup will prompt you to reboot the machine to complete installation. 7) A message displays when Setup is complete giving you the option to view the Windows Installer Log. You may be prompted to restart the computer before you can run Fortis. You can choose to reboot now or later. Click Finish to exit Setup. 8) Repeat steps 1 7 for each Fortis workstation. SILENT WORKSTATION SETUP 1 Fortis installs workstations using MSIFF F. The administrator scripts a Silent workstation F 3 Push F to a workstation using the Group Policy Editor or Microsoft Systems Management Server (SMS). 4 Note: Fortis does not currently support PublishFF F installs. 2 MSIEXEC Microsoft Windows Installer (a.k.a. MsiExec.exe): A command line executable that manages and interprets the MSIs that install, maintain, and remove applications on target systems. Click to view instructions on how to use MSIEXEC 1 Acronym for Microsoft Installer. 2 Silent installs do not display any user interface. 3 A remote install to a workstation on the network. 4 A Publish install assigns an application to a Group Policy object for installation to computer or user on a specific domain, site or organizational unit.

HHU Click F F of Fortis Installation Guide Page 34 Command line entry that sets the path for the MSI and the Fortis Shared Client directory: Example: {msiexec /qn /i \\w2k3s\apps\imaging\fortis\wksetup\fortis Workstation.msi SOURCEPARENT_PATH= \\ w2k3s\apps\imaging\fortis"} MSI Database Editor ORCA: Is a Microsoft MSI database editor that is provided as part of the Windows Installer SDK. It is the preferred editor to view/modify properties in the Fortis Workstation.msi. to view instructions on how to use ORCA.U HOW TO CONFIGURE A SILENT WORKSTATION SETUP Do the following to perform a Silent workstation setup: 1. HUHInstall the required FORTIS workstation Prerequisites.U 2. HUHSet the values for FORTIS workstation MSI properties.u 3. HUHConfigure Group Policy to perform a Push Install.U Required FORTIS Workstation Prerequisites Each Prerequisite, listed in the table below, is required and must be installed prior to running a workstation setup. When installing a Fortis workstation with Fortis Workstation.msi instead 5 of Fortis\WKSetup\Setup.exe...FF F, check Control Panel>Add/Remove Programs for any prior 6 installationf Prerequisites. If a required Prerequisite not installed, run its installer located in the Fortis\WKSetup\Prerequisites folder. Note: Prerequisites are deployed using original vendor installers. It is the Administrators responsibility to properly reinstall a modified, repaired, or uninstalled Prerequisite, before reinstalling or upgrading a Fortis workstation client. Please contact the original vendor for documentation or assistance in building an install package. Microsoft.NET Framework 2.0 Prerequisite Installer Name dotnetfx.exe Microsoft Data Access Components (MDAC) 2.8 Service Pack 1 mdac28sp1.exe Sun Java Runtime Environment 6 Update 2 Microsoft Visual C++ 2005 Redistributable Package FORTIS Workstation MSI Property Values Do the following to set the property values for Fortis Workstation.msi: SunJava.exe vcredist_x86.exe 1. In the ORCA editor, open Fortis Workstation.msi. The editor displays a Tables column in the left-frame and corresponding field columns in the right-frame. 5 Setup.exe automatically checks for and installs any missing Prerequisite. Fortis Workstation.msi does not. 6 Other applications may have previously installed Prerequisites.

Fortis Installation Guide Page 35 2. In the Tables column, select Property. The Property and Value field columns display in the right-frame. 3. Select to perform a Push or Silent install: If performing a Push install, in the Property table, add the property SOURCEPARENT_PATH: A. Right-click the right-frame. The shortcut menu displays. B. Select Add Row. The Add Row dialog box displays. C. In the Name column, select Property and enter the name: SOURCEPARENT_PATH. D. In the Name column, select Value and enter the Fortis root folder path: \\Server\Folder Path. Example: \\W2K3SDomain\Apps\Imaging\Fortis E. Click OK. If performing a Silent install, enter the following command line entry:{msiexec /qn /i \\w2k3s\apps\imaging\fortis\wksetup\fortis Workstation.msi SOURCEPARENT_PATH= \\ w2k3s\apps\imaging\fortis"} 4. Select the desired Property and assign a Value: Property Property Setting for Push/Remote Silent Install Public Properties to Install FORTIS Modules Value To Push a Silent install or perform a remote Silent uninstall, set the SILENT_PUSH value to TRUE. To Install a specific module listed below, set the corresponding public property value to SHOW. To Exclude a specific module listed below from installing, set the corresponding public property value to HIDE. Module/Feature Name Auto Logoff Configurator Fortis Ascent Fortis Document Management Fortis ecopy ShareScan OP Fortis ERM Fortis Office Full Text OCR QuickFind MSI Public Property Name ALOGOFF_INSTALLED ASCENT_INSTALLED DOCMGMT_INSTALLED ECOPY_INSTALLED ERM_INSTALLED OFFICE_INSTALLED FULLTEXT_INSTALLED OCR_INSTALLED QUIKFIND_INSTALLED

Fortis Installation Guide Page 36 Public Properties to Install FORTIS Features To Install a feature below set the properties as specified below =1. To Exclude a feature below set the properties as specified below =0. System Administration Set the Level entry for the SystemAdministration row in the Feature table Set the Value entry for the INSTALL_SYSADMIN row in the Property table Database Administration Set the Level entry for the DatabaseAdministration row in the Feature table Set the Value entry for the INSTALL_DBADMIN row in the Property table Script Manager Set the Level entry for the FScriptSrv row in the Feature table Print to MAG Set the Level entry for the PrintToMAG row in the Feature table Set the Value entry for the INSTALL_PRINTTOMAG row in the Property table

Fortis Installation Guide Page 37 Public Properties to Include FORTIS Workstation Types To Include a Fortis workstation type in the install, set the public property to SHOW. To Exclude a Fortis workstation type from the install, set the public property to HIDE. Fortis Workstation Type Fortis Scan Station Fortis Edit Station Fortis View Station MSI Public Property Name SCANSTAT_AVAILABLE EDITSTAT_AVAILABLE VIEWSTAT_AVAILABLE Set the Path to the SYSDATA Directory Specify the Windows Program Group Name Set the Path to the FORTIS Shared Client Directory Public Property for Setting User Preferences Set the following paths for the installer: Set the UNC path to the configuration files: Fortis SYSDATA. Example: \\W2K3SDomain\Apps\Imaging\FortisDT\SYSDATA Set the path to the System Data Directory: {Fortis Shared Client directory}\base.ini in the field SYSDATA_DIR. Specify the name of the Windows Start Menu folder. In FORTIS_FOLDER_NAME: Enter 0 for the default name: Fortis. Enter a custom name as the type: STRING. For Push installs, set the SOURCEPARENT_PATH variable to the root directory of the workstation install. Example: \\W2K3SDomain\Apps\Imaging\Fortis For an ecopy ShareScan install, set SHARESCAN_PATH to the ShareScan Bin directory and a WTI subdirectory. Example: C:\Program Files\eCopy\ShareScanOP\ShareScanOPManager\Bin\WTI To Set User Preferences, specify the path to the INI file containing the desired preference settings in PREFERENCE_INI_FILE Example: {path to the Fortis Shared Client Directory}\wksetup\silent\ScanSettings.ini 5. In the Menu bar, select Save>Exit. Please refer to Create Fortis Preferences INI located on page 38 for information on how to create a user preferences INI file. Use the default value SKIP if you do not wish to set any user preferences.

Fortis Installation Guide Page 38 CONFIGURING GROUP POLICY TO PERFORM A PUSH INSTALL Do the following to configure Group Policy on the Domain Controller: 1. Open the Group Policy Editor. 2. Select Computer Configuration>Software Settings>Software Installation. 3. Right-click Software Installation to open the shortcut menu: A. Select New>Package. The Open dialog box displays. B. Navigate file system to Fortis Workstation.msi and double-click to open. The Deploy Software dialog box displays. C. Leave the default setting: Assigned. 4. Click OK. CREATE FORTIS PREFERENCES INI Fortis 2.4.1 includes a new utility for Fortis Administrators to read the user preference settings on the current Fortis workstation and then write them to an INI file for use with a Silent or Push Workstation install. The utility is located here: \Fortis\CreateIni.exe STEPS TO CREATE A PREFERENCES INI 1. On an existing Fortis Workstation set all General & Annotation Preferences the way you want them to be written to the INI file. 2. On the same Fortis Workstation from Step 1, browse to the Fortis Shared-Client Server install directory and run CreateIni.exe 3. The Create Fortis Preferences INI utility will prompt you to enter a path and filename for the INI file. Browse to or enter a valid path and filename. Click OK. 4. The utility will save the INI file using the specified location and filename. The newly created INI file can now be used to set User Preferences via a Fortis Silent or Push Workstation Setup.

Fortis Installation Guide Page 39 CDEXPRESS WORKSTATION SETUP Customers who have purchased the CDExpress option need to setup the workstation(s) that they will use to create CDExpress recordings. 1. Install or Upgrade the Fortis Shared-Client Server to version 2.4.1. 2. On the client workstation that will perform CDExpress recordings, run a Fortis Workstation setup using the steps outlined in the topic XInstalling Fortis Workstation SoftwareX located on page X29 X X. 3. From the client workstation, access the shared network drive where you installed the Fortis shared-client software. Run CDExpress-2.4.1-Workstation.exe from X:\Fortis\WkSetup where X: is your shared network drive and Fortis is your program folder. 4. IMPORTANT: To complete the CDExpress Workstation Setup, please follow the instructions included in the topics XSYSADM User Default Password ChangeX and X XFortis CDExpress CustomersX. INSTALLING FORTIS OPTIONS Fortis allows for future upgrades and enhancements. Optical Character Recognition (OCR), Bar Code, Full Text Indexing, Image Enhance, Fortis Web, and Fortis Inflo are optional products that you may find the need to install at a later date. You may need to install an additional component (Document Management or ERM). Additionally, you may need to increase your seat count or apply a revision update from Westbrook Technologies, Inc. All of these items require the administrator to run a setup procedure. The following instructions guide you through that process. NOTE: If you are installing options or a component from your original purchase that you chose not to install initially, then you should use the configuration located on your original installation CD and not the new disc referred to in the instructions below. TO INSTALL OPTIONS FOR YOUR FORTIS CLIENT SOFTWARE: 1) From a client workstation, access the shared network drive where you installed the Fortis shared-client software. Run SETUP.EXE from X:\Fortis\Setup where X: is your shared network drive and Fortis is your program folder. 2) Setup displays a Welcome dialog box, urging you to close any Windows programs that may be running. When you ve finished reading, click Next.

Fortis Installation Guide Page 40 3) Click the Install Options button and click Next to continue. 4) Enter the path of the New Options configuration files. Click Next to continue. 5) Setup will prompt you for the location of your Fortis CD. Click Next to continue. 6) A summary of available options displays. Those marked with a plus sign are available for installation. Select the check box next to the option(s) to install. Click Next to continue. NOTE: If you are installing the OCR Languages option, an additional dialog box displays where you can select the languages to install. 7) Setup displays a list of Fortis add-ons. All the add-ons you have purchased are indicated with a plus sign and selected with a check mark. Clear a check box if you don t want to install an add-on at this time. (You can install add-ons at another time, if necessary, by running Setup from the X:\Fortis\Setup folder.) Click Next to continue. 8) Setup displays all the information you ve entered. To make any changes, click Back to return to the previous steps, where you can modify settings. When you are satisfied that the information is correct, click Next. NOTE: Setup may display the following message when it finishes copying files: 9) One or more of your newly installed options may require any system using it to run a Workstation Setup before it will run correctly. Click OK to continue. 10) Setup has successfully installed the Fortis options. TO INSTALL A SECOND COMPONENT FOR YOUR FORTIS CLIENT SOFTWARE: 1) From a client workstation, access the shared network drive where you installed the Fortis shared-client software. Run SETUP.EXE from X:\Fortis\Setup where X: is your shared network drive and Fortis is your program folder. 2) Click the Install Component button and click next to continue. 3) Enter the path of the New Component configuration files. Click Next to continue. 4) Setup will prompt you for the location of your Fortis CD. Click Next to continue.

Fortis Installation Guide Page 41 5) A summary of available components displays. Those marked with a plus sign are available for installation. Select the check box next to the component to install. Click Next to finish the installation. 6) Setup has successfully installed the Fortis component. TO INCREASE THE USER COUNT FOR YOUR FORTIS INSTALLATION: 1) From a client workstation, access the shared network drive where you installed the Fortis shared-client software. Run SETUP.EXE from X:\Fortis\Setup where X: is your shared network drive and Fortis is your program folder. 2) Click the Increase User Count button and click Next to continue. 3) Enter the path of the New Additional Users configuration files. Click Next to continue. 4) Setup displays a dialog box stating Additional Users updated to indicate the installation is complete. Click OK. 5) Setup has successfully installed the additional user count on your system.

Fortis Installation Guide Page 42 INSTALLING THE FORTIS WEB SERVER IMPORTANT: Fortis Web minimum system requirements are Windows Server 2003 SP2 with Internet Information Services (IIS) 6.0. NOTE: The following steps must be performed from the Fortis Web Server machine. 1) Confirm Windows Scripting Host is installed. (This is part of the default IIS installation.) 2) Confirm that ASP.NET 2.0 in installed and enabled for the Fortis Web virtual directory. 3) Make sure that all users have exited Fortis. 4) Make sure that all connections between the web server and the shared-client server have been terminated. 5) Open Internet Information Services (IIS) Manager and stop the IIS Server. 6) Back up your Fortis program folder (e.g., X:\FORTIS). 7) Insert the Fortis 2.4.1 CD into your CD drive. If AutoPlay is enabled, exit the startup screen. Run Setup from the Fortis Web folder on the CD, (e.g. E:\FORTISWEB\SETUP.EXE). 8) Setup asks you to enter the existing Fortis shared-client software folder on your network (e.g. X:\FORTIS). 9) Setup prompts you to select a location to install the Fortis Web Server files. The default location is C:\PWSITES. 10) Follow the remaining on-screen instructions to complete the install. 11) Once the install is complete you need to Configure IIS to allow access to the Fortis Web Extension DLL. In the IIS Manager, locate the Fortis Web folder under Default Web Site. Right-click the Dll folder and select Properties. The Dll Properties dialog box displays. Click Create, and then enter Dll as the Application name. From the Execute permissions list, select Scripts and Executables. Click OK on the Dll Properties dialog box. In the IIS Manager, select the Web Service Extensions folder. Click Add a new Web service extension. The New Web Service Extension dialog box displays.

Fortis Installation Guide Page 43 In the Extension name box, type FortisWeb. Click Add, and browse to the location of the PwrWbExt.dll file. Select the Set extension status to Allowed check box, and click OK. 16) Open Internet Information Services (IIS) Manager and restart the IIS Server. 17) To confirm that the install of Fortis Web executed successfully, type the address for the Fortis Web home page in Internet Explorer on your IIS server to verify access to the Fortis Web home page. NOTE: On the IIS Server hosting Fortis Web the default Fortis Web page is HHUhttp://localhost/FortisWebU 18) Please refer to the new Fortis Web Admin Help and Fortis Web User Help for more information on configuring and using Fortis Web.

Fortis Installation Guide Page 44 INSTALLING THE FORTIS WEB CLIENT ACTIVEX CONTROL The Fortis Web ActiveX control enables your end users to run the Fortis Web Edit or View client right inside Internet Explorer 6.0 or 7.0. When you install the Fortis Web server option, the browser ActiveX control is installed in the Fortis\PWSITES\DefSite\PWFiles directory. When an end user without the ActiveX control installed connects to your Fortis Web site and attempts to open a document, Fortis Web automatically installs the ActiveX control. When the ActiveX control installation completes, the end user can open a Fortis document via Fortis Web in their browser window. FORTIS WEB CLIENT ACTIVEX SECURITY SETTINGS The Fortis Web ActiveX controls are digitally signed and will authenticate as genuine software under Microsoft Internet Explorer 6.0 and above. The set of Fortis Web Active X controls distributed in Fortis 2.4.1 Service Pack 4 and above have been updated and will now also run using the default security settings recommended by Internet Explorer. IMPORTANT: Changing Internet Explorer security settings may expose your computer to increased risk of security threats. The security settings changes described below are recommendations only; please contact your system administrator or IT help desk before making any changes to Internet Explorer security settings. NOTE: Fortis Web clients running on Windows Vista will not be able to export documents if Windows Vista User Access Control (UAC) and Internet Explorer Protected Mode are enabled. UAC and Protected Mode restrict user privileges including blocking of write access to the local hard disk. There are three possible solutions to this issue; 1. Open IE7\Tools\Internet Options\Security and add the Fortis Web website to the Trusted Sites zone. (Automatically disable IE Protected Mode for this website only) 2. Run Internet Explorer as Administrator (Automatically disables IE Protected Mode during this session only) 3. Open IE7\Tools\Internet Options\Security and uncheck the checkbox for Enable Protected Mode for the zone Fortis Web is accessed from. (Manually disables IE Protected Mode in that zone for the user)

Fortis Installation Guide Page 45 PRINT-TO-MAG DRIVER The Print-To-MAG printer driver lets a Fortis user convert text documents, or images in other formats, into the Fortis document format while running the other application. Fortis users can then insert these images as pages in new or existing Fortis documents, or forward the newly created document files to a specified folder or a Fortis In Basket for further processing. The Print-To-MAG driver is also used to support the Export to TIFF option, if Print-To-MAG is not installed then the Export to TIFF option will not be available in Fortis. INSTALLATION For Fortis client workstations running Windows XP Professional and Windows Vista, Fortis automatically installs the Print-To-MAG printer driver when you install the Fortis application by running workstation setup. DISTRIBUTION Fortis provides a separate installer for Print-To-MAG in the Fortis\NTPRINT folder. Browse to the folder and run Setup.exe which invokes the Print-To-MAG Setup procedure and installs the necessary files for the Print-To-MAG driver onto the machine. This Print-To-MAG printer driver is supported on Windows XP Professional and Windows Vista and can be freely distributed to anyone, even users and organizations who don t own Fortis. Any user with this driver can create a Fortis document from any Windows application by printing the document using this driver. NOTE: Customers who need a version of Print-To-MAG that will install on Windows 2000 Professional can browse to the Fortis\NTPRINT2000 folder and run PrintMag.exe

Fortis Installation Guide Page 46 UNINSTALLING PRINT-TO-MAG WINDOWS 2000 The following provides step by step instructions for removing an existing install of the Print To Mag (Fortis Document) printer from a Windows 2000 machine. 1) Delete the PrintToMag folder (Default location is C:\Program Files\PrintToMag) 2) Go to Control Panel -> Printers 3) Delete the Fortis Document Printer (if it still exists) 4) Open the File menu and select Server Properties 5) Check the Ports tab and verify that the MAG1 port has been removed 6) Check the Drivers tab and verify that the Fortis Document printer driver has been removed. 7) Delete %WINDIR%\System32\Printmag.dll (%WINDIR% represents the location of the Windows OS directory on the computer, the typical default is C:\Windows)

Fortis Installation Guide Page 47 INSTALLING FORTIS 2.4.1 SERVICE PACK 4 Fortis 2.4.1 Service Pack 4 includes quality improvements and new features that enhance reliability, security and performance. It is recommended that all customers upgrade to Fortis 2.4.1 Service Pack 4 to take advantage of these improvements. IMPORTANT: The Windows logon used to install the service pack must have Administrative Access to the Fortis Shared Client Server directories and must have local Administrator access to all Fortis Workstations to install the workstation patch. IMPORTANT: Please make sure that all users are logged out of Fortis and that all other Fortis modules and servers such as Fortis Web, Inflo, Script Manager, ERM, etc. are shutdown and any related Windows Services are stopped before you begin installing the Service Pack. This also includes all users, servers and Windows Services that are accessing Fortis remotely across a Wide Area Network (WAN). Customers may also wish to make a backup of their Fortis installation before proceeding. NOTE: Beginning with Service Pack 4 the service pack installer will now output two files to the SYSDATA directory, remove.ini and rename.ini. These files will be used to record the list of critical Fortis application files that are either removed (deleted) or renamed during the install of the Service Pack. These files can be used to help troubleshoot in the event that you run into problems during the service pack install. Service Pack installation is done in two parts (Three parts if Fortis Web is installed) 1. From a Fortis Workstation run Fortis 2.4.1 SP4.exe. You may be prompted for the location of the Fortis Shared Client Server directory. Browse to the Fortis Shared Client directory and click OK to continue. NOTE: Please make sure you have downloaded the required IDX file and placed it in the same location as the Service Pack Installer before you begin. 2. (Customers who previously installed 2.4.1 Service Pack 2 or 2.4.1 Service Pack 3 and ran workstation setup can skip this step after installing 2.4.1 Service Pack 4) From each Fortis workstation, browse to the Fortis\WkSetup folder on the Fortis Shared Client Server and run Setup.exe to start a Fortis Workstation Setup. NOTE: You can also do a silent or push install using the MSI installer to update the workstations after installing the service pack to the Fortis Shared Client Server. See the Silent Workstation Setup topic located on page 33 for more information. Fortis Web Installations Only On installs that include Fortis Web, Fortis 2.4.1 SP4 will install several updated files for the Default and DefPOST websites. After 2.4.1 SP4 is installed you must copy the appropriate file(s) From the specified source location To the correct destination as instructed below. (Where X: is your shared network drive and Fortis is your program folder) Copy (GenFunc.js & LoginLDP.fht) From: X:\Fortis\WkSetup\WebSites\Template\Default Copy To: Default Template directory on the Fortis Web Server (Example: C:\PWSITES\DefSite\Template\Default)

Fortis Installation Guide Page 48 Copy (LoginLDP.fht) From: X:\Fortis\WkSetup\WebSites\Template\DefPOST Copy To: DefPOST Template directory on the Fortis Web Server (Example: C:\PWSITES\DefSite\Template\DefPOST) Copy (App_Web_picklistbrowser.aspx.cdcab7d2.dll & picklistbrowser.aspx.cdcab7d2.compiled) From: X:\WKSetup\WebSites\Bin) Copy To: Default Bin directory on the Fortis Web Server (Example: C:\PWSITES\DefSite\Bin) NOTE: The Fortis Web ActiveX Installers (FortisWebActiveX.exe and FortisWeb.cab) need to be downloaded from our website and copied to the PWSITES\DefSite\PWFiles directory on the Fortis Web Server. NOTE: Please make sure that any Read Only attributes have been removed from all the files that have been copied to the Fortis Web Server. You must then restart IIS. IMPORTANT INFORMATION FOR SPANISH LOCALIZATION FORTIS WORKSTATION REGIONAL SETTINGS FOR SPANISH Customers who wish to run Fortis localized in Spanish must perform the following steps; 1. Install or Upgrade to Fortis 2.4.1 2. Install Fortis 2.4.1 Service Pack 4 3. Run Workstation Setup on all Fortis Workstations 4. On each Fortis Workstation, Set your Regional Options Locale to Spanish a. Windows XP Navigate to Control Panel\Regional and Language Options. On the Regional Options tab select Spanish in the Standards and Formats dialog. b. Windows Vista Navigate to Control Panel\Regional and Language Options. On the Formats tab select Spanish as the Current Format. MICROSOFT SQL SERVER 2005 EXPRESS INSTALLATION IMPORTANT: These installation instructions apply to the following Fortis product installs that use Microsoft SQL Server 2005 Express. Fortis SE, Fortis Embedded SQL Server, Fortis Demo Install, Fortis CDExpress Workstation Install and Fortis CDExpress View Station Install. Before running any of these installs a new local Windows Group needs to be created called Users with all the same user accounts that are in the Windows Group Usuarios. This is to ensure that all the correct folder permissions are applied during the install of the Microsoft SQL Server 2005 Express.

Fortis Installation Guide Page 49 FORTIS WEB SERVER TEMPLATES FOR SPANISH On installs that include Fortis Web, Fortis 2.4.1 SP4 will install a new directory that contains translated files needed by the Fortis Web Server to support Spanish. After 2.4.1 SP4 is installed you must copy the appropriate file(s) From the specified source location To the correct destination as instructed below. Alternatively you can copy the installed PWSITES directory to another location and then copy the Spanish localized files into the new copy of PWSITES and configure the Fortis Web Server to use the new directory. This would give you the option to setup separate virtual directories for English and Spanish Fortis Web sites. NOTE: You must stop IIS before copying the files. Copy all Files and Subfolders From: X:\WKSetup\WebSites_Spanish\) Copy To: DefSite directory on the Fortis Web Server (Example: C:\PWSITES\DefSite) (Where X: is your shared network drive and Fortis is your program folder) NOTE: Please make sure that any Read Only attributes have been removed from the files that have been copied to the Fortis Web Server. You must then restart IIS. CONFIGURING FORTIS ECOPY SSOP FOR SPANISH 1. Installing 2.4.1 Service Pack 4 will create an ecopy_spanish subfolder under \WKSetup. 2. Copy the contents (Data and Lib folder) to where the ecopy connector is installed: <Program Files>\ecopy\ShareScan OP\ShareScanOPManager\Bin\WTI 3. Register the WTIOpConnectES.dll in the Lib folder using Regsrv32.exe NOTE: The Spanish and English versions of Fortis ecopy SSOP have different files names and will not conflict with each other. However, only one version of the connector can be used at any given time. To switch to English, register WTIOPConnect.dll. To switch to Spanish, register WTIOPConnectES.dll

Fortis Installation Guide Page 50 UNINSTALLING FORTIS OFFICE SEND TO FORTIS BUTTONS In some cases uninstalling a Fortis Workstation that includes Fortis Office may fail to properly remove all of the Send to Fortis buttons from the various MS Office applications. There are currently 3 known cases when the removal of the Send to Fortis buttons might fail during uninstall of Fortis Office. 1. Running uninstall with any of the MS Office applications still running. 2. MS Word is still running but hidden and only visible via task manager such as running MS Outlook and using Word as the email editor. 3. Situations where Normal.dot or the Word 2007 equivalent (buildingblocks.dotx) needs to be updated / saved but a running WINWORD.EXE process is preventing the save. The instructions below provide the information necessary to manually remove the Send to Fortis buttons. Follow the appropriate steps for your version of Office. The screenshots are for reference and may differ slightly depending on the application and its version. OFFICE 2000, XP, 2003 WORD: 1. Select Templates and Add-Ins from the Tools menu

Fortis Installation Guide Page 51 2. Go to the Templates tab and click on Organizer 3. Go to the Toolbars tab and select the Fortis toolbar and click on Delete 4. Repeat if the Fortis toolbar appears in multiple locations

Fortis Installation Guide Page 52 EXCEL, POWERPOINT, AND OUTLOOK: 1. Select Customize from the Tools menu 2. Go to the Toolbars tab 3. Select the Fortis toolbar 4. Click on Delete

Fortis Installation Guide Page 53 OFFICE 2007 WORD, EXCEL, AND POWERPOINT: 1. Click on the Add-Ins tab 2. Right click on the Send To Fortis button 3. Click on Delete Custom Toolbar OUTLOOK: 1. Select Customize from the Tools menu 2. Go to the Toolbars tab 3. Select the Fortis toolbar 4. Click on Delete 5. Click on New to compose a new email message 6. Click on the Add-Ins tab 7. Right click on the Send To Fortis button 8. Click on Delete Custom Toolbar