You can also edit the registry keys to fix the name. That is how we handle the problem.
Andy Huebner -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Thomas Denier Sent: Tuesday, March 16, 2010 3:18 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Changing attributes -----Margaret Clark wrote: ----- >Fixing the dsm.opt may not be enough. When Windows nodes are cloned >with the TSM client in place, the registry will cause this >interesting behavior even after the dsm.opt is updated. >I've found I have to deinstall the TSM client and then delete the >ADSM subkey HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM (from both >controlset instances) before reinstalling. Windows adminsitrators at our site occasionally rename existing Windows systems. We almost never specify node names in dsm.opt files for Windows client; we let the client use the machine name as the node name. When a Windows client is renamed the client scheduler service continues to use the old node name, presumably because the node name was recorded in the registry when the service was created. We have always been able to clean this up by removing and recreating the service. We did not need to deinstall the client software or manually remove registry keys. This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
