<< Click to Display Table of Contents >> Navigation:  Installing > Installing Concordance Desktop > Before installing Concordance Desktop

Here are some tips and information to consider prior to installing Concordance Desktop:

•You do not need to uninstall your existing Concordance, viewer and FYI Server applications prior to installing Concordance Desktop. However, any databases created in Concordance 10.x that you want to open in Concordance Desktop will need to be migrated to the Concordance Desktop. 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.

•Concordance Desktop 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 Concordance Desktop 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 Concordance Desktop application to crash.

•The default install directory for the Concordance Desktop application data files is C:\ProgramData\LexisNexis\Concordance Desktop

•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 Concordance Desktop, be sure to review the following information about Concordance Desktop 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 Concordance Desktop 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 Concordance Desktop. 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 Concordance Desktop database server through the Administration Console, and are available for use by any user who has the proper log in credentials to access the Concordance Desktop 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 Concordance Desktop Sales by e-mail at Sales@cloudnine.com.

Database Compatibility

Due to the major database structure changes required by the Unicode Standard, all databases need to be migrated to Concordance Desktop prior to opening those databases in Concordance Desktop.

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 Concordance Desktop. If you choose not to migrate the database, it cannot be opened in Concordance Desktop.

For more information about migrating databases, see Migrating databases.