If you have a user that you need to delete, but they have active tasks, go to the Process Monitor (Activity Window), and find all of the tasks owned by that user. You may need to use the non-hierarchal mode to find all of them. When you have found all of the tasks, highlight them, right-click and select "Take over task" (assuming you have that privilege). Then all of those tasks will now appear to be started by you. When the use no longer has any tasks in the Process Monitor, you should be able to remove them. If you don't see the "Take over task" option, you may not have the required privilege.
Original Message:
Sent: 01-31-2018 09:50 AM
From: Carsten Schmitz
Subject: Access Denied.
Well, UC4 would not let you delete a user who has active schedulers if it's a UC4 "native" account, but this probably breaks down for AD accounts.
I am not aware of any mechanism to automatically substitute users that don't exist anymore with other users. So if you remove an account from AD that has active schedulers, I believe you will have to stop those schedulers and start them again with a different user, manually.
One could argue that this is by design, because in some situations you would not want jobs to run with locked or removed accounts.
The best you can probably do, unless an expert here proves this wrong, is to run your major schedulers with generic users (something like "GROUP_SAP" instead of "JOHN_DOE"), or have a script/SQL statement that regulary checks ownership of schedulers vs. AD accounts and alerts you about any potential problems. Beyond that, I at least don't know of any native way to deal with this.