I think that this "trick" needs more research.
Theoretically if the task is set up to run the application as the admin user with the correct password and with the highest credentials - it should run without the elevation prompt
If the task is then set to run at the login of another user the access level of the user should not matter
This is I'm sure what used to happen with the "AT" command which the command underneath the task scheduler GUI, Obviously there is the now extra step of the UAC.
Will try to find an app that has the issue and try various task set-ups, though not sure when time will be available - there is also the issue of apps that are written pre UAC and those which are UAC aware - will these behave differently
It may be that this is an oversight, (OK Bug!
), on Microsoft's part - if so I can see this causing major
issues in the enterprise where this requirement is a common one