Keep in mind that persistent drive mappings happen at logon time, so the
account which the service (either ADSM, NT Schedule, or other)
logs on as must have the desired drives mapped or must have the authority to
NET USE them at startup.

Also, the local system account has no domain credentials and therefore will not
be able to map (NET USE) any domain resources without
a valid user name and password.

The easiest method of getting around this is to have the service log on as
domain authorized account (can be done via Services Control Panel)
which has the desired drives mapped.

Hope this helps .....

Pete Tanenhaus, ADSM NT Client Development
---------------------- Forwarded by Pete Tanenhaus/San Jose/IBM on 10/07/98
7/98
11:40 AM ---------------------------


ADSM-L AT VM.MARIST DOT EDU on 10/06/98 09:43:48 PM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: Foreign drives under NT 4.0 ? invalid drive spec??


How do you access those drives? I think the 'net use' command doesn't work
with schedules or 'at' commands. Maybe someone with those drives mapped has
to be logged in. I expect the unc support of client 3.1.0.5 may help with
backing up network shares.

Regards
Roger


Roger Hohmann

WestLB
Division: 009 Services
Abteilung: 001-80633
Herzogstra?e 15
D - 40217 Dusseldorf
Tel.: +49211 826 8155
mailto:roger_hohmann AT westlb DOT de