We have actually two different situations when the NT client doesn't backup
drives in case of having the scheduler started as a NT service.
One is with remote drives and Pete's recommendations will indeed fix the
problem. The second situation is more serious, because it's a hidden problem.
The drives are local drives. They are not recognized to be backed up and no
error message indicate the problem. The schedule event also finishes with
success.
When I specify these drives using the DOMAIN option, the 'Drive invalid' message
appears. The only difference is that these drives don't have a primary
partition. During the boot process, NT checks in the 'blue screen' environment
with NTDETECT its hardware configuration and we see these drives being correctly
recognized as valid drives already in this initial phase.

/----------------------------------------------------------------\
| Hans Beierle                      Internet: hbeier AT eds DOT de      |
| EDS (Deutschland) GmbH            Voice: ++49 6142 803170      |
| Eisenstr. 56 (N15)                FAX:   ++49 6142 803030      |
| D-65428 Ruesslsheim                                            |
\----------------------------------------------------------------/

An: * ADSM-L @ DIAMOND
Kopie:
Von:  owner-adsm-l[INET.OWNERADS] @ DIAMOND @ EDS HUB @ EDSHUBEUROPE
Datum: 23.03.96 02:12:26
Thema: NOTE 03/22/96 20:12:26

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