Task scheduler & Hidden User Accounts

  • Thread starter Thread starter Jon
  • Start date Start date
J

Jon

Hi all,

It maybe my lack of understanding here but can somebody help me out?

I'm trying to run a scheduled task on a daily basis using a hidden
user account. Creating the task is not a problem for example: running
Adobe Acrobat reader, I provide the task schedule details and provide
the hidden user account which by the way is an Administrator account,
also it has a password and it has been added to the security settings
for the task.

When testing I notice the the task has started but then nothing, no
error, no Adobe! NOTHING!

Could anybody help me shed some light on this? I can find nothing that
suggests a hidden account is not capable of performing task scheduling
but very little else. I may have configured something incorrectly here

Regards
 
Jon said:
Hi all,

It maybe my lack of understanding here but can somebody help me out?

I'm trying to run a scheduled task on a daily basis using a hidden
user account. Creating the task is not a problem for example: running
Adobe Acrobat reader, I provide the task schedule details and provide
the hidden user account which by the way is an Administrator account,
also it has a password and it has been added to the security settings
for the task.

When testing I notice the the task has started but then nothing, no
error, no Adobe! NOTHING!

Could anybody help me shed some light on this? I can find nothing that
suggests a hidden account is not capable of performing task scheduling
but very little else. I may have configured something incorrectly here

Regards
Click to expand...

This is by design. When you run a scheduled task under an account other than
the foreground account then this task will run in the background and will be
invisible to you. If it ran in the foreground then this would create a huge
security hole: The task uses the privileges assigned to the account under
which it runs, which the lowly foreground session may exploit for its own
purposes!
 
This is by design. When you run a scheduled task under an account other than
the foreground account then this task will run in the background and will be
invisible to you. If it ran in the foreground then this would create a huge
security hole: The task uses the privileges assigned to the account under
which it runs, which the lowly foreground session may exploit for its own
purposes!- Hide quoted text -

- Show quoted text -
Click to expand...

Many thanks, this makes a lot of sense. is there any way to bring the
task to the foreground other than use current foreground account?

Kind regards & thanks for you speedy response
 
Jon said:
Many thanks, this makes a lot of sense. is there any way to bring the
task to the foreground other than use current foreground account?

Kind regards & thanks for you speedy response
Click to expand...

AFAIK, no. It sort of defeats the purpose, don't you think? If it's just
to satisfy yourself that it's working, have it do some other short task
and schedule it for a few minutes from now and when that time is past,
go check to see if it ran.

HTH,

Twayne
 
Back
Top