Often times software distributions and services run as a 'system process' in Windows (i.e. SMS, Tivoli, etc.). This can create security problems with some installations/functions where the system account doesn't have the same permissions as the admin account. To test this, sometimes you really wish you could run a job interactively with system process permissions... here's a trick on how:
at 1500 cmd.exe /i
Yes, use the 'at' command to run a cmd.exe... it will execute with the system process permissions. Just pick a time 1 minute in the future and there you go.
