Concordance Desktop Installation Guide. Preliminary Planning Installing Concordance

Transcription

1 Concordance Desktop Installation Guide Preliminary Planning Installing Concordance

2 Concordance Desktop Installation Guide No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval system, without permission. While the information contained herein is believed to be accurate, this work is provided "as is," without warranty of any kind. The information contained in this work does not constitute, and is not intended as, legal advice. LexisNexis and the Knowledge Burst are registered trademarks of Reed Elsevier Properties Inc., used under license. Concordance is a registered trademark and FYI is a trademark of LexisNexis, a division of RELX Inc. Other products or services may be trademarks or registered trademarks of their respective companies. Concordance Desktop 1.5 Document Publish Date: Thursday, December 21, 2017 Product Release Date: November 14, 2017

3 Table of Contents 3 Table of Contents Chapter 1 About 6 Chapter 2 About Licensing and Product Activation 10 Chapter 3 What's New in 16 Chapter 4 Installing Preliminary Planning About the discovery process 22 Preparing for Installation Recommendations Additional Recommendations 35 Preparing for... Preparing for... on a Server 35 Best practices... for planning 36 Data hosting Netw ork directory... setup 39 Working w... ith 41 System requirements Server setup... and user management 43 Best practices... for server setup 47 Concordance... Desktop server security 50 Ongoing maintenance Scheduling... administrative tasks 54 Backups and... data recovery 56 Updating considerations Installing Before installing Installing Activating/Resetting a Server or Mobile license Installing language packs Registry key locations Performing silent installs Customizing the start-up view Upgrading shortcut (.fyi) files Chapter 5 Reference Information Keyboard shortcuts

4

5 Installation Guide About Chapter 1

6 6 About Concordance Desktop is a tool that provides electronic discovery, litigation document management, and litigation support. It was designed to make it easier to identify, organize, analyze and maintain case-critical information so that you can collaborate and share across your firm, or around the world. provides the means by which a small to mid-sized law firm can control and maintain the documents that are pertinent to their cases. can manage up to 2048 databases. Should your database count exceed this number, we recommend archiving some of your databases that are not active, or using an enterprise tool to manage your databases. All the functionality needed to create, maintain, store, and work with databases, as well as reviewing, marking up, and redacting, and general production functionality of your documents is available in, and can be turned on with varying licenses. There are two types of licensing; Application and User Level. Application licenses are used to activate your installation of as either a Server or a Mobile installation. User Level licenses are used to provide access to varying levels of functionality. There are several user level licenses that affect three different types of users; Administrators, Full Reviewers, and Data Reviewers. All documents for a case can be imported into one or more databases by an Administrator. Once a database is created, it can be accessed by Data Reviewers for first level searching, record categorization, and folder, tags and issues creation. The database can also be accessed by Full Reviewers for searching and marking up documents pertinent to their cases, and for setting up documents they need to send to opposing council. For more details about licensing and how it works, please see the About Licensing and Product Activation topic. Basic key benefits and features provides the most effective, cost-efficient way to manage the high volume of documents scanned paper, and other e-documents generated during litigation. Here are som e of the basic key benefits and features of : A repository that holds documents of all types A fast and efficient search engine Ability to categorize records with folders, tags, and issues Ability to secure confidential data at various administrative levels Ability to integrate with other litigation technology Here are som e of the key benefits and features when installed on a network serv er or com puter: A secure, centralized location for your document databases Local Area Network (LAN) and Wide Area Network (WAN) access from workstations on which software is installed

7 About 7 Server functionality uses highly optimized data compression. Server functionality provides RSA encryption for efficient and secure remote access. This is the same RSA 128-bit encryption that banks use for securing online transactions. A Server license is required to enable Server on a server, or a network computer that you want to use as a the server. When that license is activated, two Server services are started; Server and Admin Server. The Server service sends data to Data Reviewer and Full Reviewer users on the network. This is where most of the review work is done. Admin Server service works with the Admin Console to control the server, database access assignments, and user management. The Administration Console provides a user interface to manage server functionality, allowing administrators to publish databases, restrict access and change user settings, set performance parameters, and generate usage reports. Document review key benefits and features provides an easy to use interface and markup tools for the review process. You can view markup history as well as document and image information without having to switch back to the main window. Document review typically involves searching for and marking up documents: Relevant for turning over to opposing counsel. Containing privileged or confidential information that you do not want turned over to opposing counsel. Containing evidential information to support your case. The docum ent rev iew key benefits and features of are: An intuitive user interface for navigating and reviewing documents A single Image Base (CIB) SQLite database file to store both native and image information Advanced markup tools to review and annotate documents and images Track document markups added or removed during a review Produce color or grayscale images to PDF or TIFF Database capacity Database Capacity Number of databases 2048 Number of documents 500,000 Concatenated databases You can join up to 128 databases Fields 250 custom fields Characters per field 12 million

8 8 Database Capacity Database.ivt file 6 gigabytes Database.tex file 6 gigabytes Product integrations integrates with other leading industry technology tools and providers to assist you in maximizing the functionality you currently have in managing your case records and history, while allowing you to add on or transition data to other programs as you move through the litigation process. also integrates with the following tools: Hosted servers CaseMap LAW PreDiscovery Sanction version 2.9 only Microsoft Excel

9 Installation Guide About Licensing and Product Activation Chapter 2

10 10 About Licensing and Product Activation While all functionality is installed with every installation of, it is the licensing that determines what level of functionality is available to the users. Every installation of is capable of being licensed as a server (on a networked computer) or a stand-alone setup (on a single computer); and every installation can be used as a work station for a Administrator or Reviewer. There are five basic types of licenses; two are application licenses (server and mobile) that designate the computer as a server for multiple users across a network, or as a server for one user on their individual computer, and the remainder are user licenses that when added to a server can be used to perform administrator or reviewer tasks. Application licenses Application licenses are applied to only one computer, and allow for that computer to be used as a database server. Once an application license is activated on a computer, it is tied to that computer and cannot be used or moved to another computer. There are two different types of application licenses: Application license Description and functionality Server Used to activate server functionality on a networked server or workstation computer. Mobile Used to activate server functionality, and enable all Concordance Desktop user functionality on a single computer, for use by only one user. Server license overview A Server license is required to activate a installation as a Concordance Desktop database server, on a Local Area Network (LAN) or Wide Area Network (WAN). It is a "non-concurrent" license, meaning it can be used to activate only one server. If you need to setup multiple database servers, you will need a separate Server license for each computer you are going to use as a server. A Server license is most beneficial for small to medium sized firms that have a network environment, and/or the need for multiple users to work on the same case. It allows for multiple users to open and work on the same database at the same time. All databases created on a Server licensed computer are "owned" by that server, meaning that all setup is stored on that server and all access to those databases is controlled by the licenses added to that server. At least one server license must be purchased and activated on a computer (server or workstation) in order to allow for databases to be created on that computer. Mobile license overview A Mobile license is required to activate server functionality, and enable all user functionality on a single computer, for use by only one user. It is a non-concurrent license, meaning it can be used to Activate and enable functionality on only one computer. Usually, this is a computer that does not attach to a network.

11 About Licensing and Product Activation 11 A Mobile license is most beneficial for: Small firms having only a few or less users who handle every aspect of the review process themselves, and who have no need to share their databases with others in the firm Firms that have no network LAN or WAN setup, or have no need to work with Concordance Desktop databases on a network Firms that may or may not be on a network, but in which each user prefers to have all information pertinent to their case on one computer; maybe a computer that they can take with them to court Users with a Mobile licensed installation still have the capability to access databases on a network if they need to, but the databases they create on their own computer stay on their computer, and are not readily accessible by others. Note that at any point in time, a mobile licensed installation of can be changed to a Concordance Desktop database server by simply purchasing and activating a Server license on the current Mobile licensed computer, and of course attaching the computer to a network. This makes it convenient for those who prefer to have their own databases to work with and then after their case is over, would like to move the database to an archive server for safe keeping. The main difference between a Server and Mobile license is that a Mobile license turns on ALL functionality (Server, Administration and Full Reviewer) for a single user on a single computer, whereas a Server license turns on only Server functionality on a network computer (server or workstation). Distinctions between Mobile and Server installations: Mobile versus Server Differences RAM used for processing searches, indexing databases Set IP address restrictions for connections Mobile Server End-user machines Server Load data Reset password for all user s databases Broadcast messages to online users Kill user sessions Set Job Schedules Track Usage History Send Watchdog Notifications Can take databases offline

12 12 Mobile versus Server Can accept connections from other users A database can be opened by multiple users at the same time User licenses User licenses work a bit different than application licenses. They are used to access different functionality in. A single User license, for the most part can be used by multiple people, as long as they do not attempt to all use the same license at the same time. User licenses are added to a database server through the Administration Console, and are available for use by any user who has the proper log in credentials to access the server and/or a database on that server. There are three different types of user licenses: User license Description and functionality Administration Enables any user who has installed on their computer, to perform administration functions as well as Full Reviewer functions. Full Reviewer Enables any user who has installed on their computer, to perform Full Reviewer functions, as well as basic Data Reviewer functions. Data Reviewer Enables any user who has installed on their computer, to perform Data Reviewer functions. User licenses are based on availability, meaning how many licenses are available for a specific type of user on a server, when that type of user attempts to log into that server. If a license is not available, the user is granted the next access level down from the one to which they are assigned on that server. For example, if an administrative user attempts to log into a database server and there are no Administration licenses available at that time, that user is granted access using the next license down, which is a Full Reviewer license. If a Full Reviewer license isn't available at the time, then they are granted access using the Data Reviewer license. If a Data Reviewer license is not available at the time, then the user is unable to gain access to the server or it's databases until a license is available. This holds true for all user licenses. Administrator license overview An Administrator license provides access to the databases, and all database and user administration features. Administrator users can create and maintain databases, users, user settings, user groups, matters, and clients. In addition they have access to the same features as a Full Reviewer, meaning they can also review documents in browse view or in the viewer (which displays a PDF image of the actual document), markup documents in the viewer, search, categorize records, and create folders, tags and issues. Administrator licenses are "concurrent" meaning, one license can be used by multiple users, but not at the same time.

13 About Licensing and Product Activation 13 Full Reviewer license overview A Full Reviewer license provides access to the databases for review purposes. Full Reviewers can review documents in browse view or in the viewer (which displays a PDF image of the actual document), markup documents in the viewer, search, categorize records, and create folders, tags and issues. Full Reviewer licenses are "concurrent" meaning, one license can be used by multiple users, but not at the same time. Data Reviewer license overview A Data Reviewer license provides access to the databases for review purposes. Data Reviewers can perform the same tasks as Full Reviewers, with the exception of viewing and marking up documents in the viewer. They can review documents (in browse view only), search, categorize records, and create folders, tags and issues. Data Reviewer licenses are "concurrent" meaning, one license can be used by multiple users, but not at the same time.

14

15 Installation Guide What's New in Chapter 3

16 16 What's New in The following enhancements are included in the version 1.02 release. For more release information, see the Release Notes. v1.05 Export production control statements to a log file Ability to export a log file including errors in control statements. Option to overwrite data for production fields Ability to append or overwrite existing data in the production number fields. Name Production images after an existing field Option to use existing field values to number production images. Update image base with new load file Ability to overwrite image path based on the contents of an image load file. Enhanced Database Administration Settings Ability to omit new databases from the All Users Group Matter in the Admin Console. Windows Server 2016 Certified v1.04 Enhanced Admin Console authentication Administrators can authenticate users logging into the Admin Console on the server. Ability to append load files directly to an existing database Introduced the ability to append DAT files directly to an existing load file database. Production fields are included in the standard templates when creating databases. The BEGPRODNO and ENDPRODNO fields are now included in the Load File, Edocument, and Attachments and Transcript standard templates. Added additional fields in E-document and databases Added new metadata fields in the E-document and and Attachments database templates. Support for Office 2016 PST files Office 2016 PST files can now be imported into and Attachments databases. v1.03 Ability to import text using a field within the load file When an OCR path field is populated in the DAT file it can be selected as a method of importing text into OCR field(s). Export CCITT Group 4 black and white tiff images will now export all black and white tiff images with CCITT Group 4 compression. Load file import performance improvements Import performance improvements. v1.02

17 What's New in 17 Fast, streamlined, robust load file import Import load files faster without normalizing data (near native PDF creation), for both new databases and migrated 10.x databases Ability to Optimize (reprocess) record(s), batches, or an entire database Allows for documents to be optimized (reprocessed to PDFs) to increase performance or to view trouble documents Continued user interface update and refresh Update and refresh user interface windows for ease of use, and more current visual appeal Direct LAW integration Create databases directly from LAW PreDiscovery (v6.11) v1.01 New DAT Overlay feature Provides administrators with ability to update existing records in a database Provides administrators with the ability to update existing records in a set of Concatenated databases Provides a partial Preview of the DAT overlay file in the customize box Provides administrators with ability to drag and drop records updates and append new records New Customize logs feature Provides administrators with the ability to easily customize logs Provides administrators with easy access to Server and Client log folders directly from the Admin Console Windows 10 compliant can now run on a Windows 10 machine Microsoft Windows Server 2012 compliant can now run on a Windows Server 2012 Removed synonym.cpl from the CPL folder v1.00 New Admin Console Provides administrators with better insight into, and control over, databases and administration tasks. New Manager allows you to see, manage, and track your databases in a simple, sortable table. New Load file and Import Engine Provides a simple, easy and intuitive import interface The Import Engine automatically OCRs data for the client, standardizing on PDF. The Import Engine is significantly faster than the Concordance import, and allows for scaling to increase performance.

18 18 New Bates stamping at import Allows administrators to Bate Stamp documents at import and have those branded for tracking and recording purposes and saves time by eliminating the need to do it through a vendor or processing software first. Unification of Concordance product line Unified Concordance, FYI, and Concordance Native Viewer products which provides a WAN based product that allows clients to operate over the internet without having to separately run and install FYI and FYI Reviewer Streamlined single install Multiple installations are no longer needed. New installation architecture makes it simple and easy to install the product. The single install avoids correct version confusion. Simplified licensing Simplified licensing with two application licenses and three user licenses. Provides a greater ability to control and track licenses. Improved data integrity and performance increases Resolved tagging and bulk tagging issues. Automatic registration of databases A Registration Directory that allows for automatic migration and registration of databases. Administrators can also click on a database on the server to automatically register the database with the server. Additional drag and drop functionality Users can simply drag and drop files onto DAT, edoc, and databases. Users can use drag and drop to move tags from one folder to another in the Tags pane. Administrators can drag and drop databases to databases, creating automatic concatenation sets.

19 Installation Guide Installing Chapter 4

20 20 Installing Preliminary Planning About the discovery process Discovery has been around for a long time. In the past, it involved primarily paper documents that had to be searched through manually for privileged information or evidence. Today, discovery largely involves electronically stored information (ESI), which is simply data that exists in electronic format, stored in computers primarily as documents and . The question of how to search and review ESI for evidence comes down to two options: print it out and review it manually (slow and tedious) or put it into a database and review it on a computer (fast and effective). That s where comes in it s a database designed specifically for reviewing documents electronically, a process made faster and easier by its robust search and review features. Electronic discovery (e-discovery) starts with data being identified and collected. When all known discoverable data is collected, it needs to be processed by a tool such as LAW PreDiscovery, which puts all the data into a format that can be loaded into a Concordance Desktop database. In this step, documents get scanned, electronic files get converted and/or extracted, and the process of data filtering is completed (which can reduce thousands of documents down to a few hundred). A data administrator can then load all this processed electronic data into, where it gets reviewed and analyzed and, finally, produced for opposing counsel and/or the defense team.

21 Installing 21 Discoverable data Discoverable data is data that has been identified, preserved, and collected for a case that becomes (after many hours of review and analysis) the facts and issues that you either have to turn over to opposing counsel or use as evidence to defend your client. There are four types of discoverable data that works with: Paper documents Electronic documents Transcripts and depositions Electronic documents loads most electronic documents with ease, whether converted to tagged image file format (TIFF) or in their native form (created by popular software programs such as Microsoft Word, Adobe Acrobat, etc.). Documents loaded into Concordance Desktop in their native form are converted to PDF during import and can be viewed in. All electronic documents contain metadata, captured by the native application. However, additional meta data can still be added manually, if necessary in. You gain the following benefits when using the viewer functionality in : Consistent and reliable mark-up features for document review (redaction, highlights, etc.) Type comments/notes onto documents without defacing the original Fast loading of document images View any document or image, regardless of whether or not you have the native application makes it easy to import Microsoft Outlook and Microsoft Outlook Express messages (those with a.pst,.msg or.eml file extension). Other types of , such as those from Lotus Notes, must be converted before being loaded into, using a product such as LAW PreDiscovery (or using a vendor). Transcripts and Depositions If a transcript or deposition is in electronic form, and is formatted correctly, it can be loaded quickly and easily into, where you can review, tag, and add notes. Paper documents Even in this electronic age, people still use paper to write notes, capture diagrams, and so on. Additionally, letters, spreadsheets, reports and other documents created with computer programs are often printed out and the original electronic document lost or destroyed. In order for paper documents to be usable in, they must be scanned, to capture both text and an image (picture) of the document, and coded, to capture additional information such as author, document type, date created, and so on. This can be done using

22 22 a scanning and optical character recognition (OCR) tool such as LAW PreDiscovery. Scanning Paper is typically scanned into tagged image file format (.tif). For each TIFF, you ll have a corresponding file in the database, with matching serial numbers. A TIFF can be a single page or multiple pages, just as a single document can be one or several pages in length. So, not only are you able to view the document as a TIFF in, you ll be able to read the text of the document as well. Coding / Metadata Electronic documents contain additional information about them, referred to as metadata, which is data that is captured automatically by the software program, such as date created, author, and so on. This data is highly searchable and of great value to you during document review. However, because paper documents are scanned and lack this automatic coding, they must be coded manually (although there are now software tools, such as ALCoder, that can help speed up this process). Preparing for Preliminary planning for implementing any software application is important for achieving the best setup results, the first time. We recommend that you take some time to review this section to plan how your organization will be using so your administrative tasks are minimized for initial setup and your long-term maintenance of the application is streamlined into routine updates and adjustments, rather than reworking any database design and system security later. Discovery document conversion If you are unfamiliar with the e-discovery process, we recommend that you take some time to research this growing and rapidly changing industry and learn how it impacts your system network and strategy by understanding how critical it is that data load files are handled carefully during the import process. Because you are dealing with confidential materials, file corruption of your database records is a sensitive matter and legal implications regarding spoliation are strict and can carry hefty fines. Once data is altered, your ability to attain another copy of case records in some instances is minimal especially if it s opposing counsel s case records and can affect the lawsuit for the organizations involved. For more information about the e-discovery process, see About the discovery process. Hardware, software and system requirements Concordance s requirements for hardware, software and system are minimal and setup is flexible. The primary focus in ensuring that runs properly for you and your organization is processing Speed. It is important to understand that Concordance Desktop processing speed = memory (RAM). Please review the current system requirements for setup and suggested processor and RAM.

23 Installing 23 Keep informed of release updates and how they impact your system by checking our Technical Support web site at concordance, which is accessible from the Workspace tab in. For more information about system requirements, see Installation Recommendations. Licensing requirements Concordance s licensing requirements are minimal and licensing is very flexible to allow an easy fit for your firm's needs. The most important thing to remember about licensing is that you need at least one Server license and one Administration license if you have installed on a server or workstation computer; and one Mobile license if you have installed on a computer that you do not connect to a network, or on which you want will be performing all review work (creation and maintenance of databases, and all reviewer work) one a single computer that you do not intend to share with other users. Please review the current licensing options found under About Licensing and Product Activation. Database design Engineered for capacity and speed, provides stability with its enormous database capacity and robust user management features. Designed with a flatfile architecture and a proprietary back-end, can distribute and store data and process over local-area networks. With Concordance s separate load and index processes, you can import a variety of load files and their native file attachments, accessing them both in browse view or in the viewer (which displays a PDF copy of the native document). Proper review of your organization s records for a given case helps determine how you build and design your database structure. has some requirements for importing certain types of records, especially s and transcripts. Additionally, reviewing your case load files provides you with a high level road map for how you want to move forward in planning your database design. Database design considerations are based on: Possible database size breaking record groupings into Database 1, Database 2, Database 3 Document Type , native files, and transcripts Confidential/Privileged Status Content Predetermined Subject Groupings Rolling Production Environments adding content to primary databases by creating secondary databases and concatenating them Other For more information about databases and importing files, see About databases and About importing files.

24 24 Database access restrictions Database access restrictions are predominantly affected by the size of your organization and the user roles that constitute your review team. If your organization is large and has several geographical locations, database access restrictions for multiple ongoing cases is going to take time and forethought in planning. If you belong to a small organization, your database access restrictions may be minimal for internal staff because users are more likely to perform many roles using software. Please consider implementing database access restrictions in your organization to ensure that records are preserved in accordance with e-discovery regulations and database documents are secured from inadvertent alteration or deletion by applying recommended user permissions for field and menu items. For more information about database access restrictions and other settings, see About user management and About view preferences. Implementation checklist We understand that each organization has its own organization guidelines and processes for supporting their review teams during case review. We also understand that transferring to and implementing new technology may affect current procedures and that you may need to adapt new ones given the demands of a rapidly changing e-discovery industry. Please reference the Preliminary Planning Checklist to guide you in preparation for implementing and maintaining at your workplace. Preliminary Planning Checklist: Checklist: Preliminary Planning E-Discovery, Collection, and Processing Do you have an understanding of e-discovery rules and how they affect your specific case and the review process? Do you have a collection and processing plan in place while also following forensic guidelines, as required? Do you have vendor relationships set in place for various stages of your case? Do you have a quality control plan in place? Do you know what types of files you are receiving and whether they are recognized by? Database Design Do you know what your case dataset looks like? What is the size of your case, including the # of pages/documents and GB to be processed?

25 Installing 25 Checklist: Preliminary Planning Will this case require a review of documents appearing in near original format? Do you understand what the case review workflow will be? What kinds of fields are needed for tracking administration and reviewer metrics? What kinds of tags are needed for supporting administration maintenance? What fields are needed for coding additional metadata? Where will annotations be tracked by reviewers: If it s a field, what fields need preparation for annotations? Do you have field and tag naming conventions set in place? Do you have a list of categories for preparing your database tag structure? Have you consulted key players involved with review and administration regarding database design? Have you prepared a directory location with subdirectory folders in a structure that prepares you for optimal organization of the various files for the case? Did you create extra miscellaneous fields in your database? System Requirements Have you reviewed the system requirements? Have you given full network rights to all users in the directory where each case resides? Did you adjust the indexing and dictionary cache settings for each workstation? Do you have remote staff that will be using offline remotely and need a mobile license installed? User Management Did you plan user restriction settings for all users accessing this case? Did you apply user restrictions via User Management to each Concordance Desktop database individually? Did you store the user management settings (export them) to a safe location and share it with at least one other supervisor or administrator?

26 26 Checklist: Preliminary Planning Maintenance How will subsequent loads of data be handled? Will they be uploaded to the main database or will you use concatenation to join multiple databases? Do you have indexing/reindexing schedules planned based on the workflow and timeline of the review? Is there a back-up schedule in place? Do you have a quality control checklist for major administration tasks like importing, exporting, and global edits? Do you have a disaster recovery plan in place? Production Do you have a production plan in place for delivering files to opposing counsel? Do you know what types of reports will be generated or requested by the review team and how to print them? Roles and Responsibilities Does your review team understand the database design and know how they will specifically use for review? Does your review team understand timelines and processes required for administrating and maintaining? Are roles and responsibilities clearly defined among administrators, litigation support staff, paralegals, and attorneys? Are there policies in place for who can and cannot create/modify databases and other sensitive tasks? Ongoing maintenance As an administrator you are busy managing multiple cases and the various software programs and databases in various network locations. We recommend you to take some additional time to plan a maintenance schedule for depending on the complexity of product licensing versions and how database structure is designed and geographically dispersed. Typical database m anagem ent for includes: Directory and sub-directory folder design to store multiple databases for multiple case reviews within your organization

27 Installing 27 Back-up schedules for each case/multiple databases/concatenated databases Full index updates on databases performed during off hours (weekends or holidays) or offline if multiple databases can be updated while staff continues work in other databases Reindex updates when records are added or modified Subsequent data and image loads Deleting and packing databases and dictionary files after data entry/editing and indexing De-duplication Replicating and synchronizing databases Modifying or adding database fields, which then requires a full index Tracking metrics Running productions Related Topics About backing up databases About archiving databases About managing databases Installation Recommendations Hardware, Software, and System Recommendations The software application requires minimal hardware, software, and system specifications, and provides setup flexibility. The primary focus of our recommendations is to ensure that runs properly for you and your organization. The key factor for accomplishing this is to remember that memory (RAM) on your network servers and individual computers (i.e., workstations in a network environment) determines your processing speed. Please review the current installation recommendations, and most importantly the processor and RAM recommendations. Review each section in advance before making expensive hardware and network decisions that may not be in line with LexisNexis recommendations. You can remain informed of release updates and how they impact your system, by checking our Technical Support web site at lexisnexis.com/concordance, accessible from the Workspace tab in. Cache settings for installations The cache requirements for are minimal, as all processing occurs on the server, unless you are using a mobile only installation. On mobile

28 28 only installations, all processing occurs on the one computer, as a mobile only installation consists of only one computer. In both instances (server and mobile), the processor and local memory (RAM) installed have the greatest impact on searching, sorting, and indexing speeds. For network users, your network, internet connection speeds, and hard disk space will have some impact on the speed as well. The cache indexing setting allows you to designate a specific amount of memory to be used for indexing and reindexing databases. We recommend increasing this setting during the installation of to greatly improve indexing speed. Note that the more memory the computer has, the more you can designate for database indexing cache (up to 2GB per indexing job). Increasing this setting will result in faster indexing and reindexing processes. You will want to adjust this cache indexing setting on all computers designated as servers. Recommendations for a network computer used as a Server The following recommendations apply to any network computer (server or workstation) on which you plan to create, maintain and store databases. Each of these computers will be referred to as a "Server". A "Server" license is required for a computer if you want to set it up as a Server, and that the license must be activated on that computer to enable Server functionality. Important Note: When setting up permissions on your network, please ensure that all users have full network access to each database directory for which they will need access. Server hardware recommendations The hardware recommendations for a Server on a network computer are: Dual 3GHz Xeon or Pentium HT (hyper-threaded) processors or higher 4 GB of RAM or higher 40 GB of disk space or higher Server software and system recommendations The software and system recommendations for a Server on a network computer are: Microsoft Windows 7 (64 Bit)/ Microsoft Windows 10 (64 Bit)/Microsoft Windows Server 2008 R2/Windows Server 2012/Windows Server 2012 R2/Windows Server 2016 Microsoft Outlook 98 or higher (32 bit) High-speed Internet connection The.NET Framework 3.5 AND 4.0 or higher (3.5 must be installed and enabled, in addition to 4.0 or higher) Two open ports for inbound/outbound traffic

29 Installing 29 Two open ports in the firewall are needed for inbound and outbound traffic. By default, reviewers use Port 443 because it s generally already open on most firewalls and is typically used for SSL packets, so beware of packet monitoring protocols. The Administration Console uses Port by default for administrators, because it s typically not used by other services. Before installing on a Windows Server 2008 R2, 2012, 2012 R2 64-bit machine or Windows Server2016 make sure that the server is up-to-date with the current Microsoft patches, and that the Microsoft.NET Frameworks 3.5 and 4.0 are installed. The 3.5.NET Framework must be installed in addition to 4.0.NET Framework, as the 4.0.NET Framework does not include the updates that were included in the 3.5.NET Framework release. If the server is running on a machine that is using IPV6, you need to disable IPV6 and use IPV4 instead. When IPV6 is used, users are unable to connect to the CND server. Note that by default, Windows 10 (and later) and Windows Server 2012 (and later) automatically enable IPV6. For more information regarding the disabling of IPV6, please see article support.microsoft.com/en-us/kb/ article on the Microsoft web site. The server functionality in does not require a Web server (such as Microsoft Internet Information Server (IIS) or Apache ). Calculating user capacity The user capacity of a Server on a network computer is metered by the hardware. Based on the number of users that need to be supported, you can add multiple CPUs to have the proper user capacity available. For example, a Hyper Threaded (HT) CPU supports 50 users. Database location considerations There are a few things to consider when determining the location of the Concordance Desktop database files. database location considerations: When users access a database located on a network server, the bandwidth on the LAN, Internet connection and the server speed are all determining factors in the responsiveness of opening and working with that database in. For greatest performance and system reliability, databases must be stored local to the server. Performance may be affected by indexing, overloading of available Internet or LAN bandwidth, or in situations where databases are not stored local to the server. The software requires a minimum of 500 MB of available hard disk space for installation of software, generated logs and temporary files, plus additional space for databases. Indexing, reindexing, and packing may require extra disk space and memory (RAM).

30 30 If performance is an issue, add processors, bandwidth, and memory as needed. Additional recommendations, along with information for larger firms, can be found in the Additional Recommendations topic. Concordance server setup offers administrative flexibility when installing the database and imagebase files. You have the option to place each on different servers and/or computers across your network. A typical serv er installation includes: The application installed on the server, or whatever computer is being used as a server. The application installed on each user's computer (usually referred to as workstations or workstation computers). Activation of a Server license on the server, or whatever computer is being used as a server. Full permission on the server to the database directories that will require user access. Storage of the database files and images local to the server. Assigned user licenses (Full Reviewer and/or Only) in the Server Administration Console for users. User configuration settings Network user configuration information is stored in two places. Specific user preferences, such as highlighting color and the default search operator, are saved in the server s system registry. For information on the registry key locations, see Registry key locations. Specific database settings are stored in the database.ini file. Shared table layouts are stored in the database s home directory. Network printing is handled by Microsoft Windows. will print to any printer you have defined through Windows. has menu-option and field level user management. For additional information, see About user management and About indexing databases. In order to perform most of the database tasks, such as indexing, creating tags and notes, importing data, modifying the database, and creating new databases, the user must have Modify folder permissions to the folder where the database's.ini file is located. For more information, please contact your Network Administrator or the Windows Help and Support Center. Recommendations for installation on workstation computers

31 Installing 31 Hardware recommendations for installing on a 32-bit workstation 1 gigahertz (GHz) or faster 32-bit (x86) processor 2 gigabyte (GB) of RAM 16 GB of available hard disk space Hardware recommendations for installing on a 64-bit workstation 1 gigahertz (GHz) or 64-bit (X64) faster processor 4 gigabytes (GB) of RAM 20 GB of available hard disk space Software and system recommendations for workstations The software and system recommendations for a workstation that needs to access server based databases are: Microsoft Windows 7 (32 or 64-bit), or Windows 10 (32 or 64-bit) Microsoft Outlook 98 or higher (32 bit) The.NET Framework 3.5 and 4.0 or higher (3.5 must be installed, in addition to 4.0 or higher) Appropriate language packs installed installation Internet access for remote connection, and to download the install if needed Ability to connect internally to the server Before installing on a workstation machine, make sure that the machine is up-to-date with the current Microsoft patches, and that the Microsoft.NET Framework 3.5 and 4.0 is installed. The 3.5.NET Framework must be installed in addition to 4.0.NET Framework, as the 4.0.NET Framework does not include the updates that were included in the 3.5.NET Framework release. The server does not support connections using IPV6. If your users need to connect to the server to review and work with databases, please ensure that IPV4 is enabled on their workstations, as opposed to IPV6. Note that by default, Windows 10 (and later) automatically enables IPV6. For more information regarding the disabling of IPV6, please see article support.microsoft.com/en-us/kb/ article on the Microsoft web site. Recommendations for Mobile installations on stand-alone computers The following recommendations apply to a stand-alone computer (i.e., one that does not

32 32 connect to a network) on which you plan to create, maintain, store, and work with Concordance Desktop databases all on a single computer. In, this is referred to as a "Mobile" installation. Usually these types of setups are used by small firms having only a few or less users who handle every aspect of the review process themselves on their own computer, or in firms where there is no network environment set up. A "Mobile" license is required for a Mobile installation of, and that license must be activated on the computer to enable full functionality. Software and system recommendations for Mobile license users The system recommendations for a mobile license user are: Microsoft Windows 7 ( 32 or 64-bit), or Windows 10 (32 or 64-bit) Appropriate language packs installed installation The.NET Framework 3.5 and 4.0 or higher (3.5 must be installed, in addition to 4.0 or higher) Internet access for remote connection, and to download the install if needed Users must have full permissions on their mobile computer to write to database directory folders/files Before installing on a workstation machine, make sure that the machine is up-to-date with the current Microsoft patches, and that the Microsoft.NET Framework 3.5 and 4.0 is installed. The 3.5.NET Framework must be installed in addition to 4.0.NET Framework, as the 4.0.NET Framework does not include the updates that were included in the 3.5.NET Framework release. You cannot access databases on a machine that has IPV6 enabled. If you plan to run mobile, you need to ensure that your machine does not have IPV6 enabled. If it does, you need to disable IPV6 and use IPV4. Note that by default, Windows 10 (and later) automatically enables IPV6. For more information regarding the disabling of IPV6, please see the support.microsoft.com/en-us/kb/ article on the Microsoft web site. Hardware recommendations for Mobile license users The system recommendations for a mobile license user on a 32-bit or 64-bit computer are: 1 gigahertz (GHz) 32-bit (x86) or 64-bit (X64) (or faster) processor 4 gigabytes (GB) of RAM A minimum of 20 GB available hard disk space

33 Installing 33 Additional Recommendations Using the server functionality on a network server, requires proficiency with Internet addressing, ports, firewalls, and potentially with local area network (LAN) topologies and security settings. These issues can be complex even for experts. Your IT staff or Internet service providers are best suited to assist you with the security and network settings specific to your company. is optimized to perform at the highest levels; however, it cannot overcome slow Internet connections, slow file servers, or simple overloading. The Concordance Desktop Administration Console can monitor server performance to help identify bottlenecks and server saturation. Interpreting the information and correcting certain issues may require the assistance of an IT professional. Network connection speed, network traffic, database and imagebase size, and other items may be a factor when evaluating performance. Please review the following recommendations for enhancing performance. Indexing speed recommendations We recommend giving as much memory as possible. Concordance Desktop allocates memory to internal disk buffering during indexing. Any program that decreases the amount of available memory, or performs background processing, could severely impact indexing performance. The larger the database: the greater the impact. You can control the amount of cache, but be careful when allocating memory to the cache. Windows has virtual memory that is stored on the hard drive when it is not being used. If allocates a cache that forces too much swapping to disk, indexing will actually run slower. Indexing speed can be greatly im prov ed by the following: Using a disk-caching hard disk controller Adding a faster hard disk Using a faster computer Indexing on a Windows NTFS formatted hard drive Indexing individual databases on separate computers The highest performance is obtained by combining some or all of these options. There are many recommendations on this subject. All but one has the effect of lowering the workstation s disk activity. We also recommend indexing individual databases on separate computers. Lower workstation disk activ ity by: Adding more cache RAM to your workstation and allocating this RAM to the Indexing cache (up to 2GB maximum per ). You should leave 128MB unallocated and available for the Microsoft Windows operating system. Get a faster processor for the workstation Get a caching disk controller on the workstation Use a level 1+0 RAID array with your disk caching controller

34 34 Implementing these suggestions will result in a significant boost in indexing performance. Index cache and processor speed have the greatest impact. Recommendations for larger firms with networks For best performance across larger firms with network environments, we recommend: At least a 3GHz computer with Hyper Threaded (HT) processors and a minimum of 4GB memory (RAM) or A disk caching, fault tolerant RAID 1+0 array controller for ultimate speed and data integrity, if you need to plan for multiple, or very large databases Microsoft Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2 or Windows Server 2016 Network connection speed, network traffic, database and imagebase size, and other items may be a factor when evaluating performance. To maximize performance, the user capacity of the Server is metered by the hardware. A Pentium CPU will support 25 users. A Xeon or Pentium Hyper Threaded (HT) CPU will support 50 users. Multiply CPU capacity for dual and quad CPU servers. Server capacity is also limited by bandwidth on your LAN and your Internet connection, and by file server speed. requires a minimum of 500 MB of available hard disk space for installation of software, generated logs and temporary files, plus additional space for databases as required. We recommend storing databases directly on the Server for highest performance and system reliability. Indexing, reindexing, and packing may require extra disk space. Performance may be affected by indexing, overloading of available Internet or LAN bandwidth, or in situations where databases are not stored directly on the Concordance Desktop Server. Add processors or bandwidth as necessary, if performance is an issue. Web Servers The server does not require a Web server, such as Microsoft Internet Information Server (IIS) or Apache. is a native software application which runs directly on your server. It is optimized specifically for serving Concordance Desktop and viewer data. It does not serve any other kind of data. Remote users connect directly to the server from a installation. The server is compatible with Web servers for data hosting, and will run on a computer that is also running Web, FTP, mail, and other Internet servers. However, we strongly recommend, for highest performance, that the server/computer that you plan to register as a server be installed by itself on a dedicated server/ computer.

35 Installing 35 Memory and RAM All processing for shortcut (.fyi) files occurs on the Concordance Desktop server. allows you to allocate a specific amount of RAM for indexing databases. allows you to allocate a specific amount of memory for the purpose of indexing databases. You can allocate up to 2GB per process in the Indexing cache field on the Indexing tab in the Preferences (Tools > Preferences) dialog box in Concordance Desktop. To determine the minimum amount of RAM you can allocate for indexing take (Total RAM) (O/S RAM). For more information about calculating the indexing and dictionary cache, see Adjusting indexing settings and Adjusting dictionary cache settings. Latency and Bandwidth As administrators, how you monitor and manage SSL packets and set up your firewalls affects reviewer bandwidth for sending and receiving information from your in-house network to remote users. If users are experiencing latency issues, you will need to run a trace route for any dropped packets and check your firewalls to see if there s any delay in sending and receiving information, and then fix any issues within your network. The FYI.db File All information from the Admin Console is stored in the FYI.db file, which can be found in the same directory as the Program Data folder (ProgramData\LexisNexis\). This file includes information that is tracked for registered databases, users, licenses, settings, etc. The backup of this file is critically important to ensure the security of the information that is being stored. Preparing for Preparing for on a Server Preliminary planning for implementing any software application is important to achieve the best set-up results, the first time. We recommend that you take some time to review this section and plan how your organization will be using on a network server. Planning ahead helps ensure that administrative tasks are minimized for initial setup and your long-term maintenance of the application. When implemented properly, your administrative tasks should then be streamlined into routine updates and adjustments, rather than reworking any database design, server setup, and system security later. Best practices for planning Data hosting Network directory setup

36 36 Working with System requirements Server setup and user management Best practices for server setup Server security Ongoing maintenance Scheduling administrative tasks Backups and data recovery Updating considerations Best practices for planning Before installing on a network server, please review the best practices below, to ensure your organization has reviewed all planning phases. Best practices for planning: Server Data Hosting server ASPs hosting client data should take advantage of Microsoft Active Directory to first set up users and then add those users to. Active Directory includes password policies and organizational features for managing users. *Must set the Active Directory password to never expire Large firms and organizations should also take advantage of Active Directory and set up User Management *If using existing Active Directory, in, clear the 'Logon required' check box on the Field rights tab in the Security dialog box for each database Smaller firms and organizations can use the Concordance Desktop Admin Console to set up users and apply settings Network Directory Setup Ensure Server users have full network access to the database directory Have preset folder templates for each client and matter Have a clear separation between billable and non-billable data Receiving Data and Images

37 Installing 37 Best practices for planning: Server Verify that file formats are recognized by Export databases to new databases to update and verify existing structures to comply with your internal guidelines Database Design Create default database structure templates for different types of discovery Implement field name conventions for consistency Create an Admin tag folder Verify that you used UNC paths in the Data Entry Attributes dialog box (Edit > Validation) Use UNC path with your hyperlinks Create smaller databases and use concatenation Use document-level text files Add administration fields Add EDITTRAIL and CREATEDATE fields Server Setup and User Management General Implement server and database firewalls when possible Users Use the Admin Console, User Management, and Microsoft Active Directory Ensure Active Directory and user names match, and do not include any special characters such as %, &, #, etc. Implement your network password policies, and set Active Directory passwords to never expire Admin Console Setup user accounts Set up administration user accounts Set up administration users alerts for s. Alerts will be sent to every administrator who has an address entered in their user account. Note that to send out notifications from the server, an client

38 38 Best practices for planning: Server (such as Microsoft Outlook) must be installed and setup on the server. Managing Clients and Users Inform users of training options, immediately Create templates for users that include their logon information and pertinent project or software instructions to get them started Always communicate turn-around times, as they change Remember to educate, rather than dictate Ongoing Maintenance Schedule maintenance windows to ensure that all users are out of the database and the database is taken offline Always take databases offline when loading any data or while performing administrative work Backups and Data Recovery Always back up your FYI.db file Ensure your internal guidelines are in place for back up and data retrieval Implement archiving and data destruction policies Updating Considerations Best Practice is to always be on the most recent version of Ensure your internal guidelines are in place for back up and data retrieval Quality Control Have well-defined checklists and procedures in a centrally available location Ensure that hand-off processes are well-defined

39 Installing 39 Data hosting There are two main scenarios that involve data hosting: Concordance Server ASPs Server ASPs provide setup, security, and maintenance services. However, when speaking with Server ASPs, it is best practice to confirm that they have certified and Server members on staff to ensure your matter is setup properly and as soon as you need. In-House Concordance Server Installations For firms and organizations with the necessary technology infrastructure, data hosting inhouse allows for direct control of data and productions. Data hosting, requires a mature organization with an experienced technical team that can overcome the liability risks involved and can meet the financial investment required to ensure exceptional hardware purchases and setup, dependable power to support services, and tight physical security to protect data. Network directory setup Most organizations have network directory design guidelines already in place to store information in a consistent and logical manner. We have some recommendations for you to consider while you review your own or to consider implementing for new cases: Folder Hierarchy and Naming Conventions The following is an example of folder naming conventions and directory hierarchy for storing documents, backup files, productions, etc. This is especially useful for Hosting as it separates billable data from non-billable data. The Uploads folder gives a staging area for quality control of data received from clients. From the Uploads folder, data can then be moved to its appropriate final resting place. Moving is helpful for billing, troubleshooting such as repairing Native File links if they are disrupted. Retaining a folder template is useful when new data arrives or when moving a database to a new directory location as this will help to keep organization consistent.

40 40 Databases for Billable versus Non-billable Tasks Server ASPs hosting data for clients will have additional database design needs to construct databases to manage billable versus non-billable tasks. Uploads for billable tasks: Images Native files Databases Productions Authority lists Backups

41 Installing 41 Query files Security Uploads for non- billable tasks: Staging Load files OCR files Database administration documents Working with When working with a database server, you want to ensure that you have a strong understanding of and its viewer. There are various aspects that must be taken into consideration during the preplanning phase. Receiving Data When you receive data from a client, data processing vendor, or third party, you should always review all files and databases to ensure they have the proper formats for. We recommend having your OCR separated into individual document-level text files. When importing these text files automatically overflows any text that exceeds the 12 million character capacity of a paragraph field into the next available field. System requirements Please review the current system requirements for setup considerations and suggestions for your processor and RAM. Review each section in advance before making expensive hardware and network decisions that may not be in line with LexisNexis recommendations. When setting up permissions, make sure all users have full network access to each database directory they need to work with. Please keep informed of release updates and how they impact your system, by checking our Technical Support Web site at products/ediscovery/concordance-desktop. This link is also available from the Concordance Desktop Workspace tab. System Requirements: Server The minimum system requirements for Server are: Hardware and Software Minimum Recommended

42 42 Processor (CPU) 3GHz processors or higher Dual 3GHz processors or higher Memory (RAM) 4GB 8-16GB Hard Drive (Installation) 1GB of disk space or higher 3GB of disk space or higher Supported Operating Systems Microsoft Windows 7 (32 or Microsoft Windows Server 64-bit), Microsoft Windows 2008 R2, 2012, or 2012 R2 or 10 (32 or 64-bit), Server R2, 2012, 2012 R2 or 2016 (both 32- & 64-bit, all service packs) *Windows 8 is not supported Software Required for Proper Operation Microsoft Outlook 2010 or higher (32 bit) *64 bit is not supported.net Framework 3.5 AND 4.0 or higher Internet Protocol v4 (IPv4) Microsoft Outlook 2013 or higher (32 bit).net Framework 3.5 AND 4.0 or higher Internet Protocol v4 (IPv4) *IPv6 is not supported. *Installer updates as needed on Microsoft Windows 7 and 10 In addition to the above, the server also requires two open ports in the firewall for inbound and outbound traffic. By default, reviewers use Port 443 because it s generally already open on most firewalls and is typically used for SSL packets, so beware of packet monitoring protocols. The default Admin Console Port is for administrators, since it s typically not used by other services. Standard editions of Microsoft Windows Server support a maximum of 4GB RAM. To add more RAM, you must use an Enterprise edition of Microsoft Windows Server. System Requirements: Workstation Hardware and Software Processor (CPU) Minimum 3GHz processors or higher Recommended Dual 3GHz processors or higher Memory (RAM) 4GB 8-16GB Hard Drive (Installation) 1GB of available disk space 3GB of disk space or higher Supported Operating Systems Microsoft (both 32- & 64-bit, all service packs) Software Required for Proper Operation Windows 7 (32 or Microsoft Windows 7 (32 or 64-bit) or Microsoft Windows 64-bit) or Windows 10 (32 or 10 (32 or 64-bit) 64-bit) *Windows 8 is not supported Microsoft Outlook 2010 or higher (32 bit). *64 bit is not supported.net Framework 3.5 AND Microsoft Outlook 2013 or higher (32 bit).net Framework 3.5 AND 4.0 or higher

43 Installing 4.0 or higher Internet Protocol v4 (IPv4) 43 Internet Protocol v4 (IPv4) *IPv6 is not supported. *Installer updates as needed on Microsoft Windows 7 and 10 Calculating User Capacity User capacity of the Server is metered by the hardware. Based on the number of users that need to be supported, you can combine multiple CPU servers to have the proper user capacity available. A Pentium CPU supports 25 users. A Xeon or Pentium Hyper Threaded (HT) CPU supports 50 users. Multiply CPU capacity for dual and quad CPU servers. Additional Serv er considerations: Server capacity is also limited by bandwidth on your LAN and Internet connections and by file server speed. The Server requires a minimum of 100 MB of available hard disk space for installation of software, generated logs and temporary files, plus additional space for databases. We recommend storing databases directly on the Server for highest performance and system reliability. Indexing, reindexing, and packing may require extra disk space. Performance may be affected by indexing, overloading of available Internet or LAN bandwidth, or in situations where databases are not stored directly on the Concordance Desktop Server. If performance is an issue, add processors or bandwidth. For additional information about system recommendations and software compatibility, see System recommendations. Server setup and user management Your server infrastructure and set-up design are critical to ensuring that works in a seamless fashion, and that data processing is running at optimal levels. Planning your strategy in advance saves you frustration, time, and possibly even money in the future. The steps you take now in carefully implementing the product, server database locations, and network directories help ensure your success in using it. You need to pre- plan: Port access and service protocols Server placement

44 44 Server firewalls and monitoring services User management Plan your integration of server to ensure it coincides with your organization s network policies and procedures and re-examine them for how they impact server requirements. If user restrictions are necessary at the database level to prevent some users from seeing a database to select it, or to limit their field rights and menu access in specific databases, you may want to plan for using the User Management feature to setup those restrictions on a database by database basis. For information about setting up you users, see About setting up and managing users. For information about setting up database restrictions, see Restricting user rights to a database. For information about user groups, see About clients, matters and user groups. For information about clients and matters, see About clients, matters and user groups. Identifying administrative tasks Identifying which administrators need access to the Admin Console is key to ensuring that ongoing maintenance gets performed. Checklist: Identifying Administrative Tasks Did you set up an administrator user ID and password in Microsoft Windows Services for to access servers where data resides? Do you know which administrators on your team need access to the Concordance Desktop Admin Console? *Each user should have an individual user name and password. Additionally, have you identified which administrators on your team need access to administrative menu items? Have you determined if there are varying levels of rights being granted to administrators? Do you know which administrators will be in charge of database processing (Zap, Pack, Index, Reindex), and for what clients, matters, and databases in the Admin Console? Have you decided which administrators should receive alerts when a process fails to run, etc.? Have you determined which administrators are responsible for ensuring that packets are not dropped? Did you decide which administrators are responsible for resolving severe errors?

45 Installing 45 External authentication or user management One of the primary distinctions to make in advance is whether you are using external authentication to manage your users or are simply using user management. The server can authenticate users using Microsoft Active Directory while also allowing you to setup field and menu restrictions for each database with Concordance Desktop user management. If you are installing the server on the DMZ (demilitarized zone), you should use the external authentication to set up users, in addition to setting user management in each database. If you are installing the server on a LAN (local area network), you can simply use Admin Console to setup users and then use the User Management feature to set field and menu restrictions on a database by database basis. In, all users are assigned access to all databases and have full rights to fields and menus. For more information about authentication, see About setting up user authentication. Adding users and providing access Most Server ASPs and organizations are managing hundreds of users simultaneously and they all need access to multiple matters and databases in remote locations. Designing a user matrix that identifies each user s database access needs may be helpful to reference when setting up and managing users. provides two options for setting user access to databases; you can use the User Management feature to grant users different read/write access to fields and menus within a database, or use the Admin Console (under the Management tab) to grant read/write access to fields and menus across all databases. User management settings, user roles or groups, and user role templates can be modified based on individual needs, and affect what a user can access in. You can also control which databases and matters are viewable and accessible to each user based on client and matter organization within the Admin Console (under the Management tab). Understanding what key settings need to be retained in order for users to access the server and underlying databases helps you minimize problem solving later. If your organization uses to add users, be sure to only use single-byte characters when creating user names and passwords to be used in. For more information about user management, see About setting up user management. For more information about clients, matters and user groups, see About clients, matters and user groups. Synchronizing databases Synchronizing updates the user lists - adding new users and removing deleted users. Databases can be synchronized automatically in the Admin Console by clicking the

46 46 Synchronize now button on the Management tab in the Admin Console. Jobs can also be scheduled to synchronize databases. A database administrator needs to be specified before a database can be automatically synchronized. Passwords uses the authentication logon name to determine a user's database rights, field rights, and menu settings. Check the database in the Admin Console and add user names and rights as needed. Best Practices for new databases If you need to restrict access on a database by database basis, first add the users in the Admin Console and then restrict field-specific rights and limit their menu access from the User Management screen. For more information about adding users to a database, see Setting up users. Be sure to only use single-byte characters when creating user names, passwords, and database names in. The server does not support user, user group, database, matter, and client names, or passwords that contain Unicode characters, such as Chinese or Japanese characters. Currently, only single-byte characters, such as English characters, are supported. Be sure not to use special characters when creating does not support the use of special characters, such as %, &, #, etc. in user IDs, user groups, database names, matter names, and client names. When adding dom ain users to, it is im portant to follow these steps: 1. Add all of the domain user names to the database and assign database rights and access. For more information about adding users to a database, see Setting up and managing users. 2. Add the users to the domain server. 3. Insert the domain users under the Users folder on the Management tab in the Admin Console. For more information about inserting domain users, see Updating the Users list.

47 Installing 47 If both the LDAP and Auxiliary server options are set, both server names are displayed when using the Insert Domain Users option. Best practices for server setup Server is server class software and requires a powerful, designated server to ensure that performance is optimal. Some IT departments may try to host Server on a virtual machine as opposed to a designated server in an effort to save money without allocating enough system resources. Unlike (where processing is performed on individual workstations), all processing for.fyi users is done on the Server. When implementing Server, we recommend that you invest in the best server your organization can afford, that meets or exceeds what is stated in the system requirements. Server is not a web server and cannot work through a proxy server. Server must have an open connection through a named port. When planning your server setup, there are a few things to consider beforehand. We recommend that you reference the Best Practices for Server Setup when planning your server configuration. Best Practices for Server Setup: Server Server Minimum Windows Server 2008 SP2/Windows Server 2008 R2 or Windows Server 2012/Windows Server 2012 R2/Windows Server 2016 Dual Xeon (HT) (hyper-threaded) processors User capacity is metered by the hardware Each Pentium CPU supports 25 concurrent users Each Xeon or hyper-threaded CPU supports 50 concurrent users 4 GB RAM or higher 100 MB available hard disk space Disk caching, fault tolerant RAID 1+ 0 array controller High-speed Internet connection, 1.5mbps or faster Best Practice Ample CPU + RAM dependant on the number of users and how they use it

48 48 Best Practices for Server Setup: Server * Virtual machines are not recommended due to scalability limitations Failover Redundancy T3 or OC1 Internet Connections Server Security Standard Behind Firewall Secure Access Best Practice Hardware Firewall Network/Server Monitoring 24-hour Surveillance Fingerprint/Retina scan access Server Backups Standard Incremental secure backups Best Practice Data Mirroring/Clustering (SQL Server) Disaster Recovery Plan Offsite Data Recovery Server Support Required Staff CCSA CCFA Project Manager Network Administrator Technical Support Best Practice 24/7 Technical Support CCST Paralegals

49 Installing 49 Best Practices for Server Setup: Server Print Job Clerks Project Managers Law Firm Experience, Previous Vendor Experience, and EDD/ Processing Experience Database Administrators Active Directory Administrators Certified DBAs, Very Technically Savvy, Detail Oriented, and have Network Administration Experience Server Setup Standard Be sure to have the recommended minimum hardware resources Best Practice Create a separate Microsoft Windows account for Concordance Desktop Server that has network rights to run services Store active databases on the Server itself or on a SAN or NAS server box that is attached to the Server to eliminate as much network latency as possible. If you are using a SAN or NAS server box for databases, the server should be on the same LAN, in the same location as the Server, and connected to the Concordance Desktop Server with Gigabit-speed Ethernet switches and cables. Be sure your Server is not on a Web server. Store the TIFF image files associated with your databases on the Server or on a SAN or NAS server box that is attached to the Server to eliminate as much document and production latency as possible. If you are using a SAN or NAS server box for TIFF image files, the server should be on the same LAN, in the same location as the Server, and connected to the Concordance Desktop Server with Gigabit-speed Ethernet switches and cables. Shortcut (.fyi) File Setup Standard Provide the shortcut (.fyi) file to the client to allow them greater control over their data Best Practice Make sure that clients/users are using the latest version of. We recommend that you do NOT allow access to the following menu items:

50 50 Best Practices for Server Setup: Server File > Modify File > Reindex File > Index File > Administration File > Begin Program File > Edit Program Edit > Validation Edit > Delete and undelete server security The server uses a variety of security methods to ensure data integrity, security, and high performance. Please read this section carefully, prior to implementing security for the computer you will be using as your server. Concordance Server Connections An installation of connects to the computer, registered as the server, using an SSL encrypted connection. This connection is fully compatible with firewalls that monitor and verify SSL traffic. Unlike a standard Web server connection, the server connection is kept open for the entire session for both efficiency and functionality. The connection is kept open to send progress messages, to update interactive search results and progress meters, and to perform other operations that would not be possible with repeated and unnecessary connections and disconnections. Encryption Data passed between the server and clients is both compressed and SSL encrypted for high speed and security. uses both RSA public and private key encryption. All data is transmitted using RSA 128-bit encryption. The initial handshake conversation is encrypted using 1024 bits. This is the same SSL encryption used by web servers for tasks such as online banking. We recommend that you install the server on SSL Port 443, as it is fully SSL compliant. Ports Administrators can log on to the Admin Console using an administrator user name and password. Firewalls are not required, but can be used to maintain security

51 Installing 51 when exposing the server to public IP ranges. Using firewalls determines which IP ranges are allowed access to the server. Setting Port Addresses: End-user traffic for shortcut (.fyi) files via the server Default Port is 443 Administration traffic on the server via the Admin Console Default Port is We recommend that you periodically check your ports to ensure they are open to inbound/outbound traffic. For more information about modifying port addresses, see Adjusting port settings. DMZ or LAN? The server can reside on your LAN or in your DMZ as your data security policy dictates. If you are using external authentication, user log-ons and passwords in Concordance Desktop must be identical to the DMZ in order for reviewers to access databases on the computer registered as the server. If you are only applying user management, we recommend that you register the server license on a computer on your LAN because the DMZ generally requires opening a connection from the server to the LAN, which can create a security risk. We also recommend using NAT (Network Address Translation) to open an inbound port to the server, and setting the server to use SSL Port 443, as it is fully SSL compliant. Authentication Types Microsoft Windows NT, Microsoft Active Directory, and PDC secure login can be used by, making user administration easy and fully integrated with your existing network policies. will use NT, PDC, and Active Directory authentication, passing all login and passwords to your existing domain server for verification and enforcement of password policies including expiration, length, mix of alphanumerics, and all other policy restrictions used by your organization. with Active Directory, Windows NT, or PDC can be used to verify users credentials. Logins are checked with Windows Security Controller. Setting this up helps ensure conformation with password policies. Supported Authentication Types Internal Types Description Concordance Uses the.sec file to authenticate users. Highly recommend always

52 52 Supported Authentication Types Desktop implementing a user login and password to connect. External Types Description External by Domain Allows for authentication against an NT Domain Controller (without Active Directory). External by NT Server Allows for authentication against a stand-alone server (Member server). External by Active Directory LDAP Uses the Microsoft Windows Active Directory to authenticate users. Authentication by Lightweight Directory Access Protocol (Active Directory). For more information about external authentication and how it relates to users, see About setting up user authentication. Using Microsoft Active Directory If you are using external authentication, you will need to first set up users in Active Directory and then add the user's name in the Security Console of the database, before specifying.fyi users in the Admin Console. When using external authentication, it is important that user names match in the Active Directory and the database. We also recommend registering databases in the Admin Console as a means of adding users to the Server. User accounts are enabled in the Admin Console on the Management tab. For more information about setting up users in the Active Directory refer to Microsoft's web site and search on "active directory." File Storage Considerations File size and storage considerations are additional planning elements when setting up the Server. You need to ensure the following: The server hosting databases can access other servers easily That server can access files easily Databases and images are local to the server There are no latency issues arising from databases or image files that are too big You can choose to store databases and im ages in two ways: LAN For this setup, we recommend you store databases and images on the same server/computer that you have registered as the server, to reduce any latency issues in accessing files.

53 Installing 53 Network Accessible Storage You can choose to store databases on one network device and images on another, and have the server point to these locations to access them. Latency differentiations are minor if database size is kept smaller and all images are processed as single TIFs. For more information about database design, see Database Design in the Preparing for topic. Ongoing maintenance As an administrator you are busy managing multiple cases, various software programs and databases, and all in various network locations. We recommend that you take some additional time to plan a maintenance schedule based on the following tasks and processes, and any others that are distinct to your organization or client needs. Typical database m anagem ent for Serv er and com panion products include: Directory and sub-directory folder design to store multiple databases for multiple case reviews within your organization Backup schedules for each client and matter, and each database, including multiple database and/or concatenated databases Full index updates on databases performed during off hours (weekends or holidays) or offline if multiple databases can be updated while staff continues work in other databases Reindex updates when records are added or modified Loading data into databases offline Subsequent data and image loads Packing databases and dictionary files after removing records within the database. De-duplication Modifying or adding database fields, which then requires a full index Creating or removing users and adjusting security settings and permissions Tracking metrics Running productions Monitoring and extending user sessions Updating product versions in accordance with system requirements Archiving data according to your organization s internal guidelines or client s needs For more information about backups and data recovery, see About backups and data recovery. For more information about automating tasks in the Admin Console, see About scheduling jobs.

54 54 Scheduling administrative tasks Planning in advance what jobs need to be scheduled for ongoing maintenance helps you determine the schedules you need to manage these tasks for multiple databases and all your users and clients. By setting up a standard maintenance schedule, you can inform your users in advance to ensure that they set up their review times around these schedules. You want to make sure that all users are out of the database and the database is taken offline when performing administrative tasks. The Jobs tab in the Admin Console assists with management tasks, like reindexing and packing. All scheduled tasks on the Jobs tab are processed on the Concordance Desktop Server. You can find your database indexing time by reviewing the Log tab in the Concordance Desktop Admin Console. For more information about automating tasks in the Admin Console, see About scheduling jobs. Exclusive Administrative Tasks Some database management tasks require that all users are logged out of the database. The administrator is the only user allowed in the database when the following processes are occurring in : File > Modify File > Index File > Administration > Pack > Database File > Administration > Zap File > Administration > TRK Maintenance Tool The following database management tasks in do not require the database to be taken offline, but they should be taken offline to ensure validity of all data: File > Reindex File > Administration > Pack > Dictionary Documents > Import Documents > Export Creating productions (Tools > Production > Production... or Tools > Production > Native File Production) Indexing and Reindexing Databases Actively changed databases need frequent updating to keep the index and dictionary entries current. An index is the exclusive process of creating the database dictionary and index for the purpose of enabling full-text searching. A reindex simply updates the existing database dictionary and its corresponding index. A reindex is not an exclusive task. administrators are responsible for ensuring that all data is reviewed and proper backups are made before indexing/reindexing the database with updates. These processes are done from the File menu in, by selecting Index or

55 Installing 55 Reindex. One way to verify whether a database requires reindexing is to check the File menu in. If there is a check mark next to Reindex on the File menu, then the database dictionary is not current with additions or changes. You can also verify reindexing status on the Databases task pane at the bottom of the Current Database panel. If the active database dictionary needs updating, the panel displays Needs Reindexing. Lastly, you can query on any documents that have changed under the Search menu. There will be times when you need to perform full index updates to include modifications to the dictionary, stopwords list, and punctuation settings. This is an exclusive process and only the database administrator can access the database at the time during the process. To perform a full index, open the database, and on the File menu, click Index. Reference the following Indexing and Reindexing Checklist to ensure you have completed all necessary tasks prior to performing these processes. Checklist: Indexing and Reindexing Reindexing Did you select the Allow exclusive indexing check box on the Indexing tab in the Preferences dialog box (Tools > Preferences) in to prevent reviewers from searching during a reindex? Did you pack the dictionary to optimize reindexing speeds up to 6x? Did you set up the ReindexingDaemon_V10.xx.cpl under the Windows Task Scheduler to automate this task? Indexing Have you planned your indexing processes to run when it does not impact regular work hours? Have you considered performing a full index for individual databases locally on dedicated admin machines? *Indexing and reindexing on a separate machine will not impact Concordance Desktop Server performance. Did you send a broadcast message to alert reviewers of when indexing will occur and the timeframe for when the system may be available again? *You can do this by sending broadcast announcements from the Connections tab in the Admin Console. Did you ensure that all reviewers are logged out of and.fyi by checking the Status column on the Connections tab in the Admin Console? *Processing can take hours and impacts access to the system and work activity. You can schedule these tasks on the Jobs tab in the Admin Console.

56 56 Backups and data recovery Most Server ASPs and large firms and organizations should already have backup and data retrieval planning outlined and implemented, as well as disaster recovery protocols. Determining backup schedules for Server depends on the number of databases and users you have to manage. If you have numerous users accessing databases and running tasks, you may want to consider scheduling backups twice daily. If you only have a few databases with a handful of users accessing them, you may be able to set backup schedules to once a week. Do not perform live backups if you are using backup software that locks files, even briefly. This has been known to cause read/write functions to the database files to fail, and can cause file synchronization or corruption issues. Check with your IT group and/or backup solution provider to verify that no file locking occurs before scheduling any backups on Server and files that are in use. Be aware that anti-virus, firewall, and backup software can often interfere with network traffic and the locking of files, and in effect could cause Server software to crash. For more information about backups and data recovery, see About backups and data recovery. Updating considerations Whether you are updating, or third-party products on the server that hosts the server, you need to back up your FYI.db files first. Often administrators run patches on their servers and reboot without stopping and starting the services and backing up the FYI.db file. Doing so is a common cause for file corruption of the FYI.db file the very file you do not want to rebuild. If you reboot the server while the services are still running, it appears as a server crash to the services. Updating Guidelines: Back up the server FYI.db File - Always back up your FYI.db file before performing any updates to any products or services running on the server/computer that hosts the server. For more information about backups, see About backups and data recovery. earlier versions - Due to the new simplified installation and the new database format, there is no upgrade process from a previous version of Concordance Desktop, Concordance Native Viewer and FYI server to. If you want to open existing databases in, you need to migrate those databases to the new format. Once migrated, the databases can no longer be opened in Concordance, they can only be opened in. Therefore, we recommend backing up your databases prior to migrating them to. Please see Migrating databases for more details.

57 Installing 57 Tagging - Before migrating existing Concordance 10.x databases to, ensure that any legacy issues with tagging are resolved in the databases, or you will import those issues into. Once you migrate a database for use in, the database can no longer be opened in the previous version of Concordance, Concordance Native Viewer or server. Always back up the server FYI.db file before performing updates to the server/computer, or updates to any third-party products on the server that hosts the server. You need to shut down services for while you perform updates, otherwise you risk corruption to the FYI.db file, as the server reads a server reboot as a system crash. Moving existing databases to other servers If you need to move existing databases to another server, and need to ensure that all path information for those databases and imagebases are preserved, we recommend that you hire a consultant. You can consider creating an alias in your host file on your server, such as \\myserver.1\. This would then redirect all paths to \\myserver.2\. See your local network administrator for more information concerning your host files. Moving an existing Concordance 10.x database to another folder If you plan to migrate an existing Concordance 10.x database to, but also want to move it to another folder, first move the database to its new location and open it in Concordance 10.x. Doing so ensures that the notes DCB is properly linked to the parent DCB. Once these two steps are done, you can migrate the Concordance 10.x database to. Moving imagebases viewer If you receive an error message stating that is unable to open the corresponding document, you need to edit your folder paths. The folder path listed in the message box is the path stored in the imagebase. That path points to where your files are located, so the viewer can open and display the document. You need to change the path to the directory location where your documents actually reside. See, Renaming file paths and folders. Use caution when resetting folder paths as there is no undo function and changes are permanent. We recommend backing up the.cib file before performing this process or other imagebase management tasks.

58 58 Installing Before installing Here are some tips and information to consider prior to installing : You do not need to uninstall your existing Concordance, Concordance Native Viewer and FYI Server applications prior to installing. However, any databases created in Concordance 10.x that you want to open in will need to be migrated to the. Once a database has been migrated, you can no longer open it in the previous Concordance and FYI Server applications. Therefore, you may want to make a backup of the database prior to conversion. must be installed at its default location; you cannot use a customized location. Databases created in Concordance 9.x and below will need to be converted to Concordance 10.x databases (10.21 for E-Document databases) prior to migrating them to Concordance Desktop. Make sure that you regularly back up your server data and strongly caution users to regularly back up their data on their workstations. Do not install until your data has been backed up. Do not perform live backups if you are using backup software that locks files, even briefly. Doing so can cause read/write functions to the database files to fail, and can also cause file synchronization or corruption issues. Check with your IT group and/or backup solution provider to verify that no file locking occurs before scheduling any backups on Concordance Desktop databases. Be aware that anti-virus, firewall, and backup software can often interfere with network traffic and the locking of files, and in effect, could cause the application to crash. The default install directory for the application data files is C: \ProgramData\LexisNexis\ If you choose to uninstall FYI Server, note that the CPL and Database folders associated with that previous version are not removed. If you want to remove the folders, make sure that you back up the folders first, and then manually delete them. Before installing, check to ensure that the Microsoft.NET 3.5 and 4.0 Frameworks are installed and enabled. Before installing, be sure to review the following information about licensing, system requirements, installation changes, and database compatibilities. Licensing Application licenses are applied to only one computer, and allow for that computer to be used as a database server. Once an application license is activated on a computer, it is tied to that computer and cannot be used or moved to another computer. There are two kinds of application licenses; server and mobile. User licenses work a bit different than application licenses. They are used to access different functionality in. A single User license, for the most part can be used by multiple people, as long as they do not attempt to all use the same license at the same time. User licenses are added to a database server through the

59 Installing 59 Administration Console, and are available for use by any user who has the proper log in credentials to access the server and/or a database on that server. For more information on licensing, see About Licensing and Product Activation. For more information on obtaining licenses, please contact Sales at or LitigationSalesGroup@ReedElsevier.comm. Database compatibility Due to the major database structure changes required by the Unicode Standard, all databases need to be migrated to prior to opening those databases in. Since there is no backwards compatibility to older database versions in Concordance Desktop, version 8.x and 9.x databases must first be converted to Concordance 10.x format. When opening a 10.x database, regardless if it was a converted 8.x or 9.x database or one created in 10.x, you are prompted to migrate it to. If you choose not to migrate the database, it cannot be opened in. For more information about migrating databases, see Migrating databases. databases are not compatible with Concordance 10.x or lower, and any version of FYI Server and FYI Reviewer Installing The application can be installed on any Windows 7, Window 10, Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2 computer (for networks, this could be a server or a workstation) that will either be used as a Concordance Desktop database server, or as a reviewer's computer. To install, you simply download the application setup file, install it on a computer or server, and then if you want to use that installation as a database server, activate the server functionality with a Server license. Reviewer computers do not have to be activated. There functionality is controlled by the available user licenses on the server, and their user account access level on that server. On a single computer that is not on a network, the process is the same, except that you have to activate the installation with a Mobile license, which activates the installation as a Mobile, and enables all functionality for a single user on that computer. In a network environment, at least one computer should be designated as a Concordance Desktop database server, and be activated with a Server license. All other Concordance Desktop installations on the network (LAN or WAN) can then be used as reviewer computers. Depending on the user licenses that get added to the server, the users of the computers on which is installed, can open and work with the databases on that server. For installation on a single (non-networked) computer, a Mobile license must be activated in, to enable all functionality for a single user on that computer.

60 60 Before installing, check to ensure that the Microsoft.NET 3.5 and 4.0 Frameworks are installed and enabled. must be installed at its default location on the C drive. To install : 1. Download the installation file and save it to the computer, a network server, a flash drive, or an external usb drive. 2. Open the folder where you downloaded and saved the install file. 3. Right-click on the _Install.exe file and select Run as administrator. 4. You are asked if you want to allow the program to makes changes, click Yes to launch the installer. The Welcome to the setup wizard window opens. 5. Click Next. The License Agreement window opens.

61 Installing If you would like to print the License Agreement, click the Print button. Otherwise, continue to step Click Yes. The Start Copying Files window opens.

62 62 8. Click Next. The Ready to Install the Program window opens.

63 Installing Click Install. The Setup Status window opens, and the installation begins. A progress bar displays the status.

64 64 When the installation finishes, the Setup Status window closes. Within a brief moment, the Setup is now complete window opens.

65 Installing Click Finish. If you just installed on a server or network computer you intend to use as a database server, you need to activate the server functionality on the computer using a Server license. If this installation was on a network computer to be used by a reviewer, no activation is required. For more details regarding activation and licensing, please see the "About Licensing and Activation" topic. To set up a dedicated service account It is best practice to use a dedicated service account, instead of a local system account, to run Services to view data in the database, plan to use mapped drives or work remotely. You will want to add a use a dedicated service account with administrative rights to access the network directory where databases reside. If you do not have a valid service account set up that has rights to this directory structure, you will not be able to connect to your images or native files if they are stored on a separate server. The dedicated service account can also be the same account as the administrator account used to access the Administration Console, or you can make separate accounts for stronger security. To set up a dedicated service account, you need to set up a Microsoft Windows user account with Log on as a Service rights. The dedicated service account should be set up before installing. If you did not set up the dedicated service account before installation, you can change the logon information for the Concordance Admin Server and

66 66 Concordance Server services in the Services Manager. To change the Server service logon information in Services Manager 1. Open the services.msc file. Opening the services.msc file opens the Services dialog box. You can also open the Services dialog box from the Control Panel dialog box. From the Start menu, click Control Panel, double-click Administrative Tools, and double-click Services to open the Services dialog box. 2. Right-click Concordance Admin Server in the Name column and click Properties. Clicking Properties opens the Concordance Admin Properties (Local Computer) dialog box. 3. Click the Log On tab.

67 Installing Click the This account option. 5. Add the Microsoft Windows user account with Log on as a Service rights to the This account field. 6. Type the user account s Microsoft Windows password in the Password and Confirm password fields. 7. Click OK. 8. Repeat steps 2-8 for the Concordance Server service. 9. Stop and restart both the Concordance Admin Server and Concordance Server services. Activating/Resetting a Server or Mobile license Application licenses are applied to only one computer, and allow for that computer to be used as a database server. Once an application license is activated on a computer, it is tied to that computer and cannot be used or moved to another computer. There are two different types of application licenses: Application license Description and functionality Server Used to activate server functionality on a networked server or workstation computer. Mobile Used to activate server functionality, and enable all Concordance Desktop user functionality on a single computer, for use by only one user. To activate a Server or Mobile license: 1. Open the with your server or mobile license, and copy (CTRL + C) the license key, including the semi-colon at the end. 2. Right-click on the icon on the desktop and select Run as administrator. 3. In the User Account Control dialog box, click Yes. opens. 4. From the Help menu, click Activate. 5. In the License Key field, paste (CTRL + Z) the license key.

68 68 6. Click Activate. 7. A dialog opens asking for the port numbers for the server and the Admin Console. The defaults are for the server and 443 for the Admin Console. If you have FYI Server installed, you may need to change the defaults, as FYI Server also uses and 443 as the defaults for that products server and Administration Console. Change the defaults if necessary. If you 'Cancel' the activation at this point in time, the Admin service is not created. Your license key will be activated, but you will not be able to run the Admin Console or perform administrative tasks on the server. Run the Concordance Desktop installer and select "Repair" to remedy the issue. 8. Click OK. To reset a Server or Mobile license: 1. Right-click on the icon on your desktop and select Run as administrator. 2. In the User Account Control dialog box, click Yes. opens. 3. From the Help menu, click Activate. Before proceeding to step 4, ensure that the Admin Console is not open in. If it is left open during a reset, it can cause issues with licensing. 4. Click the Reset... button. If you do not see the Reset... button, you did not select to run as an administrator (see step 1). You will need to close the application and start again. 5. A dialog box opens asking if you are sure you want to reset now. Click Yes. The license key is reset. Installing language packs To display characters in Unicode within, the appropriate language packs need to be installed on the computer. Please go to the Microsoft web site to find out how to install language packs for your version of the Windows operating system.

69 Installing 69 Registry key locations The registry settings are stored in the same places relative to the new key names: Registry key locations for are: HKEY_CURRENT_USER\Software\LexisNexis\ (32-bit) HKEY_LOCAL_MACHINE\Software\Wow6432Node\LexisNexis\\Settings (64-bit) also has a Registry value for the snapshot path: HKEY_CURRENT_USER\Software\LexisNexis\\Settings\AutoSave It holds the path to the snapshot for the current user, which is: <drive>:\documents and Settings\<username>\My Documents\ \autosave.snp Performing silent installs When you need to install and activate on numerous machines, you can save time by running silent installations of on each machine. Silent installations use a setup.iss InstallShield Silent response file to run an installation. Silent installations install applications without prompting you for input during the installation. To install using a silent installation, you will first need to create a setup.iss file. This setup.iss file only needs to be created once. When you are creating the setup.iss file, you will be running a normal installation on a machine and will be recording each step and setting of the installation process for the setup.iss file. After the setup.iss file is created, this file can be used any time you want to run a silent Concordance Desktop installation on a machine. To create a setup.iss file for installing : 1. Click Start, and then click Run. 2. Type cmd in the Open field and click OK to open the cmd.exe command prompt. 3. Do one of the following: Type the path to the _Install.exe file followed by -r and press Enter. For example: w:\concordance desktop_install.exe -r Run the _Install.exe directly on the workstation and complete all of the installation and activation steps. When the installation is complete, the setup.iss file is created in the \WINDOWS subdirectory.

70 70 The setup.iss file contains a record of the actions you performed for each installation dialog box. Best practice is to store the setup.iss, and the installation together in a network folder that you can access from each machine on which you will be running a silent install. 4. Create a network folder and add the following files to the folder: setup.iss _Install.exe To install using a setup.iss file: 1. Click Start, and then click Run. 2. Type cmd in the Open field and click OK to open the cmd.exe command prompt. 3. Type [path to the _Install.exe file] -s -f1[path to the setup.iss files] and press Enter to silently install. For example: w:\concordance desktop_install.exe -s -f1w:\setup.iss The -s parameter tells InstallShield that you are running a silent operation, and the -f1 parameter indicates where the setup.iss file is located. Note that there is a space between the -s and -f1 parameters, but there is no space between -f1 and the path to the setup.iss file. Silent installation programs do not display error or status messages, such as Setup is now complete, during the installation. By default, silent installation status and error information is recorded in the setup.log file. The setup.log file is automatically created in the same directory where the setup.iss file is located. If the setup completes, the setup.log file should contain the following information: [InstallShield Silent] Version=v7.00 File=Log File [ResponseResult] ResultCode=0 [Application] Name= Company=LexisNexis Lang=0009 Result codes indicate whether an installation was successful or there were errors during the installation. A 0 in the ResultCode field indicates the installation was successful. For more information about the setup.log file, including a list of result codes and their definitions, see the Checking for Errors Using the Setup.log File Help topic in following Web site: Click the Search button in the Flexera Software Web site and search for setup.log to view the Help topic and other relevant Help topics.

71 Installing 71 Customizing the start-up view In, there are four settings you can define to customize what you will see when you open : Initial browse path Default database view Most recently used list Workspace tab display To customize the Concordance start-up view 1. On the Tools menu, click Preferences to open the General tab in Preferences dialog box. 2. In the Initial Browse Path field, click the ellipsis (...) button and browse to the folder you want to be the initial folder that opens when browsing for a file or opening a new database. For example, entering C:\LexisNexis\Databases\ opens this folder when opening a database in the Databases task pane. 3. In the Default view field, select Browse or Table. The view you select is displayed when you open a database in. 4. In the Number of MRU items field, type or scroll to the number of files to list in the most recently used (MRU) file list. Your MRU list is displayed in the File menu and the Recent panel in the Databases task pane. The maximum number of files you can display is 9. If a user's MRU list in the File menu or Databases task pane is blank, your company may have a policy preventing the user's computer from writing to the MRU registry key: HKEY_CURRENT_USER\Software\LexisNexis\\Recent File List

72 72 By default, the Workspace tab is displayed and contains links to the LexisNexis Web site. You can customize your Workspace tab to display internal or external Web pages simply by adding a link to an external HTML web page or to a locally stored.htm or.html file with information you d like to publish for user reference. 5. In the Workspace section, the Enable workspace check box is selected by default. To continue displaying the Workspace tab in, leave the Enable workspace check box selected. If you do not want to display the Workspace tab, clear the check box. 6. If you want the Workspace tab settings to apply to all users in all databases, in the Apply to field, choose <All databases, all users>. If you only want the Workspace tab settings to only apply to the local user, choose <local user only>. 7. To add a link to an external HTML Web page, in the URL field, enter the Web site URL. Be sure to include or in the URL. For example: concordance. To add a link to an internal internal.htm file located on your server, in the URL field, enter the full UNC path. For example: J:\LexisNexis\Internal_Links.htm OR \\MyServer \MyFolder\myhtm.htm.