Hi,

For windows, you can remotely change the registry key
\HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient\Nodes\
<node_name>\<ITSM server name> folder and after restarting the ITSM
service(s) things should work.

Regards,

Karel

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Schneider, John
Sent: maandag 12 februari 2007 17:28
To: ADSM-L@VM.MARIST.EDU
Subject: Problem changing TSM server name

Greetings,
        I recently inherited a few TSM servers.  Their internal TSM
server name does match the DNS name.  The TSM clients connect to it via
the DNS name, but we would like to change the TSM server name to match.
For example, the DNS names of our standard are ABCD-TSM1, where ABCD is
a 4 letter abreviation of the site name.  But the internal TSM name of
these servers are ADSM, or TSM-SERVER1 or something.

        This is easy to change with SET SERVERNAME, but when I tried to
change one of them, I hit an unforeseen consequence.  The next night
when the client backups kicked off, all the clients failed to run their
schedules because of authentication errors.  The message in the activity
log showed the clients getting unknown client errors, and the client
name, instead of the real client name, looked like some sort of
encrypted garbage characters.
As soon as I set the TSM servername back to the original, they all went
back to working.

        This leads me to believe that the TSM servername is used during
the initial password exchange-and-save when the client first
authenticated and saved it's local password.  To fix this then, will we
have to go out to every TSM client one at a time and re-authenticate and
save the passwords?
Does anyone one know of a way to change the servername without touching
each of the clients?


Best Regards,

John D. Schneider
Sr. System Administrator - Storage
Sisters of Mercy Health System
3637 South Geyer Road
St. Louis, MO.  63127
Email:  [EMAIL PROTECTED]
Office: 314-364-3150, Cell:  314-486-2359

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request

Reply via email to