We have a large number of VisualCron instances, these run a lot of Windows Processes (Task Process Execute.) These tasks access stored AD credentials to authenticate against a range of resources DBs, File Shares, Services, APIs etc.
Upgrading to 8.2.7 caused any of the above tasks to fail to access any authenticated resources eg file shares. This may or may not result in an actual VC task failure dependent on the program logic. Further investigation showed: tasks were no longer being executed with the supplied AD credentials but run as the SYSTEM user. This behaviour occurred for separate upgrades for 7.7.5, 8.02 and 8.1.2.
Turning on extended debugging showed that the credentials has all been switched from CreateProcessWithLogonW to CreateProcessAsUserW silently on upgrade.
If this is correct it presents us with a number of problems
- It looks as though we will need to check the credentials for every execute task check the settings before the update and restore back to CreateProcessWithLogonW. then individually verify that tasks are still working.
- We now need to keep verbose debugging enabled to view/alter the credentials settings. This exposes a whole range of additional settings we'd rather end users went nowhere near as these can lead to even more issues. I'm not sure what the constraints are here, but I think it would be useful to have the WIN32 Execution option displayed/modifiable without having to enable extended debugging ie
Edited by user
| Reason: edit