Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Currently, the environment is running Qlik Sense 3.1 SR5, on synchronized persistence. Also, the services are being run by the Local System account.
In attempting to upgrade to a later version and Shared Persistence, the installer prompts that the services cannot be run under Local System.
I cannot find anything related to 3.1 or earlier versions and changing the service account from Local System to a domain account. The only documentation i can find relates to changing the account during the installation, before the services start. I'm wondering if it can be done with an existing environment.
Any thoughts/suggestions?
Thanks!
I'd strongly suggest an upgrade to something released after 2016 😄
This is going to be from memory since it has been a while since I used 3.x and much less synchronized persistence. I'll chop up the instructions from https://support.qlik.com/articles/000049699 and remove the shared persistence stuff. Again, it'll be from memory.
From there, you're going to want to change the account / password used by the data connections which start with qrs (I believe that's the old format, it's now monitor_apps...).
On Shared Persistence builds, you need to do explicit stuff to handle certificate regeneration but I don't recall that being needed on Synchronized Persistence.
Hope that helps
I'd strongly suggest an upgrade to something released after 2016 😄
This is going to be from memory since it has been a while since I used 3.x and much less synchronized persistence. I'll chop up the instructions from https://support.qlik.com/articles/000049699 and remove the shared persistence stuff. Again, it'll be from memory.
From there, you're going to want to change the account / password used by the data connections which start with qrs (I believe that's the old format, it's now monitor_apps...).
On Shared Persistence builds, you need to do explicit stuff to handle certificate regeneration but I don't recall that being needed on Synchronized Persistence.
Hope that helps