Couple of thoughts....

1) Never tried this but, if the userid/password are the same on all the
servers, is it possible to set the new password on one server then copy the
encrypted *.PWD file to the other 25 servers ?

2) You could hardcode the userid/password in the DSM.OPT file using the
 -nwuser option.

3) Set up a unique ADSM id with the appropriate access (i..e. supervisor
equivalent in Netware 3.1x). This id could either have a nonexpiring
password or would allow you to control when the password gets changed.  I
finally convinced our Netware folks to do this and it has made my life
easier.

Tim Pittson
pittson1 AT bwmail1.hcc DOT com
 ----------
From: owner-adsm-l
To: Multiple recipients of list ADSM-L
Subject: Change of NetWare Supervisor password
Date: Tuesday, March 05, 1996 10:42AM

Due to a change in staffing we have had to change our generic NetWare
supervisor password which was being used, among other things, to run
our adsm backup and restore processes.  We have 26 servers in hours
and would really rather not console into each of them to perform a
backup or restore just to set the new password.  Does anyone know of a
quick and (somewhat)clean way to handle this with this many file
servers?

Regards,
Chuck
 ---
Chuck Mattern           "That which does not kill us, makes us stronger.."
Sr. Systems Engineer    -Friedrich Nietzsche-
cmattern AT homedepot DOT com
2455 Paces Ferry Rd.
Atlanta, GA 30339-4024
770-433-8211 ext 84446