220-1102 Question 86
Single answerTask Scheduler (taskschd.msc)A small business uses a Windows 10 PC in the accounting office to run a nightly cleanup script at 11:00 PM. The script is configured in Task Scheduler and runs correctly when the accountant is logged in, but it does not run if no one is signed in at that time. You need to make sure the task runs every night whether or not a user is logged on. Which action should you take in Task Scheduler?
- A
Edit the task and select "Run whether user is logged on or not," then provide the account password if prompted
- B
Edit the task and check "Run with highest privileges" so the task can start without a user session
- C
Change the trigger from a daily schedule to "At log on" so the task starts in the background
- D
Move the script into the user's Startup folder so Windows launches it automatically at night
Show answer and explanation
Correct answer: A
Explanation
The key issue is that the task currently depends on an interactive user session. In Task Scheduler, the proper fix is to configure the task to run whether or not the user is logged on. This is done on the task's General tab. If the task uses a user account, Windows typically requires that account's password so it can run the task in the background. The "Run with highest privileges" setting is only for elevation and does not replace the need to allow unattended execution. Microsoft's Task Scheduler guidance distinguishes between trigger conditions, security context, and privilege level, so technicians should verify all three when troubleshooting jobs that fail outside a signed-in session.
- A. Correct.
Correct. In Task Scheduler, a task that must run even when no user is interactively signed in should be configured to "Run whether user is logged on or not." Windows may prompt for the account credentials so it can store the necessary information to launch the task in a non-interactive session. This is the standard configuration for scheduled tasks that must run unattended.
- B. Incorrect.
Incorrect. "Run with highest privileges" allows the task to run elevated, similar to administrative rights, but it does not by itself allow the task to run when no user is logged in. A common misconception is that elevation and unattended execution are the same thing; they are separate settings.
- C. Incorrect.
Incorrect. Changing the trigger to "At log on" would only run the task when a user signs in, which does not solve the requirement for the task to run at 11:00 PM if no one is logged in. This option confuses trigger timing with logon state behavior.
- D. Incorrect.
Incorrect. The Startup folder only launches programs when that specific user signs in. It cannot start a script at a scheduled nighttime interval without a logon event. This is a common consumer-level workaround, but it is not appropriate for a managed scheduled task requirement.