I also got a lot of resistance.. finally sold it to them after somebody
using the supervisor ID did something very damaging and they weren't able to
track them down because everybody needing supervisor equivalence was using
the supervisor ID.  This way, if something breaks and they can track it to
the ADSM backup ID, they know who did what.  This way, if the ADSM backup ID
breaks something, I'm accountable.

Tim

 ---------
From: owner-adsm-l
To: Multiple recipients of list ADSM-L
Subject: Re: Change of NetWare Supervisor password
Date: Tuesday, March 05, 1996 1:39PM

OK, fwiw #1 below works.  I got a lot of resistance to the adsm id
with supervisor preivledges idea.  That may take some work...

> 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 ?
>
> 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.

Thanks for the help,
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