Skip to main content Skip to complementary content
Qlik Resources

Running Replicate under a different account

You can run Replicate under an account with less privileges than the default account. Both the Qlik Replicate Server service and the Qlik Replicate UI Server service can be run under different accounts, as described in the following sections.

Information note

  • The Salesforce and MongoDB source endpoints are not supported when Replicate is run under a non-admin account.

  • As some endpoints may require stronger privileges than others, running Replicate under an account with insufficient privileges may cause replication issues.

Changing the Qlik Replicate Server Service account

Changing the default Qlik Replicate Server Service Log On user for admin users

  1. Add the user to the "Log on as a service" policy in the "Local Security Policy".
  2. Edit the Qlik Replicate Server service to log on with the user.
  3. Restart the Qlik Replicate Server service.
  4. Open Task Manager and verify that the repctl.exe process is running under the specified user.

Changing the default Qlik Replicate Server Service Log On user for non-admin users

Information noteIf you already performed this procedure in an earlier version of Replicate, you only need to perform the additional steps described in Steps required after upgrading to Replicate November 2022 or later below.
  1. Add the user to the "Log on as a service" policy in the "Local Security Policy".

  2. Set the user as the Owner of the log.key, mk.dat, and muk.dat files.

    The default location of these files is:

    C:\Program Files\Attunity\Replicate\data

  3. Grant the user full control over the log.key, mk.dat, and muk.dat files.

  4. Grant the user full control over the following registry entries:

    HKEY_LOCAL_MACHINE\SOFTWARE\Qlik\Qlik Replicate

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\Repctl.exe

  5. Grant the user full control over the Replicate jvm folder

    The default location of this folder is:

    C:\Program Files\Attunity\Replicate\jvm

  6. For both the <INSTALL-DIR>\Attunity\Replicate and <INSTALL-DIR>\Attunity\Replicate\data folders, open the folder properties and set the folder permissions as follows:

    1. Grant the user full control.
    2. Click the Advanced button.
    3. In the Permissions tab, click the Change permissions button.
    4. Select Replace all child object permission entries with inheritable permission entries from this object and click OK.
  7. Grant the user write permission on <INSTALL-DIR>\Attunity\Replicate\endpoint_srv\bin.

  8. If you have not yet registered your Replicate license, register it now.

  9. Verify that the muk.dat file exists in <INSTALL-DIR>\Attunity\Replicate\endpoint_srv\data and then grant the user full control over this folder.

  10. Grant the user full control over any target folders defined in relevant target endpoints (for example, the Target folder specified in the File target endpoint settings).

  11. If execution of user-defined commands is allowed, add the user to the "Replace a process level token" policy in "Local Security Policy".

  12. Edit the Qlik Replicate Server service to log on with the specified user.
  13. Stop the Qlik Replicate UI Server service.
  14. Restart the Qlik Replicate Server service.
  15. Start the Qlik Replicate UI Server service.
  16. Open Task Manager and verify that the repctl.exe process is running under the specified user.

Steps required after upgrading to Replicate November 2022 or later

If you already performed the Changing the default Qlik Replicate Server Service Log On user for non-admin users procedure in an earlier version of Replicate, after upgrading to Replicate November 2022, you need to perform the following additional steps:

  1. Edit the Qlik Replicate Server service to log on with the user you added to the "Log on as a service" policy (in the "Local Security Policy").

  2. Grant the user full control over the following registry entry:

    HKEY_LOCAL_MACHINE\SOFTWARE\Qlik\Qlik Replicate

  3. Stop the Qlik Replicate UI Server service.
  4. Restart the Qlik Replicate Server service.
  5. Start the Qlik Replicate UI Server service.

Changing the Qlik Replicate UI Server Service Account

Information note

The user can either be an admin user or a non-admin user. If you change the user to a non-admin user, the user must be the same as the non-admin user set in Changing the Qlik Replicate Server Service account above (assuming that a non-admin user was set).

To change the default Qlik Replicate UI Server Service Log On user:

  1. Open a command prompt and run the following commands:

    1. Delete the existing user (if there is one), by running the following commands:

      netsh http delete urlacl url=http://+:80/AttunityReplicate

      netsh http delete urlacl url=https://+:443/AttunityReplicate

    2. To add the user, run the following commands (where username is replaced by the name of the user):

      netsh http add urlacl url=http://+:80/AttunityReplicate user=Username

      netsh http add urlacl url=https://+:443/AttunityReplicate user=Username

  2. Edit the Qlik Replicate UI Server service to log on with the new user.
  3. Restart the Qlik Replicate UI Server service.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!

Leave your feedback here