Instructions for changing User names and Password

📘

All commands should be executed with elevated privileges.

Instructions for changing the Install user

The software upgrades should be performed under the original installer user so that the protected setup parameters will be available during the upgrade. If the installer user becomes unavailable for some reason, the setup parameters must be copied to another user account that has administrator privileges as follows.

  1. Log on with the new installer user account
  2. Stop RTDB
  3. Copy the file SetupAnswers%app_dsn%.bat from the userprofile directory of the old installer account from directory %userprofile%\abb oy\Parameters to the corresponding userprofile directory of the new user.
    md "%userprofile%\abb oy\Parameters"
    copy "c:\users\admin1\abb oy\Parameters\Setup_Answers_*.bat" "%userprofile%\abb oy\Parameters"
    # Where,
    # admin1 is the old user name
  4. Modify the Windows vault entries "CPIMS/ADMIN" and "CPIMS/DBADMIN" and (in case this is the DCN node, also) "CPIMS/MAIN_DBADMIN" replace old username and password with New username and password. Follow the below sections for making corresponding changes.

Instructions for changing both name and password of the Admin user

The adminuser user account is used for running the RTDB-Scheduler and some other services. The name of the user account has been provided as a setup parameter during the installation. The adminuser must have administrator privileges (or other privileges for running as a service and accessing the database tables locally).

If the user account needs to be changed for some reason, this can be done (after updating the username or password first in Windows) as follows

  1. Log on to the system with current install user.

  2. Stop RTDB.

  3. Store the name and password of the new account to the Windows vault entry "CPIMS/ADMIN"

  4. Add the user to the RTDB-Admin group by running following command.

    "%app_root%\Config\Security\APP_Create_users.bat"
  5. Reinstall the services

    "%app_root%\config\application\APP_Install_Services" /remove all
    "%app_root%\config\application\APP_Install_Services" /install all
     
    ## Set the startup type of RTDB main service back to Automatic, for example with command:
       e.g.,
         sc config "RTDB D RTDBData" start= auto
    
  6. If this is the main node of a hierarchical set up, force re-registration of the DCN nodes this is needed so that the new adminuser will know the access information to the DCN nodes. (Make sure to perform these steps after RTDB is started in Main node after making all the changes)

    praotstx %app_dsn% -sql "delete from simpleconfig where sectionname like 'DatabaseNodes_%' and KeyName like 'Added_%'"

    restart RTDB-Scheduler in all DCN nodes.

  7. Optionally clean up the Vault entries for the old adminuser (the names of the vault entries start with "CPIMS/" or "CPIMS_DC/").

Instructions for changing only Admin user's password and the user name is unchanged

It is recommended that the password of the adminuser is non-expiring.

However, if you are forced to change the password, you can follow the same instructions as in "Instructions for changing both name and password of the Admin user", but skip these steps:
Step 4. Add the user to the RTDB-Admin group
Step 6. force re-registration of the DCN nodes
Step 7. clean up the Vault entries for the old adminuser

Instructions for changing both username and password of the DBAdmin user

The dbadminuser user account is used for applications to connect to the RTDB database either with Vtrin or ODBC connection. Note that the dbadmin user must be same for all replica nodes of a high availability system (either a user account in the common domain, or a local user account with same name and password).

If the user account needs to be changed for some reason, this can be done (after updating the username or password first in Windows) as follows:

  1. Log on to the system with current install user
  2. Store the name and password of the new account to the Windows vault entry "CPIMS/DBADMIN"
  3. Add the user to the RTDB-Admin group by runnning.
    "%app_root%\Config\Security\APP_Create_users.bat"
  4. Provide the new value to the adminuser (this step is optional if the logged on user is the adminuser), run the folowin command.
     %app_root%\config\featureinstall\APP_Give_Setup_Answers_to_adminuser.bat
  5. If this is the main node, you need to tell the new user name and password to each data collector node.
    Log on to the data collector node with the user account that was originally used for installing RTDB.
    Update the vault information for entry "CPIMS/MAIN_DBADMIN"
  6. If this is a DCN node, force re-registration of the DCN node to the main node.
    Run below command in Main Node and restart RTDB-Scheduler service in DCN
    praotstx %app_dsn% -sql "delete from simpleconfig where sectionname like 'DatabaseNodes_%' and KeyName like 'Added_NN'"
    		## where NN is the name of the DCN node
  7. Restart Vtrinlink in main server

Instructions for changing only DBAdmin user's password and the user name is unchanged

It is recommended that the password of the dbadminuser is non-expiring.

However, if you are forced to change the password, you can follow the same instructions as in "Instructions for changing both username and password of the DBAdmin user"
skip this step from the section:
Step 3 - Add the user to the RTDB-Admin group