Win 2003 and 5.3.4 client install problems

[jackvant]

We've been around and around on this issue with Tivoli Support and the problem is far from solved. We have installed 5.3.4 on Windows 2003 servers with mixed success. We do the standard install with the client acceptor service linked to the schedule, but the acceptor doesn't start the schedule it is linked to and so the scheduled backup fails. We got lucky on one machine and the error log indicated that registry key couldn't be read. When we looked at the key, it was set properly but the acceptor simply insisted that it couldn't read the key. We reset the key using the wizard and the scheduled event missed again. We then used dsmcutil to reset the key and suddenly all was lovely and the scheduled event worked. When we got done with this exercise, we checked a number of the other machines and some had the key set properly and others had the key missing. We reset these using the command line.



We have had this problem with half of the new installs we have done, and we have had about a 20% failure rate on upgrades. We have tried to convince TSM support that there is some problem that prohibits the acceptor service from reading the registry key properly. We're good and stumped by this, and we have about 60 Mircorosft nodes and counting. Any Microsoft experts out there who might have an idea as to where to look.



We've done everything asked of us by Tivoli. We uninstalled and reinstalled. Deleted and re-added the services and used the command line. We have a bad feeling that the machines we have managed to fix with the command line utility are going to cause us grief again very soon.

 

[cheffern]

Hey Jack -



Try this.

Shut down the Scheduler and the CAD and any other TSM services to be safe -

Run this command:

dsmcutil update cad /name:"TSM Acceptor" /cadschedname:"TSM Remote Client Agent"



Make sure you have this entry in the filesystem dsm.opt:

MANAGEDSERVICES WEBCLIENT SCHEDULE



Start all TSM services back up -

And it should now be ok.



This assumes you are having the same problem I had -

And it sounds like it is -

So I hope this helps you.



(This was a "home grown" fix - Tivoli support could not assist us either -

In some cases this didn't work fully though, so we ended up abandoning the CAD for nodes that weren't restrained memory-wise...Using the scheduler without the CAD has had no adverse affect on our systems. )



Good Luck -

-Chef.

 

[LED888]

Just curious.

If the CAD Service is not starting the schedule backup, why not use the schedule service?

Or even use the schedule with Windows, the bad thing is that the dsmsched.log is not updated since the backup is being started out side of TSM.



-Sias