GPO Scheduled Task: Error 0XA on new workstation
Published: Dec 21, 2020 - 11:33
Hello everyone,
I'm a WAPT user on a Windows 10 network, and we're deploying the WAPT agent via a Group Policy Object (GPO). The GPO copies the waptdeploy.exe and waptagent.exe files to c:\windows temp and then creates a local scheduled task running under the system account.
This all worked perfectly until recently (around 150 workstations deployed this way), but for the past few days, the task has been failing with a 0xA error (incorrect environment). The file copying is successful on these workstations, and the task is correctly created and runs successfully.
Here is the task's argument.
--hash=76ce8c03c9f514a6b3803804bf75c9d4286483e1f1f66ec2a0cbbf644b2d8195 --minversion=1.8.2.7269 --waptsetupurl=c:\windows\temp\waptagent.exe --wait=15
We've been looking for the source of the problem for a while now, but we can't find it. Manual installation is OK. We're stuck.
If you have any ideas, we'd appreciate it.
Thanks,
I'm a WAPT user on a Windows 10 network, and we're deploying the WAPT agent via a Group Policy Object (GPO). The GPO copies the waptdeploy.exe and waptagent.exe files to c:\windows temp and then creates a local scheduled task running under the system account.
This all worked perfectly until recently (around 150 workstations deployed this way), but for the past few days, the task has been failing with a 0xA error (incorrect environment). The file copying is successful on these workstations, and the task is correctly created and runs successfully.
Here is the task's argument.
--hash=76ce8c03c9f514a6b3803804bf75c9d4286483e1f1f66ec2a0cbbf644b2d8195 --minversion=1.8.2.7269 --waptsetupurl=c:\windows\temp\waptagent.exe --wait=15
We've been looking for the source of the problem for a while now, but we can't find it. Manual installation is OK. We're stuck.
If you have any ideas, we'd appreciate it.
Thanks,
