I've seen problems on some Winders machines where if the value returned by the %COMPUTERNAME% is in lower-case letters and you didn't specify NODENAME, then different portions of TSM react differently. What I had was that the Web client interface would change the encrypted stored password that what was originally stored with the TSM B/A client and scheduler service.
I don't know if this is your problems, but try specifying the NODENAME in the DSM.OPT file and on the DSMCUTIL command that installs the service. Bill Boyer DSS, Inc. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Joel Fuhrman Sent: Friday, March 15, 2002 9:45 PM To: [EMAIL PROTECTED] Subject: scheduler service overwrites baclient's password The password key which is located in the registry at HKLM\software\ibm\adsm\backupclient\nodes\W7\adsm is removed when the scheduler service is started. The scheduled log contains: 03/15/2002 18:11:11 Querying server for next scheduled event. 03/15/2002 18:11:11 Node Name: W7 03/15/2002 18:11:11 Please enter your user id <W7>: ANS1029E Communications have been dropped. 03/15/2002 18:11:11 Scheduler has been stopped. Removing and re-installing the Scheduler Service and TSM (version 4.2.1.20) did not help. BACKGROUND: The system was created using a clone disk on which the TSM installed. After the disk is cloned, the hostname is changed along with the sids. The host then joins the domain. The TSM client is used to register with the TSM server. Finally, the TSM scheduler service is created and it wipes out the password. Any suggestions would be appreciated.
