A password scheme may be a good idea also. We don't particularly have
it so that the clients "know" the passwords anyways, so having a
scheme may be a good idea for the future also so that you know ahead
of time what the password would be.

On 9/22/05, Scott Grover <Scott.R.Grover AT supervalu DOT com> wrote:
> I believe you'll need to set password expiration to 0 on node definitions so 
> it
> doesn't happen again....but you'll have to reset passwords individually from
> each client for the current situation.
>
>
>
>              "Gill, Geoffrey L."
>              <GEOFFREY.L.GILL@SA
>              IC.COM>                                                         
> To
>              Sent by: "ADSM:             ADSM-L AT VM.MARIST DOT EDU
>              Dist Stor Manager"                                              
> cc
>              <[email protected]
>              DU>                                                        
> Subject
>                                          [ADSM-L] 95% missed backups last 
> night
>                                          ( found the problem but what    is 
> the
>              09/22/2005 12:01 PM         easy fix)
>
>
>               Please respond to
>               "ADSM: Dist Stor
>                   Manager"
>              <[email protected]
>                      DU>
>
>
>
>
>
>
> Ok here's an update on my own post. While waiting for a callback from
>
> support I seem to have discovered what the problem is. It seems that the
>
> passwords have not kept in synch between client and server. Yes
>
> passwordaccess generate is set on all the nodes so I don't understand the
>
> problem.
>
>
>
> I logged on to one of my clients and opened the baclient. It asked for the
>
> password when it should not have. I changed the password on the server to a
>
> known value and entered that in the client window and it connected. I was
>
> then able to restart the scheduler service and the client connected properly
>
> instead of showing the odd characters on the TSM server.
>
>
>
> The problem now is we have 250 nodes that need fixing and the only way I
>
> know to fix them is to do what I did. I have no clue what the passwords are
>
> of these nodes and neither does anyone else. So after I change all of them I
>
> have to then tell the administrators so they can do what I did.
>
>
>
> Boy is there going to be a bunch of pissed people, including me, if I can't
>
> do something on the server to fix this.
>
>
>
> The next question is how long is it going to be till this happens again?
>
>
>
>
>
>
>
> Thanks,
>
>
>
> Geoff Gill
>
> TSM Administrator
>
> SAIC M/S-G1b
>
> (858)826-4062
>
> Email:  <mailto:geoffrey.l.gill AT saic DOT com> geoffrey.l.gill AT saic DOT 
> com
>