Read/write permissions for timeSensor LEGAL under Windows

Read/write permissions for timeSensor LEGAL under Windows

This article has been machine translated. If you find any errors, we would be grateful if you could report them to translation@timesensor.com.

General

Many errors around the automatic update of the server or the client are related to insufficient write permissions under Windows. This article summarises some general guidelines again.

Server installation under Windows Server 2016 or 2019

  1. Both Windows Server variants are supported. In case of doubt, we recommend using Windows Server 2019.
  2. A local user account must be set up on the server. This may or may not have administration rights. We recommend choosing the user name for the local user account as follows:
    1. timeSensorAdmin -> if the local user account has administration rights.
    2. timeSensorDBA -> if the local user account does not have administration rights.
  3. The timeSensor LEGAL software must be installed in this local user account. The database server must first be started in this user account with administration rights ("Run as Administrator"). This will create all settings, links and help files with the correct permissions.
  4. Then it is recommended to install the database server as a service.
  5. If the server is not to run as a service, it must be started normally (i.e. just not as administrator).

Client installation under Windows

  1. If the timeSensor client is installed in a location where the logged-in user does not have read/write access, the system administrator must update the client every time the database version changes. This slows down the automatic update of the client application.
  2. Therefore, it is advantageous to install the client once for each user in a directory in which the logged-in user has read/write access. This then enables an automatic update of the client whenever the version of the database changes. In order to provide this convenience for the administrator, it is necessary to provide each user with an individual copy of the client. In other words, there must be no instantiation of the client application.