Date: 22 March 1996, 20:00:55 EST
From: Pete Tanenhaus, ADSM Client Development (pt AT vnet.ibm DOT com)
To:   ADSM-L at VM.MARIST.EDU
Subject: Drive invalid when running scheduler as an NT Service

Could the drive in question possibly be a remote drive ?

When the scheduler runs as a service and the System is the
user who logs on the service (which is the default) none of
your mapped drives will be available.

If this is the case there are two possible solutions:

   1. Changed the service to log on as a different user
      via the Services Control Panel.

      Make sure that the user has the desired drive automatically
      mapped at logon time.

   -- or --

   2. Modify the schedule to use the PRESCHED command to execute
      a batch file that maps the drive via the NET USE command
      prior to the schedule executing.

      Remember that when the system logs on no environment variables
      are available so you either have to point the fully qualified
      path of the batch file or place it in the System32 directory.

Hope this helps ...

Pete Tanenhaus
ADSM Client Development