Changing Schedule Service Object Account Causes Problems

Last reviewed: May 12, 1997
Article ID: Q106152

The information in this article applies to:
  • Microsoft Windows NT operating system version 3.1
  • Microsoft Windows NT Advanced Server version 3.1

SYMPTOMS

When you change the default object account (system account) for the Schedule service to another account, you will experience problems when you run scheduled commands.

If you want to schedule commands that need to access network resources, such as back up a remote share, you need to change the Schedule service logon account from system account to a network access-permitted account. This is done using the Services option in Control Panel by defining the Startup settings. This is necessary because the system account has only guest privileges accessing remote shares.

After you start the Schedule service, and add a process to the service using the AT command, the command starts at the specified time, but doesn't perform any action and returns without errors.

WORKAROUND

Start the Scheduler Service with the default object account (System Account) and create the following batch file to be scheduled:

   REM Connect to server1\share1 using privileges of user1
   NET USE Z: \\SERVER1\SHARE1 /USER:DOMAIN1\USER1 PASSWORD

   REM Execute remote backup of device Z:
   NTBACKUP BACKUP Z:\ /D "MY BACKUP" /B /L C:\BACKUP.LOG

   REM Disconnect remote share
   NET USE Z: /D

   REM Continue the operation for any additional remote shares

This batch file first assigns drive Z to remote SHARE1 on SERVER1, and then backups the remote share via the NTBACKUP command. After the backup has been completed, drive Z is unassigned and reconnected to additional share(s). The NET USE command is executed with a special account which needs full access to all files installed remotely.


Additional query words: prodnt schedule fail fails
Version : 3.1
Platform : WINDOWS


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: May 12, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.