Anything spawned by "at" runs as the system account. It's sorta like
"runas" but you run as the system instead of a regular user account. I'd be
willing to bet that that's not the same as the account you logged on as.
There are only 2 caveats: 1) you'll probably have to be a local admin to use
"at" and 2) anything that Explorer (and several other less-common apps) does
on the desktop will happen in the context of the logged-on user unless you
kill Explorer (or whatever other single-instance app) first.
Try it out. You can even start a cmd console with at, then launch your app
from there.
--
Drew Cooper [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Pascal Yokogawa" <(E-Mail Removed)> wrote in message
news:096c01c3d5b8$0e70fb50$(E-Mail Removed)...
> We have to run the application under an other user than
> the user logged in, which is not possible (at least in our
> eyes) with the "at" command...
>
> >-----Original Message-----
> >Not sure how you can do this with the Task Scheduler UI,
> but the cmdline
> >tool "at" will let you run an app as the local machine
> that can interact
> >with the desktop - see "at /interactive".
> >--
> >Drew Cooper [MSFT]
> >This posting is provided "AS IS" with no warranties, and
> confers no rights.
> >
> >
> >"Pascal Yokogawa" <(E-Mail Removed)>
> wrote in message
> >news:0bd601c3d534$686d11e0$(E-Mail Removed)...
> >> Hi,
> >>
> >> We currently face the following problem:
> >>
> >> We run an Excel application with a custom made addin.
> This
> >> application is run by a scheduled task (windows XP)
> under
> >> a different username (same machine). Both useraccounts
> are
> >> Administrators, no events in the Event Viewer show up.
> >>
> >> Our application works correctly under both usernames
> (the
> >> username we logged in with, and the username the task
> runs
> >> on), but after some research we found out that with a
> >> scheduled task under a different username Excel asks for
> >> userinteraction. As the task runs invisible, we cannot
> see
> >> what exactly is asked.
> >>
> >> Microsoft Spy++ does not reveal any windows, so
> debugging
> >> is not possible at the moment.
> >>
> >> Our question:
> >> Is there a possible way to find out what the messagebox
> >> should show? All help is welcome.
> >>
> >> PS Userinteraction is required BEFORE running our custom
> >> addin, so debug logging from within the addin is not
> >> helpful.
> >>
> >> Regards,
> >>
> >> Pascal Yokogawa
> >
> >
> >.
> >
|
Similar Threads
