Elizabeth,
machine names different to the ADSM nodename don't make any problems.
Just get sure that these names don't get too long. I remember one case a
few months ago where a longer nodename including a mailing path (like
machine.organisation.com) made ADSM crash.
Another idea is the optfile: Did you put the baclient and adminclient
into one directory? Two different optfiles? Do both clients work
properly without the scheduler service?
If you had an older version of the scheduler active, did you stop the
service and uninstall the service? You can't uninstall older PTF's
service installations using the PTF6 tool. Use instsrv (resourcekit) to
remove the old service before installing a new one.

Good luck!

Regards,
Michael
--
Michael H. Bartl
Michael H. Bartl
ADAC e.V. (Rechenzentrum, Produktionsplanung und Organisation)
Tel.: (089) 7676-4063, Fax: (089) 7676-8161
EMail: Michael.Bartl AT Zentrale.ADAC DOT de

>----------
>Von:   Moir,Elizabeth[SMTP:Elizabeth.Moir AT LN.SSW.ABBOTT DOT COM]
>Gesendet:      Dienstag, 11. November 1997 15:16
>An:    ADSM-L AT VM.MARIST DOT EDU
>Betreff:       ADSM and the NT Service
>
>Hello ADSMers who are also NT gurus - and others as well.
>
>I'm having a problem installing the ADSM Scheduler as an NT service on two of
>my NT clients using ADSM V2.  Everything seems to go along fine until it gets
>to the point of validating the node password.  At that point everything just
>hangs, we get a "Quincy" error message that can't be removed with the delete
>button and no service is installed.
>
>I have installed the service on my own machine without any problems and I'm
>lost as to what the next step would be.  One thing I've noticed that might
>make a difference - my machine's name is the same as my ADSM nodename; their
>machine names are different.
>
>Does anybody have any suggestions.  Thanks in advance.
>