Security Compliance

How to update the AD user account used in existing scheduled tasks in ARM

This article explains how to update the AD user account used in existing scheduled tasks in ARM. Since ARM does not allow direct modification of the user through the UI, the modification must be performed in the database

First published date

12/3/2025 12:48 PM

Last published date

1/9/2026 9:57 PM

Overview

Some ARM environments rely on automated jobs, such as recurring password change tasks or one-time scheduled actions that run under an AD user account.

If this account is modified or removed for security or operational reasons (for example, deletion, permission changes), any scheduled tasks using that account may fail.

Since ARM does not provide a built-in option to change the credentials associated with existing scheduled tasks, administrators must manually update this information in the ARM database.

Product section

Access Rights Manager

Resolution

1 - Before proceeding, please ensure that you take a backup of the database.

2 - In the scripts below, please update the following:

  • Query 1: Run the first query only if the users are in a different domain. Replace 'newdomain' and 'olddomain' with the correct NetBIOS domain name
  • Query 2: Replace 'new.aduser' with the correct new AD user. Replace 'old.aduser' with the correct old AD user
  • Query 3: Same as query 2.
-- Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further
-- disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose. The risk arising
-- out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation,
-- production, or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits, business
-- interruption, loss of business information, or other pecuniary loss) arising
-- out of the use of or inability to use the scripts or documentation.

-- Query 1
UPDATE _jobconfig_object_values
SET _value = 'newdomain'
WHERE _property = 'windowscredential.domain' AND _value = 'olddomain'

-- Query 2
UPDATE _jobconfig_object_values
SET _value = 'new.aduser'
WHERE _property = 'windowscredential.username' AND _value = 'old.aduser'

-- Query 3
UPDATE _jobconfig_object_values
SET _value = 'new.aduser'
WHERE _property = 'username' AND _value = 'old.aduser'


3 - Restart the ARM service on the ARM server.

After applying these changes, the old tasks should run with the updated AD user.