The third suggestion was to launch CMD.exe via a Scheduled Task. In this case the service fails to start and results it the following error message: FAILED 1053: The service did not respond to the start or control request in a timely fashion. C:\sc create RunCMDAsLSA binpath= "cmd" type=own type=interact I found information online which suggests lauching the CMD.exe using the DOS Task Scheduler AT command, but I received a Vista warning that "due to security enhancements, this task will run at the time excepted but not interactively." Here's a sample command: AT 12:00 /interactive cmd.exeĪnother solution suggested creating a secondary Windows Service via the Service Control (sc.exe) which merely launches CMD.exe. Basically, I would like to run CMD.EXE under the Local System Account. Since the Windows Service is running under the Local System Account, I would like to emulate this same behavior. I'm currently running Vista and I would like to manually complete the same operations as my Windows Service.
0 Comments
Leave a Reply. |