Thomas, Thanks for both of your responses. You have confirmed what we are seeing. We rooted through the registry and see the keys with the old node name and encrypted password. The box was renamed and rebooted but the GUI was never bought up. As soon as we bought up the GUI, it grabbed the hostname and attempted (and failed) to connect to the TSM server since we kept the old nodename.
Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html From: Thomas Denier <thomas.den...@jeffersonhospital.org> To: ADSM-L@VM.MARIST.EDU Date: 08/22/2011 12:47 PM Subject: Re: [ADSM-L] Renaming a Windows node - where does it get the nodename if no nodename statement? Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> -----Zoltan Forray wrote: ----- >Please correct me if I am wrong, but I was under the impression that >if a Windows node does NOT have a NODENAME statement in it's dsm.opt, >it simply asks the OS for the hostname and uses that. This value is >also used for the filespace names. The documented default is the Windows machine name. This is often the same as the IP host name, but it is possible for the two names to be different. [Material removed] >Or does the scheduling process use the registry keys, not caring >about the hostname changed? Our experience with renamed Windows nodes indicates that the scheduler service locks in the node name in effect at the time when dsmcutil was used to create the service. I don't know whether this behavior is documented. The service presumably uses the registry to store the node name. When a Windows node is renamed, we tell the system administrator do remove and recreate the service.