You've found a bug in the utility.

The OPTFILE option is somewhat confusing in that is serves two purposes.

One is to specify what options file the scheduler service will use to logon to
the ADSM server.

The other is to specify what options file the utility will use to start an API
session with the ADSM server to validate passwords.

 In the problem you describe, the utility is  trying to locate the specified
option file on the local machine to start the
API session to validate the password.

Note that the location specified is valid for the service itself because it is
relative to the remote machine.

So in your example, the utility is attempting to start an api session from an
options file located in  d:\adsm_v\baclient\dsm.opt
on the local machine when it should be using the remote machine location   \\
DRN2302\d$\adsm_v\baclient\dsm.opt.

Since the option file doesn't exist in this location on the local machine the
password validation fails and the registry password
isn't generated on the remote machine.

The service itself will correctly use  d:\adsm_v\baclient\dsm.opt, but it won't
run because the password wasn't generated.

Thanks for finding this and I'll make sure that  it gets fixed in the next ptf.

I will also be adding several new commands for starting and stopping the
service as well as new options for specifying domain accounts
and passwords the service uses to logon.

Anyway, there are several methods of getting around your current problem.

One would be to simply specify /VALIDATE:NO when installing the service as
follows:

dsmcutil install /name:"ADSM Central Scheduler Service"
/clientdir:"d:\adsm_v\baclient" /node:DRN2302 /machine:DRN2302
/password:client /autostart:yes /optfile:"d:\adsm_v\baclient\dsm.opt"
/validate:no


This will bypass the password validation check and will allow the password to
be generated into the registry.

If required, the password could then be validated with the UPDATEPW command as
follows:

   dsmcutil updatepw /mach:DRN2302 /node:DRN2302 /password:client
/commmethod:tcpip /commserver:server.whatever.com
                                        /commport:1500

Note that COMMMETHOD, COMMSERVER, and COMMPORT options are only required if you
need to point a server other than the
one specified the local options file.

Hope this helps and thanks again for finding this.


Pete Tanenhaus, ADSM NT Client Development

---------------------- Forwarded by Pete Tanenhaus/San Jose/IBM on 08/26/98
6/98
10:27 AM ---------------------------


ADSM-L AT VM.MARIST DOT EDU on 08/26/98 07:17:00 AM
Please respond to dthorneycroft AT lacsd DOT org
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: Remote installation of NT scheduler service


Phil: I haven't had any problems using the remote install. The only
difference
I see Between my procedure and yours is that I don't enclose the path to
my optfile or clientdir in quotes.


Phil Chissell wrote:
>
> Has anybody successfully installed a scheduler service on a remote NT
> node via the dsmcutil command?
>
> e.g. To install a scheduler service on node DRN2302 from node FRED.  On
> FRED, I issue the following command:
>
> dsmcutil install /name:"ADSM Central Scheduler Service"
> /clientdir:"d:\adsm_v\baclient" /node:DRN2302 /machine:DRN2302
> /password:client /autostart:yes /optfile:"d:\adsm_v\baclient\dsm.opt"
>
> this returns:-
>
> ************************
>
> ADSM Windows NT Scheduler Service Configuration Utility
> Command Line Interface Version 1.00.e
> Last Updated Jul 24 1998
>
> Command: Install and Configure ADSM Scheduler Service
> Machine: DRN2302
>
> Connecting to registry on remote machine DRN2302 ...
>
> Installing ADSM Client Service:
>
>        Machine          : DRN2302
>        Service Name     : ADSM Central Scheduler Service
>        Client Directory : d:\adsm_v3\baclient
>        Automatic Start  : Yes
>
> The service was successfully installed.
>
> Creating Registry Keys ...
>
> Updated registry value 'ImagePath' .
> Updated registry value 'EventMessageFile' .
> Updated registry value 'TypesSupported' .
> Updated registry value 'OptionsFile' .
> Updated registry value 'EventLogging' .
> Updated registry value 'ClientNodeName' .
> Updated registry value 'ADSMClientKey' .
>
> Generating registry password ...
> Authenticating password with ADSM for node DRN2302 ....
>
> Connecting to ADSM Server via client options file
> 'd:\adsm_v3\baclient\dsm.opt'...
>
> Unable to locate/open the specified options file .
>
> Password Authentication failed.
>
> The Registry password wasn't updated.
>
> ********************
>
> The service is installed but it doesn't work as it cannot find the
> options file.
>
> I have successfully deleted remote scheduler services and can install
> them OK locally.
>
> Can anybody help?
>
> Cheers
>
> Phil
>
> Phil Chissell
> National Power plc
> Windmill Hill Business Park
> Whitehill Way
> Swindon
> Wilts. SN5 6PB
> UK
>
> Tel:  +44 (0)1793 894237
> Fax: +44 (0)1793 894230
> MailTo:Phil.Chissell AT natpower DOT com