1400 requests at same time

[Luiz Lucena]

Hi everyone, 

I'm facing a little challenge. We have created a workflow (legacy) around 8 years ago, for our user termination process. This workflow is divided into two subflows, one for automated processes and one for manual processes. 

The account to be disabled is an AD account, so it will call a PowerShell script on the MID server (one of four servers), run the Disable AD User script, return the script output to the instance. Process the other tasks in the two workflows.

We never predicted a bulk operation for this process, so this runs on one terminated user at a time. 

The challenge is, business came up with a requirement without further notice that we need to deactivate around 1400 inactive accounts due to cleanup process. They want to use the current process due to auditing reasons.

I know I can run a Fix Script to call that requested item for each user matching the criteria, but my main concern. is regarding the MID servers and all the other operations they might be performing when we trigger this operation.

For example, the MID servers will be handling ALL other requests as usual, scheduled jobs, etc. 

Let me know your thoughts on this.

[GlideFather]

Hi @Luiz Lucena,

in my perspective it strongly depends on how the user management is handled. Because deactivating any user in ServiceNow while having an integration/provisioning with LDAP will result in re-activating the user again as the LDAP is usually the source of truth...

So I would focus on this as first. Are you sure that this 1400 users to deactivate will not be overwritten with the first sync?

Also, in the script you can add autoSysFields(false); which means that your script will do what you wrote but will not update the Updated and Updated by values. Same for setWorklow(false); which will not cause any other actions related to the deactivation - e.g. notifications, events, etc.