Thanks.  I my way back from getting asprin to help relieve the pain of
playing softball I remembered there was an option to prevent the client
from talking to the TSM server.  Thanks for the quick response, this is
definitely one of the best forums I've been on.  I ran it with the
/validate:no and it worked perfect.

Thanks again,
Eric

-----Original Message-----
From: Prather, Wanda [mailto:Wanda.Prather AT jhuapl DOT edu]
Sent: Wednesday, April 20, 2005 12:49 PM
To: ADSM: Dist Stor Manager
Cc: Jones, Eric J
Subject: RE: Updating reg key for client in DMZ


1) You don't need to delete the registry key (or at least I never have
had to).  DSMCUTIL will do everything you need.

2) Specify option on the dsmcutil updatepw command::  /validate:no
That will cause it to change the pw in the registry without trying to
contact the server.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Jones, Eric J
Sent: Wednesday, April 20, 2005 12:38 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Updating reg key for client in DMZ


Good Afternoon.
I have a INTEL client with Win2K running TSM 5.2.2 to a TSM server on
AIX(5.2) running TSM 5.2.2.
Running through updating the scheduler does not seem to update the
password successfully.
We are in a DMZ so the client cannot talk to the server and the password
needs to be updated on the client machine.
============================================================
What I thougth would work was to
                        Delete the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient\Nodes\m
yclient
                        On a command prompt run   :   dsmcutil updatepw
/node:myclient /password:abcd123
====================================================================
The server is set with the password so when the backup runs the
passwords will be the same.
The problem is it cannot contact the server so it fails and the key does
not get updated.
How can up update the password in the registry which is currently set
incorrect.

DSM.OPT file the passwordaccess is set to "generate"
PASSWORDACCESS GENERATE

Have a Great Day,
Eric Jones
> *  eric.j.jones AT lmco DOT com
> *:   607-751-4133
Cell : 607-972-7621