Re: Renaming a W2K node
Everything you did is OK. And with old versions of the client (V3.1, for instance) that is all you had to do. But on W2K, you need more steps for the service. 1) Repeat all the stuff you did, that makes the GUI OK. 2) Start the GUI, pull down Utilities, Setup Wizard 3) Click (only) the check box for configure scheduler. - NEXT 4) Click modify existing scheduler - NEXT 5) On the next page, click to highlight the service name - NEXT 6) Keep walking through and take all the defaults except put in the the new nodename and password. 7) Click FINISH. 8) restart the scheduler service Bottom line is that the service installation saves stuff in the registry and you have to fix it this way. If this doesn't fix it, I would try using the setup wizard to uninstall the old service, then reinstall it with the new nodename. -Original Message- From: Todd Lundstedt [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 05, 2003 7:00 PM To: [EMAIL PROTECTED] Subject: Renaming a W2K node AIX 4.3.3 running TSM Server 4.2.1.7. I have a few client nodes that are W2K servers. Oddly, they are named after our NT servers (NT-ServerA, NT-ServerB, etc..). The dsm.opt file contains the NT machine name as the NodeName. I would like to change the NodeName to W2K-ServerA, but not rename the machine name. ... I stopped the scheduler service on the client node. ... I modified the name in dsm.opt, and saved the file ... I renamed the node on the TSM Server (rename node nt-servera w2k-servera, or whatever the command is... I actually used the web admin GUI to do it). ... I entered dsmc query session at the command line of the client node. ... ... it indicated it was node W2K-ServerA, requested the user ID, and password.. I entered (defaulted) the ID, and keyed in the password for that node. The information was returned as expected. ... I entered dsmc query session at the command line of the client node, again. ... ... The information was returned as expected, without ID and password being required (by the way, the opt file does have passwordaccess generate), still indicating it was the new nodename, W2K-ServerA. ... I started the service up... it started and quietly failed (no GUI messages on the screen). I checked the dsmsched.log file, and it appeared that it attempted to connect using NT-ServerA instead of W2K-ServerA. Baffled.. so ... I checked to properties on the service.. I didn't see anything that indicated NT-ServerA. ... I started the Backup/Archive GUI (vers 5.1.x) and checked the preferences there. Everything was as I would have expected it to be based on the values in the dsm.opt file, including the node name being W2K-ServerA After much searching of documentation and scratching of head, I punted and changed everything (dsm.opt, nodename on TSM server, etc.) back to NT-ServerA and the service started up and stayed up. What am I missing to change the node name? Something is still using the old node name when it attempts to contact the TSM server, and of course, that nodename no longer exists on the TSM server. I did do some looking around in that quickFaQ that Richard links to all the time... didn't find anything in there that jumped out at me. Same with the last 3 months of ADSM.org archives, and IBM's horridly slow and completely non-user-friendly support pages. I am lost... Thanks in advance Todd
Re: Renaming a W2K node
Thanks for everyone's responses on this. With the suggestions given here, I was able to write up a procedure to assist our NT/W2K admins with this function. It involves using the DSMCUTIL command instead of the wizard, and a little thought before doing it. In these special cases, I wanted the TSM node name to be something other than the NETBIOS name, and the scripts we have setup for the NT admins to run includes registering the node, and installing the services with %computername%. Which means, the filespace names will default to \\%computername%\driveletter$, for a totally different named node. However, if the NETBIOS name is changing along with the nodename, the filespace names will need to be changed as well (or else they will just backup full again). Anyway.. Thanks again everyone. Todd |+-- || Prather, Wanda| || [EMAIL PROTECTED]| || HUAPL.EDU | || Sent by: ADSM: | || Dist Stor | || Manager| || [EMAIL PROTECTED]| || T.EDU | || | || | || 03/13/2003 01:13| || PM | || Please respond | || to ADSM: Dist | || Stor Manager | || | |+-- -| | | | To: [EMAIL PROTECTED] | | cc: | | Fax to: | | Subject: Re: Renaming a W2K node | -| Everything you did is OK. And with old versions of the client (V3.1, for instance) that is all you had to do. But on W2K, you need more steps for the service. 1) Repeat all the stuff you did, that makes the GUI OK. 2) Start the GUI, pull down Utilities, Setup Wizard 3) Click (only) the check box for configure scheduler. - NEXT 4) Click modify existing scheduler - NEXT 5) On the next page, click to highlight the service name - NEXT 6) Keep walking through and take all the defaults except put in the the new nodename and password. 7) Click FINISH. 8) restart the scheduler service Bottom line is that the service installation saves stuff in the registry and you have to fix it this way. If this doesn't fix it, I would try using the setup wizard to uninstall the old service, then reinstall it with the new nodename. -Original Message- From: Todd Lundstedt [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 05, 2003 7:00 PM To: [EMAIL PROTECTED] Subject: Renaming a W2K node AIX 4.3.3 running TSM Server 4.2.1.7. I have a few client nodes that are W2K servers. Oddly, they are named after our NT servers (NT-ServerA, NT-ServerB, etc..). The dsm.opt file contains the NT machine name as the NodeName. I would like to change the NodeName to W2K-ServerA, but not rename the machine name. ... I stopped the scheduler service on the client node. ... I modified the name in dsm.opt, and saved the file ... I renamed the node on the TSM Server (rename node nt-servera w2k-servera, or whatever the command is... I actually used the web admin GUI to do it). ... I entered dsmc query session at the command line of the client node. ... ... it indicated it was node W2K-ServerA, requested the user ID, and password.. I entered (defaulted) the ID, and keyed in the password for that node. The information was returned as expected. ... I entered dsmc query session at the command line of the client node, again. ... ... The information was returned as expected, without ID and password being required (by the way, the opt file does have passwordaccess generate), still indicating it was the new nodename, W2K-ServerA. ... I started the service up... it started and quietly failed (no GUI messages on the screen). I checked the dsmsched.log file, and it appeared that it attempted to connect using NT-ServerA instead of W2K-ServerA. Baffled.. so ... I checked to properties on the service.. I didn't see anything that indicated NT-ServerA. ... I started the Backup/Archive GUI (vers 5.1.x) and checked the preferences there. Everything was as I would have expected it to be based
Re: Renaming a W2K node
Hello Have you tried to remove the service and then reinstall it? The service stores the nodename to use in the Registry. Regards Niklas -Original Message- From: Todd Lundstedt [mailto:[EMAIL PROTECTED] Sent: den 6 mars 2003 01:00 To: [EMAIL PROTECTED] Subject: Renaming a W2K node AIX 4.3.3 running TSM Server 4.2.1.7. I have a few client nodes that are W2K servers. Oddly, they are named after our NT servers (NT-ServerA, NT-ServerB, etc..). The dsm.opt file contains the NT machine name as the NodeName. I would like to change the NodeName to W2K-ServerA, but not rename the machine name. ... I stopped the scheduler service on the client node. ... I modified the name in dsm.opt, and saved the file ... I renamed the node on the TSM Server (rename node nt-servera w2k-servera, or whatever the command is... I actually used the web admin GUI to do it). ... I entered dsmc query session at the command line of the client node. ... ... it indicated it was node W2K-ServerA, requested the user ID, and password.. I entered (defaulted) the ID, and keyed in the password for that node. The information was returned as expected. ... I entered dsmc query session at the command line of the client node, again. ... ... The information was returned as expected, without ID and password being required (by the way, the opt file does have passwordaccess generate), still indicating it was the new nodename, W2K-ServerA. ... I started the service up... it started and quietly failed (no GUI messages on the screen). I checked the dsmsched.log file, and it appeared that it attempted to connect using NT-ServerA instead of W2K-ServerA. Baffled.. so ... I checked to properties on the service.. I didn't see anything that indicated NT-ServerA. ... I started the Backup/Archive GUI (vers 5.1.x) and checked the preferences there. Everything was as I would have expected it to be based on the values in the dsm.opt file, including the node name being W2K-ServerA After much searching of documentation and scratching of head, I punted and changed everything (dsm.opt, nodename on TSM server, etc.) back to NT-ServerA and the service started up and stayed up. What am I missing to change the node name? Something is still using the old node name when it attempts to contact the TSM server, and of course, that nodename no longer exists on the TSM server. I did do some looking around in that quickFaQ that Richard links to all the time... didn't find anything in there that jumped out at me. Same with the last 3 months of ADSM.org archives, and IBM's horridly slow and completely non-user-friendly support pages. I am lost... Thanks in advance Todd
Re: Renaming a W2K node
Hello Niklas, I have also observed that 'feature', where nodename is not the nodename in dsm.opt. You should start the Client GUI, from the menu choose Utilities, Setup Wizard, Help me configure Client Scheduler, Update previously installed scheduler, and follow the steps through. It asks for what dsm.opt file to use, and right after that is asks what nodename to connect as == This is where you have to change it to the NEW nodename. I haven't checked where this nodename (for the scheduler) is kept (file|registry?), but I have planned to look into it. Hope this solves your problem. Rgds. Geirr G. Halvorsen -Original Message- From: Niklas Lundstrom [mailto:[EMAIL PROTECTED] Sent: 6. marts 2003 09:18 To: [EMAIL PROTECTED] Subject: Re: Renaming a W2K node Hello Have you tried to remove the service and then reinstall it? The service stores the nodename to use in the Registry. Regards Niklas -Original Message- From: Todd Lundstedt [mailto:[EMAIL PROTECTED] Sent: den 6 mars 2003 01:00 To: [EMAIL PROTECTED] Subject: Renaming a W2K node AIX 4.3.3 running TSM Server 4.2.1.7. I have a few client nodes that are W2K servers. Oddly, they are named after our NT servers (NT-ServerA, NT-ServerB, etc..). The dsm.opt file contains the NT machine name as the NodeName. I would like to change the NodeName to W2K-ServerA, but not rename the machine name. ... I stopped the scheduler service on the client node. ... I modified the name in dsm.opt, and saved the file ... I renamed the node on the TSM Server (rename node nt-servera w2k-servera, or whatever the command is... I actually used the web admin GUI to do it). ... I entered dsmc query session at the command line of the client node. ... ... it indicated it was node W2K-ServerA, requested the user ID, and password.. I entered (defaulted) the ID, and keyed in the password for that node. The information was returned as expected. ... I entered dsmc query session at the command line of the client node, again. ... ... The information was returned as expected, without ID and password being required (by the way, the opt file does have passwordaccess generate), still indicating it was the new nodename, W2K-ServerA. ... I started the service up... it started and quietly failed (no GUI messages on the screen). I checked the dsmsched.log file, and it appeared that it attempted to connect using NT-ServerA instead of W2K-ServerA. Baffled.. so ... I checked to properties on the service.. I didn't see anything that indicated NT-ServerA. ... I started the Backup/Archive GUI (vers 5.1.x) and checked the preferences there. Everything was as I would have expected it to be based on the values in the dsm.opt file, including the node name being W2K-ServerA After much searching of documentation and scratching of head, I punted and changed everything (dsm.opt, nodename on TSM server, etc.) back to NT-ServerA and the service started up and stayed up. What am I missing to change the node name? Something is still using the old node name when it attempts to contact the TSM server, and of course, that nodename no longer exists on the TSM server. I did do some looking around in that quickFaQ that Richard links to all the time... didn't find anything in there that jumped out at me. Same with the last 3 months of ADSM.org archives, and IBM's horridly slow and completely non-user-friendly support pages. I am lost... Thanks in advance Todd
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.
Re: Renaming a W2K node
H 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.
Renaming a W2K node
AIX 4.3.3 running TSM Server 4.2.1.7. I have a few client nodes that are W2K servers. Oddly, they are named after our NT servers (NT-ServerA, NT-ServerB, etc..). The dsm.opt file contains the NT machine name as the NodeName. I would like to change the NodeName to W2K-ServerA, but not rename the machine name. ... I stopped the scheduler service on the client node. ... I modified the name in dsm.opt, and saved the file ... I renamed the node on the TSM Server (rename node nt-servera w2k-servera, or whatever the command is... I actually used the web admin GUI to do it). ... I entered dsmc query session at the command line of the client node. ... ... it indicated it was node W2K-ServerA, requested the user ID, and password.. I entered (defaulted) the ID, and keyed in the password for that node. The information was returned as expected. ... I entered dsmc query session at the command line of the client node, again. ... ... The information was returned as expected, without ID and password being required (by the way, the opt file does have passwordaccess generate), still indicating it was the new nodename, W2K-ServerA. ... I started the service up... it started and quietly failed (no GUI messages on the screen). I checked the dsmsched.log file, and it appeared that it attempted to connect using NT-ServerA instead of W2K-ServerA. Baffled.. so ... I checked to properties on the service.. I didn't see anything that indicated NT-ServerA. ... I started the Backup/Archive GUI (vers 5.1.x) and checked the preferences there. Everything was as I would have expected it to be based on the values in the dsm.opt file, including the node name being W2K-ServerA After much searching of documentation and scratching of head, I punted and changed everything (dsm.opt, nodename on TSM server, etc.) back to NT-ServerA and the service started up and stayed up. What am I missing to change the node name? Something is still using the old node name when it attempts to contact the TSM server, and of course, that nodename no longer exists on the TSM server. I did do some looking around in that quickFaQ that Richard links to all the time... didn't find anything in there that jumped out at me. Same with the last 3 months of ADSM.org archives, and IBM's horridly slow and completely non-user-friendly support pages. I am lost... Thanks in advance Todd
