Re: Changing attributes

2010-03-18 Thread Clark, Margaret
will stop. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Thomas Denier Sent: Tuesday, March 16, 2010 1:18 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Changing attributes -Margaret Clark wrote: - Fixing the dsm.opt may

Re: Changing attributes

2010-03-17 Thread Huebner,Andy,FORT WORTH,IT
: [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

Re: Changing attributes

2010-03-16 Thread Clark, Margaret
\ADSM (from both controlset instances) before reinstalling. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Schneider, Jim Sent: Tuesday, March 09, 2010 12:13 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Changing attributes In my

Re: Changing attributes

2010-03-16 Thread Thomas Denier
-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

Changing attributes

2010-03-09 Thread Fred Johanson
I've got a client that generates this 5-6 times a night: 03/09/10 03:29:03 ANR1639I Attributes changed for node NIROLO: TCP Name from OLORIN to NIROLO, TCP Address from 128.135.19.3 to 128.135.19.5, GUID from

Re: Changing attributes

2010-03-09 Thread Schneider, Jim
] Changing attributes I've got a client that generates this 5-6 times a night: 03/09/10 03:29:03 ANR1639I Attributes changed for node NIROLO: TCP Name from OLORIN to NIROLO, TCP Address from 128.135.19.3 to 128.135.19.5, GUID from fd.5f.d0.81

Re: Changing attributes

2010-03-09 Thread David E Ehresman
Two different ips, 128.135.19.3 and 128.135.19.5, both using the same tsm node name. Could result in an interesting restore scenario. David Fred Johanson f...@uchicago.edu 3/9/2010 3:02 PM I've got a client that generates this 5-6 times a night: 03/09/10 03:29:03 ANR1639I Attributes

Re: Changing attributes

2010-03-09 Thread Gary Bowers
Sounds like you've got the same client name on two different servers. Each time they check in with TSM, they are updating their IP and GUID. Go check the dsm.opt on both those servers. Gary On Mar 9, 2010, at 2:02 PM, Fred Johanson wrote: I've got a client that generates this 5-6 times a