I have a few "on demand" scheduled tasks. And I use alternative desktops supplied by SysInternals\Desktops. Whenever I run one of those tasks, either from the Scheduled Tasks MMC applet or with "schtasks.exe /run /tn ...", it runs on the default desktop, regardless of which is the current I/O desktop. Is there any way around this or a more appropriate forum in which to ask? I have also posted this query in the Win 7 UI forum. Thanks. - Vince

1. I would address Sysinternals forum. 2. Configure creation of log files and analyze them as well as "history" 3. Hope you set up your tasks with elevated rights. Regards Milos

1. I would address Sysinternals forum. 2. Configure creation of log files and analyze them as well as "history" 3. Hope you set up your tasks with elevated rights. Regards Milos I have other ways of creating alternate desktops and it happens with those also. Elevated rights ... yes. What logs; what history? Taskhost.exe and taskeng.exe run as the logged-on user and are, no doubt, attached to the "Default" desktop. Neither makes an attempt to determine the I/O desktop (with, for example, OpenInputDesktop()). Without determining the I/O desktop, I don't suppose it's possible to create a process on any desktop but the default one. I can't imagine a work-around for that but I'm hoping for one. - Vince

1. I would address Sysinternals forum. 2. Configure creation of log files and analyze them as well as "history" 3. Hope you set up your tasks with elevated rights. Regards Milos I have other ways of creating alternate desktops and it happens with those also. Elevated rights ... yes. What logs; what history? Taskhost.exe and taskeng.exe run as the logged-on user and are, no doubt, attached to the "Default" desktop. Neither makes an attempt to determine the I/O desktop (with, for example, OpenInputDesktop()). Without determining the I/O desktop, I don't suppose it's possible to create a process on any desktop but the default one. I can't imagine a work-around for that but I'm hoping for one. - Vince The task history, once enabled, showed nothing out of the ordinary. And, in fact, the work-around was simple ... configure the task to run a shim-app which **does** OpenInputDesktop() and then runs (CreateProcess()) the real target (specified in its args) on that desktop. I'm still wondering ... Is this merely an omission of functionality on the part of TASKHOST/TASKENG?

Hi, You can post your concern in Sysinternals Forums. http://forum.sysinternals.com/Kim Zhou TechNet Community Support

Hi, You can post your concern in Sysinternals Forums. http://forum.sysinternals.com/ Kim Zhou TechNet Community Support There has been no discussion in the SysInternals fotum. It is no surprise; the problem has nothing to do with SysInternals. There are other ways to create and switch to other desktops. On-demand tasks (schtasks /run /tn...) are, quite simply, run on the "Default" desktop regardless of which is the input/output desktop. ... by design, or an oversight?