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 <rickadam...@winn-dixie.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:ads...@vm.marist.edu] On Behalf Of Roger Deschner Sent: Thursday, April 01, 2010 5:16 PM To: ADSM-L@VM.MARIST.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 rog...@uic.edu ======I have not lost my mind -- it is backed up on tape somewhere.=====
