Try using the following:
dsmcutil updatepw /validate:yes /node:clientname
/password:clientpassword
then stop and restart the scheduler.

We are running ADSM version 2.x. We had some security issues last week
so
we changed administrative password for all our servers.We also changed
them
at the node level on the server. The Novell and Unix ones worked fine as
far as kicking off the nightly backups. We changed the password on the
nodes on the ADSM server, then we went to the client and changed them.

We have 3 NT machines that will not run at night as scheduled. I tried
the
command line dsmc incremental to kick them off manually and it asked me
to
type in the password. I did and thought then the next night they would
kick
off OK but they didn't. The next day I went to the command prompt on
these
machines and used the updatepw.exe option and it said storing the
password
in the registry. I thought then this morning I would come in and they
would
have run last night. No such luck. Of course I am backing them up
manually
using the GUI interface at the node level until we get this resolved.

Any help would be appreciated.

Janie Pendergraft
St. John's Regional Medical Center