When a job is configured to run under the computer's built-in Administrator account, adTempus may log warning ADT005458W each time the job runs:

Job is configured to run with Administrator privileges but user .\administrator is not an Administrator. The job will run with normal privileges.

This issue occurs if all the following conditions are true:

  • The job is configured to use the computer's built-in Administrator account (even if the account has been renamed to something other than "administrator")
  • The job is configured with the option to Run with highest privileges checked
  • In the computer's Local Security Policy, the policy "User Account Control: Admin Approval Mode for the Built-in Administrator account" is not set to "Enabled".


When the security policy is configured as described above, the built-in Administrator account (but not other members of the Administrator group) always run with elevated privileges ("As Administrator"). Because of this adTempus is unable to elevate the user's logon session, and therefore mistakenly believes the user is not an Administrator.


This warning message can be ignored, as the built-in Administrator account will still be executing with elevated privileges. To avoid the warning you can:

  • Uncheck the Run with highest privileges option, or
  • Change the job to run under an account other than the built-in Administrator account, or


  • adTempus 4
    This issue has been resolved. Resolved in version 4.9.