We recently updated LDMS from 9.0 to 9.5
As part of that transition, we migrated all of our provisioning templates that install software on new machines to the new core.
We found, however, that these tasks (mostly Execute File tasks) now seem to always run as the System user, but in 9.0, these ran as the current user logged into the machine. This mean we could actually see the software installing silently, but if there was an error and a exe hung up, we would be able to fix them easily. Now we don't see any feedback for the app, our only option is to kill the process and let the rest of the template finish.
Is there anyway get back to having these tasks run as the current user? Since this is run during provisioning of a new computer, the local admin is logged in and permisisons are not an issue. We also don't ever run provisioning on deployed machines with active endusers.
We have tried various RunAsUser commands and tools with varying success, but we would prefer not to pass around passwords and need to prepend every task with another executable
Has anyone else seen this issue? Anyway arround it? Any settings we can tweak to change the user tasks execute as?