Despite the “Hidden” box being checked in the Scheduled Task properties, tasks which would natively produce a interface box (regardless of whether user input is required) – such as a batch script – can still appear as a window on your desktop. For tasks where no user input is required, this can be quite annoying, but thankfully there is an easy fix for this.

geektechsupport
—
2013-05-06T17:36:22Z —
#2

What happens when the user has to change their password? Will they need to go in to the scheduled task and update it there as well?

faulkner132
—
2013-05-06T17:43:01Z —
#3

The user would need to update their password in the task settings or it would fail.

iluv9mm
—
2013-05-07T14:01:45Z —
#4

Our IT department had a service account set up for each user, as well as their normal account. Tasks like that ran under the service account.

The network guys' automatic configuration tools reached out every month and assigned each person's service account a new password, then scanned through all the scheduled tasks using that account and updated those passwords too. They would not tell the users what ther passwords were, though.

it always missed something, like developers IIS startup services, which they also have locked down. So for a week after each password change, the network guys would be hopping around to all us developers trying to get our development environments working again. Fun fun fun...

markw676
—
2013-05-08T22:06:58Z —
#5

Isn't there a trick to put start as the first command in like a batch file to hide the command prompt?

faulkner132
—
2013-05-15T15:45:33Z —
#6

You could do something like that, however the command window would still pop up for a split second when the START command runs.