Scheduled task runs for longer than expected

Question

Hi

Because we are in the process of integrating a new company, we need to create their new users in their old domain and then migrate across using ADMT.
Once migrated, we need to add a few attributes, move to a new OU and force a replication to a DC in a remote office.

The process runs like so:

• 1. Scheduled task modifies 3 user attributes (Company, Office and Extension Attribute 7)
  2. Business rule 1 catches the user modification and sets the UPN based on a custom command (I tried to put this into the scheduled task, but got an error with the SetModifiedPropertyValue command) then moves the account to a different OU
  3. Business rule 2 catches the move and a powershell script waits to make sure a specific local DC is up to date with the UPN, then forces a sync with the remote DC

The issue is that when I run the scheduled task, I would expect it to run for a few seconds at most, but 5 minutes later it is still reporting that it is running.
Would the business rules be classed as part of the scheduled task?

Thanks

Matt

Answer 1

Hello,

Would the business rules be classed as part of the scheduled task?

Yes, after the Scheduled Task updates a user, it waits for all the Business Rules to execute before updating the next user. Most probably, the delay is in majority caused by the second Business Rule.

Comments

Hi

That's fine, I just wanted to check.
Thanks for the information.

Matt