Hello. I upgraded from ADManager Plus 32 bit to 64 bit and the problem I was having with the Disable Policy not passing Arg1 into the Powershell has returned.

For some reason the Disable Policy script is not passing the %USERNAME% as a variable into the powershell script.

The custom script call that I am using is: Powershell -ExecutionPolicy Unrestricted ./disablescript.ps1 -Arg1 %USERNAME%

This returns the following error: Custom Script Result :D:\ManageEngine\ADManager Plus\bin\disablescript.ps1 : Missing an argument for parameter 'Arg1'.

I have a few automated jobs running that call powershell scripts that are working fine using this exact same set of commands. Is there a difference how powershell requests are processed between the Disable Policy and the Automated Jobs?

Please let me know if there are any errors with my commands or any ideas on resolving. Thank you for your time and and assistance.

James