One of our users is running version 3-1-0.6 of the ADSM backup client on
his Windows NT 4 (SP3) machine using the ADSM Central Scheduer.

While the ADSM is working fine in backing up local drives, he also wants
the Win NT client to backup a drive on his 2nd machine (a Windows 95)
which he has mapped to his NT machine. A reading of the ADSM documentation
suggests that his remote machine would have to be (1) running Windows NT,
(2) be a member of the same Windows NT LAN domain as his ADSM client
machine, and (3) he use a domain userid auithorized to access the remote
drive.

If this is true, can anybody suggests a workaround?  For example, could I
set up a preschedulecmd which would map the remote drive, and then include
the mapped letter in his domain command?


thanks,

Mark Keintz                            University of Pennsylvania / 6298
Computer Core Director                 Population Studies Center
mark_keintz AT pop.upenn DOT edu              3718 Locust Walk
phone: 215/898-6713   fax: 898-2124    Philadelphia, PA 19104-6298