Consider the following scenario:

• You create a scheduled task on a Windows Server 2008-based or Windows Vista-based computer.
• This task is configured for Windows Server 2003, Windows XP, or Windows 2000.
• One or more triggers are configured for this task.
• On the Conditions tab, you select the Stop if the computer ceases to be idle option.

In this scenario, the Stop if the computer ceases to be idle option is not saved after the task is created. Therefore, this scheduled task does not stop after the system returns from an idle state.

Notes:

• This issue does not occur if this task is configured for Windows Vista or Windows Server 2008.
• This issue does not occur if no trigger is configured for this task even if the task is configured for Windows Server 2003, Windows XP, and Windows 2000.

Consider the following scenario. When you run Windows Vista in audit mode, you try to end a process by using the Taskkill.exe program. However, the Taskkill.exe program stops responding. If you try to end the unresponsive Taskkill.exe process by using another instance of Taskkill.exe, the second instance also stops responding.

Consider the following scenario:

• You are running Windows Vista or Windows Server 2008 on a computer.
• You create a scheduled task to run at a given time.
• You configure the scheduled task to wake the computer to run.
• You put the computer in hibernation (S4).

In this scenario, the computer comes out of hibernation at the expected time. However, the scheduled task may not run as expected.

Consider the following scenario:

• You have a computer that is running Windows Vista or Windows Server 2008 in a domain.
• You configure a scheduled task on the computer.
• You try to change the running user context from the default user account to another account in the domain.

In this scenario, you receive the following error message:

An error has occurred for task TaskName. Error message: The specified account name is not valid
This problem occurs if the NetBIOS domain name is not the default name.

Note: By default, a NetBIOS name is the leftmost part of the DNS domain name. For example, if the DNS name is “contoso.com,” the NetBIOS domain name is “CONTOSO.” However, an administrator may arbitrarily choose any valid NetBIOS name.

Consider the following scenario:

• You create a scheduled task on a computer that is running Windows Server 2008 or Windows Vista Service Pack 1 (SP1).
• One or more command-line arguments in this scheduled task are enclosed in quotation marks.

In this scenario, the scheduled task does not run as expected. Additionally, a value of 0×1 appears in the Last Run Result column.

For example, assume that you create a scheduled task by running the following command-line argument:

schtasks /create /tn "Test Scheduled Task" /tr "c:\temp.bat \"1-Jan-70 8:00:00\"" /sc daily /st 03:15:00 /ru System

The scheduled task fails after it starts at 03:15. However, if you delete the quotation marks around “1-Jan-70 8:00:00,” the scheduled task runs successfully.

Note: The issue does not occur in Windows Vista or in Windows Server 2003.

After you configure a scheduled task in Windows Vista, the Task Scheduler does not wake Windows Vista from sleep to run the scheduled task as expected. You experience this issue if you use the Create Basic Task Wizard to create the scheduled task.

Note: The following information in Windows Vista Help indicates that this functionality is supported:
You can also set a condition that tells the task to wake the computer from sleep mode to run the task when the trigger is activated.

Consider the following scenario. On a Windows Vista-based computer, you create a task in Task Scheduler. Then, you enable the Run task as soon as possible after a scheduled start is missed setting for the task. If the computer was turned off when the task was scheduled to run, the task will run as expected when you restart Windows Vista. However, if the computer was in sleep mode when the task was scheduled to run, the task does not run at the scheduled time. Additionally, the task does not run as expected when you wake the computer.