Schedule task and screen verbose

[Guest]

I had got a couple of schedule task on batch files created in local
administrator.
These batch files call out to exe or excel program and show the actual
running process.
However I notice that these screen process are not shown while other user
accounts are loggin.
Is there a way to show the screen process within other account logins?

 

[Pegasus \(MVP\)]

I had got a couple of schedule task on batch files created in local
administrator.
These batch files call out to exe or excel program and show the actual
running process.
However I notice that these screen process are not shown while other user
accounts are loggin.
Is there a way to show the screen process within other account logins?

It is in the nature of scheduled tasks that they run in the background.
They are not meant to be interactive. They become only visible if they
are scheduled to run under the same account as the foreground
logon account.

 

[Guest]

Thanks,

I am trying to troubleshoot a schedule task but in vain.
A python script was runned from a batch file. It will look for a ODBC
connection and get the relevant data.

Apparently it could not contact the ODBC connection using the schedule task.
However by running it directly using the batch file it run fine.

Everything was run in restricted user profile.
Task is created in local admin account.

Puzzling me

 

[Pegasus \(MVP\)]

Assumming that the task is scheduled to run under
the Windows account xxx, you must log on yourself
as xxx so that you can see what's going on.

What's the batch file you run? Have you tried running
the scheduled task under an administrator's account?

 

[Guest]

Task is created and scheduled in local administrator account.
Was able to run without any problems in local admin account.

I assigned the Read/Execute/Write permission of the task to the batch file
owner.
Owner using his domain account login, runs the task but the script in the
batch file was not able to communicate with ODBC connection.

However owner still in his login, double click and run the batch file
through windows explorer and the script was able to run without any problems.

Task details:
Batch file runs a python script to extract some data through an ODBC
connection in the network.

 

[Pegasus \(MVP\)]

Maybe it's getting too late where I am (11:15 pm) but I am
unable to wrap my mind around your reply. Here is what
I gather:
a) Task scheduled under a local administrator: Runs OK.
b) Batch file invoked under the user's domain account: Runs OK.
c) Task triggered by the user while logged on under his domain account:
Fails.

I can't see any difference between a) and c), because in each
case the task runs under the preset local admin account.

Furthermore I do not understand why you don't let the task
run under the user's domain account, since this works fine.

Perhaps the fog will lift from my brain overnight.

 

[Guest]

You still has quite a clear mind
a, b and c are correct and it is puzzling me why the batch file is unable to
run under scheduler in user account.

We are controlling the access of schedule tasks.
Only admins were able to create and delete tasks.
users (developers) were only able to read,execute and write from schedule
tasks.