How to Move a Scheduled Job to Another NT Server

Last reviewed: March 9, 1998
Article ID: Q178555
The information in this article applies to:
  • Microsoft Windows NT Server version 4.0

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information on how to do this, view the "Restoring the Registry" online Help topic in Regedit.exe or the "Restoring a Registry Key" online Help topic in Regedt32.exe.

SUMMARY

This article describes how a Windows NT Administrator can move scheduled jobs from one Windows NT 4.0 server to another. For example, a server with several different batch jobs scheduled to run at various times throughout the week needs to be taken offline, so the jobs need to be moved to another server.

NOTE: The purpose of this article is to instruct you how to move the schedule from one server to another. All batch files, applications, or services called upon by these scheduled jobs still have to be installed locally on the computer you are moving the scheduled jobs to.

MORE INFORMATION

Follow the steps below to move all scheduled jobs from Server1 to Server2:

Server1

  1. Click Start, point to Settings, click Control Panel, and then double-click Services.

  2. Stop the Schedule service.

    WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

    For information about how to edit the registry, view the "Changing Keys And Values" online Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" online Help topics in Regedt32.exe. Note that you should back up the registry before you edit it.

  3. Run Registry Editor (Regedt32.exe) and go to the following subkey:

          HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Schedule
    

  4. On the Registry menu, click Save Key.

  5. Navigate to a network share accessible by both servers, then name the file Schedule.reg.

Server2

  1. Click Start, point to Settings, click Control Panel, and then NOTE: double-click Services.

  2. Stop the Schedule service, if it is running.

  3. Run Registry Editor (Regedt32.exe) and go to the following subkey:

          HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Schedule
    

  4. On the Registry menu, click Restore, select the saved file on the network share mentioned in Step 5 under Server1, and then click Open.

    You will be prompted with a warning that Registry Editor will restore a key on top of the currently selected Key. If there were jobs previously scheduled on Server 2, they will be replaced.

    Click OK to continue.

  5. Close Registry Editor.

  6. Click Start, point to Setting, click Control Panel, and then double-click Services.

  7. Start the Schedule service.

The entire job schedule is now transferred to the new server without having to manually recreate them using the AT command or WinAT.


Additional query words: winat.exe scheduler
Keywords : nt32ap nthowto NTSrv ntutil kbtool
Version : WinNT:4.0
Platform : winnt
Hardware : ALPHA PPC x86
Issue type : kbhowto


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 9, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.