Doesn't work that way.  The password must not have been stored (i.e. the
GUI run for the first time).

When defining or resetting the password for a Windoz box, I always tell
the client:

1.  Stop the scheduler/GUI
2.  I reset the password on the TSM server
3.  Start the GUI.  You will be prompted for the password.  Stop and start
the GUI again.  You should not be prompted for the password, the second
time.
4.  Start the scheduler service



From:
ADSM-L <tsm AT NETWORKC.CO DOT UK>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
04/02/2010 09:51 AM
Subject:
Re: [ADSM-L] Why need password to create client scheduler?
Sent by:
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



That's how PASSWORDACCESS GENERATE works for sure, but I'm not quite
sure that's what Roger is asking -the question is why, if you're
already using PASSWORDACCESS GENERATE and your password is already
presumably stored in the registry, you need to input it again when
setting up the scheduler.

/David McClelland
London

On 2 Apr 2010, at 14:03, Rick Adamson <RickAdamson AT WINN-DIXIE DOT COM>
wrote:

> In Windows this is so that the password can be stored in the registry,
> once stored you do not have to reenter it. when the client is
> installed
> and configured issue any generic command from the cli, such as "dsmc q
> tsm", it will prompt you for the password, enter it and you are set.
> Additionally, when the password expires, as defined on the TSM
> server it
> will be updated on the client.
>
> ~Rick
> JAX FL
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> Behalf Of
> Roger Deschner
> Sent: Thursday, April 01, 2010 5:16 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] Why need password to create client scheduler?
>
> If PASSWORDACCESS GENERATE is in effect and has been initialized with
> the node password successfully encrypted and stored, and if you then
> go
> to create a scheduler, why do you need to give the node password
> again?
>
> This sometimes means, that if the user no longer knows their password,
> that we have to change their password for them just so they can
> create a
> scheduler.
>
> Is there a way around this? Perhaps some creative use of the dsmcutil
> program?
>
> Roger Deschner      University of Illinois at Chicago     rogerd AT uic DOT 
> edu
> ======I have not lost my mind -- it is backed up on tape
> somewhere.=====