Curious. What is the symptom when this happens? Does the client just get "invalid password", or is there some other error message?
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of James Thorne Sent: Thursday, November 07, 2013 10:03 AM To: [email protected] Subject: Re: [ADSM-L] Today's self-inflicted wound: IC90735 APAR IC90735 was created in response to a PMR I raised after hitting this problem on a 6.2 to 6.3 server upgrade. It is referring to the encryption used during authentication and only affects 6.3 and 6.4 clients; from IBM: "this does not affect TSM Client versions below 6.3, for the following reason. The client implemented AES for this authentication was in 6.3, and the 6.2 clients can only use DES, so that 6.3 server won't try to use AES with them." This was fixed in baclient 6.3.1.2 and 6.4.0.5 (6.4.0.6 for Windows) so any clients at or above those versions should not hit the problem. James. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Nick Laflamme Sent: 06 November 2013 16:53 To: [email protected] Subject: [ADSM-L] Today's self-inflicted wound: IC90735 After a few uneventful upgrades from 6.2 to 6.3 TSM servers in my most recent TSM shop, my first such upgrade for my current client hit IC90735: some clients using encryption don't correctly change to AES-128 and thus are rejected for invalid passwords. The APAR led to client changes, not server changes, and I for one don't know how to determine ahead if time which clients are using encryption. So, if you still have an upgrade to TSM 6.3 server (or 7.1?!?), here's one more concern to note. Off to bandage my feet, Nick
