*** Original Author:  ADSM-L @ UGA - ** Remote User **; 10/17/94 06:23

>Received: from uga.cc.uga.edu by AUDUCADM.DUC.AUBURN.EDU (IBM MVS SMTP V2R2.1)
>   with TCP; Mon, 17 Oct 94 05:58:06 CDT
>Received: from UGA.CC.UGA.EDU by uga.cc.uga.edu (IBM VM SMTP V2R2)
>   with BSMTP id 8459; Mon, 17 Oct 94 06:53:10 EDT
>Received: from UGA.CC.UGA.EDU (NJE origin LISTSERV@UGA) by UGA.CC.UGA.EDU (LMai
> V1.2a/1.8a) with BSMTP id 5735; Mon, 17 Oct 1994 06:53:10 -0400
>Date:         Mon, 17 Oct 1994 06:49:03 EDT
>Reply-To:     "Dist. Stor. Manager(ADSM) List"
> <ADSM-L%MARIST.BITNET AT uga.cc.uga DOT edu>
>Sender:       "Dist. Stor. Manager(ADSM) List"
> <ADSM-L%MARIST.BITNET AT uga.cc.uga DOT edu>
>From:         "Del Hoobler (852-1487)" <hoobler AT VNET.IBM DOT COM>
>Subject:      Updating password
>X-To:         adsm-l AT vm.marist DOT edu
>To:           Multiple recipients of list ADSM-L
> <ADSM-L%MARIST.BITNET AT uga.cc.uga DOT edu>
>
>> We seem to have gotten ourselves into a catch 22 during our
>> evaluation of ADSM.  I registered several folks to participate
>> in the test, but they were not able to actually start using the
>> product until after their password expired.  The Windows client
>> does have a utility function to change your password, but once
>> the password has expired, it does not appear to let you update
>> your password.  Short of deregistering all the Windows users, is
>> there any way to update an expired password (either by the
>> administrator or by the user)?  Thanks.

From an ADSM administrator client:

     update node <nodename> <password>

Del

*** Comments from STEWAJM - Stewart, Mike; 10/17/94 09:07am:
We found the earlier incarnations (pre 1.18, I think) of
the windows client wound not allow the user to change an expired
password.  The problem we saw was fixed by a later version
(maybe 1.18 (?)).