Is this accomplished on the client or server side?  Our documentation
states that ADSM cannot be run as a service!

Thanks for the clarification!

Bonnie






Trevor.Foley AT BANKERSTRUST.COM DOT AU on 10/08/97 06:29:14 PM

Please respond to ADSM-L AT VM.MARIST DOT EDU

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Bonnie Goins/Headquarters/USX)
Subject:  Re: NT client




Trevor Foley@BT_AUSTRALIA
09/10/97 08:29 AM

Hi Sharon,

Unless I am missing something, you don't have ADSM running as a service.
Having it autostart at login is quite different to having something run as
a service.

To get ADSM running as a service, you need to run the DSMCSVCI.EXE utility
which is located in your ADSM BACLIENT directory. This will install the
ADSM scheduler as a service so it will continue to run even if someone logs
out.


regards,

Trevor

> I have an NT 3.1 client that runs adsm as a service.  I have it auto
starting when the machine is logged in as
> administrator. However, all too often, the machine gets logged out and
back in as some other user. Of course adsm
> does not work at this point.  Our NT administrator wants to know:
> If the remote devices could be backed up by UNC name as opposed to
mapping them to the machine.
> My next option is to try logging into the machine as ADSM, mapping the
drives to that user then logoff the console
> and see if the backups work correctly
> Does anyone else have this problem or any insight? I look forward to
hearing from you.