ranadhir
07-14-2008, 03:43 AM
We are trying to get an interactive command prompt,running with 'SYSTEM' user credentials
The sequence of steps are as follows:
1) Get the local time (through the TIME shell command, for example)
2) Add one minute to this time
3) Run the AT command with this new time.
4) Wait one minute for the command window to appear.
An example set is as below:
E:\Documents and Settings\Adi>time
The current time is: *16:29*:00.96
Enter the new time:
E:\Documents and Settings\Adi>at *16:30* /interactive cmd.exe
Added a new job with job ID = 1
We do get a command prompt with 'SYSTEM' privileges.
Next,we attempt to do this on a remote w2003 host through REMOTE login.
In this case,though we find the cmd.exe running in the task manager,but we DO NOT see the command prompt in the foreground.
What service/security setting prevents the command prompt to interact with the desktop in this case?
We also confirmed that in certain other environments ,we DO see the command prompt on the foreground successfully ,even via remote login.
Unfortunately,we have not been able to work out the security 'tweak',which obstructs our first environment from doing so.
Any help will be much appreciated.
The sequence of steps are as follows:
1) Get the local time (through the TIME shell command, for example)
2) Add one minute to this time
3) Run the AT command with this new time.
4) Wait one minute for the command window to appear.
An example set is as below:
E:\Documents and Settings\Adi>time
The current time is: *16:29*:00.96
Enter the new time:
E:\Documents and Settings\Adi>at *16:30* /interactive cmd.exe
Added a new job with job ID = 1
We do get a command prompt with 'SYSTEM' privileges.
Next,we attempt to do this on a remote w2003 host through REMOTE login.
In this case,though we find the cmd.exe running in the task manager,but we DO NOT see the command prompt in the foreground.
What service/security setting prevents the command prompt to interact with the desktop in this case?
We also confirmed that in certain other environments ,we DO see the command prompt on the foreground successfully ,even via remote login.
Unfortunately,we have not been able to work out the security 'tweak',which obstructs our first environment from doing so.
Any help will be much appreciated.