Paul,
Regarding the characteristic where the TSM Scheduler remembers the nodename.

For Windows:

" The service seems to remember the node name in effect when the service was 
created, even in the absence of a 'nodename' option in dsm.opt. I don't know 
whether there is a way to change the node name the service uses; we advise 
client system administrators to remove the service and create a new one when a 
Windows system is renamed."

** Your way of fixing this is best; uninstalling then reinstalling the 
scheduler. **

        There is a registry entry for the TSM Scheduler service that contains 
the node name.  I used to have a problem with some of the new Windows servers 
that came into TSM MISSing their backup for authentication reasons.  
        A Windows admin eventually told me why and their way to fix it.  
        In our case, the servers were all built from the same image.  They all 
had the same machine name.  When TSM was installed and the Scheduler set up and 
tested, it was under the standard "build" nodename.  Subsequently, before the 
machine went into production, it was renamed.  Sometimes the nodename in the 
dsm.opt file was changed, but authentication still failed.
        
The Windows folks used to edit the Registry entry for the TSM Scheduler 
service...but your method is much safer.



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Thomas Denier
Sent: Thursday, June 02, 2011 3:20 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TSM & client machine renames

-----Paul Zarnowski wrote: ----- 

IMPORTANT:  E-mail sent through the Internet is not secure. Legg Mason 
therefore recommends that you do not send any confidential or sensitive 
information to us via electronic mail, including social security numbers, 
account numbers, or personal identification numbers. Delivery, and or timely 
delivery of Internet mail is not guaranteed. Legg Mason therefore recommends 
that you do not send time sensitive 
or action-oriented messages to us via electronic mail.

This message is intended for the addressee only and may contain privileged or 
confidential information. Unless you are the intended recipient, you may not 
use, copy or disclose to anyone any information contained in this message. If 
you have received this message in error, please notify the author by replying 
to this message and then kindly delete the message. Thank you.