server Migration to v6.2, dont want to be prompt for password on TSM Client

petitehada

Active Newcomer
Joined
Dec 30, 2009
Messages
7
Reaction score
0
Points
0
Hi,

We are migrating our TSM clients from a server v5.5 to a server v6.2 (2 different physical servers). Where have exported the nodes definition from the 5.5 instance and imported those definitions to the v6.2 server instance.
We have about 400 nodes and we want to avoid going on each client and type again the password. :(
Do you have any idea to avoid having the password prompted again ?

Note : we already have the option : password generate

Thanks,
 
The stored TSM password on the client is associated with the TSM instance name as defined in the dsm.opt - since you're using the export/import route your TSM instance name is changing, therefore there is no stored password...
 
Solution :servername + guid

Seems with found the solution :
Ensure the servername are the same on the v5.5 and the v6.2 servers
+
Guid are the same on both servers

To change GUID : [FONT=&quot]On Windows, open the Registry Editor (regedit) and look for the
HKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\GUID key

We will confirm it with IBM support tomorrow.
[/FONT]
 
Let us know if you are able to alter the GUID for the server instance - interesting :)
 
Very interesting.
We didn't ran in that issue because we have drop and reinstalled the instance after changing the GUID.
After reading your post, we did a DB backup and it was succesfull.

Thanks for your help ! :)

From my own experience you might get problems with backing up the db2 database.
ANR2987W Session ended because of machine GUID or local host IP address mismatch
see:
http://adsm.org/forum/showthread.php?20980-TSM-6.2-deployment-issues
So it is a god thing that you contacted IBM before you made the update, but you can chnage the guid back again :)
 
Brilliant.
This is very good news.

running insertdb right now :)



NR1379I INSERTDB: Read 131,777,800,304 bytes and inserted 949,466,986 databas
ntries in 23:06:20 (5439.08 megabytes per hour).
....
ANR1379I INSERTDB: Read 1,759,367,279 bytes and inserted 12,587,994 database
entries in 0:05:00 (20124.00 megabytes per hour).
ANR1379I INSERTDB: Read 2,993,159,346 bytes and inserted 21,677,062 database
entries in 0:10:01 (17095.51 megabytes per hour).

Why the drop in speed?

Maybe 1 hour left to go (This is only a test upgrade top prepare for the real upgrade).
 
Nearly done. Will test your workaround. Thank you!


ANR1379I INSERTDB: Read 131,777,800,304 bytes and inserted 949,466,986 database
entries in 23:06:20 (5439.08 megabytes per hour).
ANR1364I Input volume e:\upgrad\88177183.ost closed.
ANR1379I INSERTDB: Read 132,683,468,709 bytes and inserted 955,901,129 database
entries in 23:36:20 (5360.43 megabytes per hour).
 
Back
Top