Knowledge Base

Task Scheduler Task Does Not Run When Copied to Another Computer

Article ID: 187853

Article Last Modified on 1/23/2007

APPLIES TO

This article was previously published under Q187853

SYMPTOMS

When you copy a Task Scheduler task (.job) file from one Windows NT-based computer to another Windows NT-based computer, the copied task may not run.

CAUSE

This behavior can occur because the access credentials for the task are not copied with the .job file.

RESOLUTION

To resolve this behavior, change the credentials for the copied .job file. To do so, follow these steps:
  1. Double-click My Computer, and then double-click Scheduled Tasks.
  2. Double-click the copied task.
  3. In the Run As box, type the user account that has the credentials required to run the task, and click OK.
  4. Type the password for the user account, and then click OK.
  5. Click OK, and then close the Scheduled Tasks window.

MORE INFORMATION

The Local Security Administration Subsystem (Lsass.exe) is the process that runs the Local Security Authority (LSA) component of the Windows NT Security subsystem. The Lsass.exe process manages security administration on the local computer. The Security Reference Monitor enforces the access validation and audit generation policy defined by the LSA. It provides services to both kernel and user modes to ensure that users and processes attempting to access an object have the correct credentials.

For additional information about how to use Task Scheduler, please see the following article in the Microsoft Knowledge Base:

178706 How to Schedule a Program Using Task Scheduler

Keywords: kbprb KB187853


Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.