Betsy,

 This is an unusual problem.  I had a similar experience that a scheduled
command would not recognize a drive but I could run a DSMC INC G: and it
would work.  I do not believe this has anything to do with the ID used to
install the product.  When a service runs, it uses a specific ID to run
under.  The default is the SYSTEM ID which has sufficient authorization.  I
would suggest that you try the following.

1) Make certain that F: and G: are local to the machine.  If they are not
local then you may have to take certain steps to get access to them prior
to backing them up.

2) Put domain all-local in the DSM.OPT and try a scheduled backup.  Does it
recognize F: and G:?

3) IF the drives are local and the ADSM scheduler fails to access them,
attempt an uninstall and re-install of ADSM.

If this still does not work, let us know.  The drives may have a problem.

Good luck,
  Dan T.

----------
> From: Moir,Elizabeth <Betsy.Moir AT ABBOTT DOT COM>
> From: Moir,Elizabeth <Betsy.Moir AT ABBOTT DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: NT Service and Logical Drives
> Date: Tuesday, October 21, 1997 10:30 AM
>
> To: OAS     --LMS1
>
> FROM: Betsy Moir (TTCEDM) Ext 85020
>       VM Tech Services
>       email:  betsy.moir AT abbott DOT com
> Subject: NT Service and Logical Drives
>
> I have a client with a problem that my lack of NT server experience can't
> help them with.
>
> They installed ADSM on their NT server as userid ADSMTEST.  ADSMTEST was
a
> member of the administrator group and the Backup group.  The options file
> contains the command DOMAIN D: F: G:  When the scheduler runs it
recognizes
> drive D: and backs it up, but returns the error ANS4147E Drive F: is an
> invalid drive specification.  The same for G:
>
> The questions are:
>
> 1.  How do we get the ADSM scheduled service to recognize these logical
>     drives?
>
> 2.  When the product is installed under a user account, does it retain
the
> rights of that account even if the account isn't logged on to the server
at
> the time of scheduler runs?
>
> 3.  Is it possible to get ADSM to recognize the F: and G: drives without
> having to grant ADSMTEST access at the directory level.
>
> If anyone has any experience with this or can help out with a solution it
> would be greatly appreciated.  Thanks.
>
> Betsy