Don't do this.  Use passwordaccess generate and let the server/client change
the password periodically.  That is what happens.  Don't try to automate
something that is already automated by the product.

Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs, CO 80949
[EMAIL PROTECTED] or [EMAIL PROTECTED]
www.storsol.com or www.storserver.com
(719)531-5926
Fax: (240)539-7175


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Kevin
Sent: Wednesday, January 09, 2002 5:45 PM
To: [EMAIL PROTECTED]
Subject: Re: Script procedure to automate updating 300+ NT TSM client
password s


My understanding is that if you expire the password you have to initiate
a client session and type in the new password so that the scheduled
session will run properly later that evening. The alternative is that
the client / server session will have a TCP/IP communications failure as
the password will not be recognized. This of course is providing you
have password access set to generate in the client options file, and
registration set to closed.

Has this changed? I believe this is true as of version 3.1 of ADSM, but
since installing and running TSM 4.2.1.7 I haven't tried it.

Kevin.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
taford
Sent: Wednesday, January 09, 2002 6:01 PM
To: [EMAIL PROTECTED]
Subject: Script procedure to automate updating 300+ NT TSM client
password s

Has anyone tempted such a task?  Looking to streamline the
administration of
updating TSM client passwords every 90 days.

Tim Ford
System Manager
Micron Technology, Inc.
[EMAIL PROTECTED]

Reply via email to