The advice notes on this page cover:
- Configuring the security
- Answer common questions
- Requirements
If you cannot find information related to you specific problem here, please contact support using the Contact Us page.
Network/Multi-user Installations
Advice and guidance on configuration
CRS Risk - Risk Assessment Toolkit by default will install all application files and the database onto the local computer. However, this is not required or recommended (unless you have only 1 PC to install the software on and no network server)
Reasons for moving the database to a network server include:
- Separates application and data - removes single point of failure
- Includes the database file in the nightly backup for security
- Allows additional clients to be installed and share the data (licenses permitting)
Standlone installation
Installing the software as standalone, on a single PC
Database must be backed up onto CD or other media frequently to prevent loss of data in a disaster scenario.
Single PC, Networked database
The advantage of this scenario, is that the database can be backed up with the server data, reduces the workload on the local computer, and enables the database to be shared with other clients (licenses permitting).
When installing additional clients, during the installation simply 'Join an existing network' and provide the required information (location of database and administrator password). See below for the diagram of a multi-user installation.
Multi-user Installation
Important Information for multi-user installations
You will need to obtain a license for each PC or Client that has the software installed. If you install the software to a Terminal Server i.e. Citrix® Metaframe or Microsoft® Terminal Server, you will still need to purchase licenses for the number of sessions required to serve the users.
The location of the database is stored in the registry, it is important to note that the database location must be common to all client PC's, i.e. the drive mapping must use the same drive letter. Failure to do this, could result in clients unable to locate the database.
Your network administrator will need to ensure that the correct permissions are set on the folder containing the database. Users must, at least, have Read/Write permissions to the directory.
Further information is included in the online help files included with the software.