Scheduled Tasks Run in the Context of Session 0 with Terminal Services

This article was previously published under Q255544
This article has been archived. It is offered "as is" and will no longer be updated.
Windows 2000 includes a Scheduled Tasks tool that you can use to configure many tasks, including scripts, documents, and programs. Although you can configure these tasks remotely by using a Terminal Services session, you cannot interact with the task through a Terminal Services session when it runs.
All scheduled tasks run in the context of session 0 (the console). For example, if you schedule Calculator to start every day at 11:00 A.M., Calculator starts every day at 11:00 A.M. on the console, even if you configured the task through a Terminal Services session.

Article ID: 255544 - Last Review: 10/20/2013 17:45:30 - Revision: 2.2

Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Datacenter Server

  • kbnosurvey kbarchive kbinfo KB255544
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)