Scheduled Tasks

[Guest]

This is a silly task, but I am trying to debug a problem with Antivirus
Update. I am trying to see if scheduled tasks works correctly. I used the
wizard to create a task to open up the calculator. When the time comes, it
simply states running. Should'nt the calculator program open up? I use an
administrative account, and I know the password is correct because when I use
an incorrect PW, it states that the task could not start.

 

[Pegasus \(MVP\)]

This is a silly task, but I am trying to debug a problem with Antivirus
Update. I am trying to see if scheduled tasks works correctly. I used the
wizard to create a task to open up the calculator. When the time comes, it
simply states running. Should'nt the calculator program open up? I use an
administrative account, and I know the password is correct because when I use
an incorrect PW, it states that the task could not start.

Scheduled tasks run invisibly in the background unless
you use the same account as your current foreground
session.

 

[Guest]

Check Task manager. It's probably running, you just can't see it

 

[Guest]

The Scheduled task is using an admin account which is the same as the
foreground.
The AT Service Account is using the system Account. Would the system account
have to be logged on the same account as the foreground?

 

[David H. Lipman]

From: "Greg" <[email protected]>

| This is a silly task, but I am trying to debug a problem with Antivirus
| Update. I am trying to see if scheduled tasks works correctly. I used the
| wizard to create a task to open up the calculator. When the time comes, it
| simply states running. Should'nt the calculator program open up? I use an
| administrative account, and I know the password is correct because when I use
| an incorrect PW, it states that the task could not start.

You might be using the correct credentials (account and password) but there may be another
reason why it won't start.

Instead of waiting for the event time to trip, just right click on the job and choose "Run".
If it doesn't launch, double-click on the job and edit it. Make sure all paths are valid.
Substitute any environmental variables with real fully qualified paths. Note that any time
you edit the job you will have to re-enter the account and password credentials.