Transition to STP User Management

Preparations

  • Install the STP User Management Service (at least version 1.6.512) on the server.

  • Install the STP User Management Application (at least version 1.6.512) on the server.

  • Update STP Documents to the latest version if necessary.

  • If you are also using STP Lexolution (formerly LEXolution.KMS), you should uniquely name groups in both applications before switching to STP User Management. If groups with the same name are used in STP Lexolution and STP Documents, only one group with that name will be created when switching to STP User Management. All users assigned to the groups from STP Documents and STP Lexolution will be assigned to this group. For example, if more than one server is configured against the Service Bus (SB), you must also add the system identifiers to the groups. (see the second-to-last point)

  • If more than one server is configured against the Service Bus (SB), the system identifiers in the configuration file STP.Ecm.Remoting Server.exe.config must be made unique.

    <add key="LsbIdentifier" value="main"></add>

    To do this, start a text editor with the option "Run as administrator", load the configuration files into the text editor, and change the value for "main" accordingly. Save the configuration file.

  • Check if there are users in the system where all three checkboxes for Hidden, Locked, and Restricted User are checked. If such users exist, please remove the Restricted User checkbox before migration.

  • Stop the STP User Management Service for STP User Management.

Execution

Important Notes

Check if the service for the server starts without STP User Management after updating to the latest version of STP Documents. Resolve any issues that may arise before switching to STP User Management.

If you are using STP Documents, STP Documents (formerly LEXolution.KMS), and winsolvenz.p4, we strongly recommend completing the switch to STP User Management for STP Documents first, and copying the SQLITE database for STP User Management to a secure location. If problems occur during the migration of winsolvenz.p4 and STP Lexolution to STP User Management, you can safely repeat the migration after resolving the causes of the issues.

Check if the service for the winsolvenz.p4 server starts without STP User Management after updating to the latest version of winsolvenz.p4. Resolve any issues that may arise before switching to STP User Management.

Then switch winsolvenz.p4 to STP User Management. Also, back up the winsolvenz database and the SQLITE database for STP User Management after the switch.

Check if the service for the STP Lexolution server starts without STP User Management after updating to the latest version of STP Lexolution. Resolve any issues that may arise before switching to STP User Management.

Then switch STP Lexolution to STP User Management. Also, back up the STP Lexolution database and the SQLITE database for STP User Management after the switch.

To switch STP Documents to STP User Management, follow these steps:

  • Stop the STP LEXolution.DMS Server service (for STP Documents!).

  • Back up the STP Documents database.

  • In SQL Server Management Studio, delete the row with the GUID "502B20BA-1024-4E89-AC02-12577DFD9D49" in the "Name" column from the "tblFlag" table in the STP Documents database.

  • Ensure that the STP User Management Service is running.

  • Start the STP LEXolution.DMS Server service.

  • Wait about 5 minutes until the migration of users to STP User Management is complete and check the server log file to see if the entry "Migration finished" has been written.

  • Start the STP User Management Application and log in as STPAdmin.

  • Check that all users and groups have been correctly transferred and that the two system groups "Administrators" and "All" have been renamed to "Administrators DMS (<System Identifier>)" and "All DMS (<System Identifier>)". The default value for the system identifier is "main".

  • Start the standard DESK and log in with a valid user.

    Note

    If the user being used is not marked as a domain user in the STP User Management Application, you must add a user password in the STP User Management Application. The passwords from the old user and group management in the office settings of the standard DESK can no longer be used for logging into the standard DESK and the Outlook DESK.

  • Check in the office settings that the role management is now displayed instead of the previous user management. Check in the role management that all groups are still assigned the correct roles.

  • After the update, back up the STP Documents database and the database file CommonData.db. Ensure that the database backup file created by the SQL Server (e.g., LEXolution.bak) can be clearly associated with the backed-up copy of the database file CommonData.db for STP User Management when restoring.

    Note

    Please note that after switching to the new user and group management via STP User Management, the SQLITE database file CommonData.db for user management in the directory C:\ProgramData\STP AG\STP UserManagement must also be backed up when backing up the STP Documents database.

    When restoring the STP Documents database, the database file CommonData.db associated with the database backup must also be copied to the directory C:\ProgramData\STP AG\STP UserManagement.

Related to