You need to launch a file as the System account to verify access rights, test network access, test LiveUpdate, look at proxy settings or to try to install using a non-user based account but have found the new security changes in the Microsoft Windows kernel 6 or greater prevents the AT task scheduler from launching an "interactive" application with system level access.
Changes in the Windows account security prevents direct access from the command line to the task schedulers ability to create a local session-0 interactive system account run applications. This issue will apply to any Windows operating system running kernel 6 or greater. (Vista, Windows 7, Server 2008, Server 2008 R2 for all 32-bit and 64-bit variants as well as Itanium.)
When you try to use the AT scheduler with the /interactive switch you will get the following window:
If you use the Windows built-in GUI task scheduler or the Schtasks tool, you will be able to assign the System account to launch the application but you will not be able to see or interact with the application now due to security changes in Windows. The application will show in the Task Manager but that is the total level of interaction ALL local users will get.
This is new behavior that was introduced in Vista's security model and has been implemented into Windows 7 and all Windows Server 2008 families.
It is possible to launch a local Session 0, user-accessible win32 application using System account privileges using the third party tool called PSExec from Microsoft.
The command line is:
psexec -i -s [path to executable and/or script]
(The -s switch runs as System; the -i switch runs as Interactive.)
Please note, include the path in quotes if the executable resides in any folder that has spaces or is more then 8 characters long.
Example : psexec -i -s "C:\Program Files\Internet Explorer\iexplore.exe"
This will launch two windows:
"Service Changes for Windows Vista," which discusses the changes in the security model: