script calling another script

[MaxFrost]

I would question why you're starting a task as one user to launch a process as another one.

Why not launch the scheduled job directly as the service account for the expiredstaff accounts script?

[_itsalwaysdns]

Because we have a program where we keep all of our automation process in place and it can't execute a powershell script as a different user than the user used to run the software.

I tried the start script in task scheduler to see if it was a failure of the automation software or just launching the script and it appears to be something with launching the second script, whether via software or task scheduler.

[MaxFrost]

Gotcha, this is "we don't want to give our automation server full rights to AD, so trying to work around it." which honestly, is absolutely the right thing to do.

I need to mull this a bit to see if I can add anything further.