Hmmmm.... I suspect you would need to use dsmcutil.exe to update the node name and password to the new node, i.e.:
dsmcutil update /name:"your service name" /node:newnodename /password:password Then stop/restart the service. You would need to update all services installed. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply) The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. Thomas Denier <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/06/2003 07:57 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Re: Renaming a W2K node My experience has been the same as that of the other respondents: the node name used when the scheduler service is created is frozen in. I have always ended up having the system administrator delete and recreate the service when Windows nodes have been renamed at our site. There is another issue you will need to deal with. The node name for a Windows client is embedded in each of the file space names corresponding to drive letters (but not in the SYSTEM OBJECT file space). You will need to rename the file spaces to match the new node name.