Uninstall and reinstall may not be the solution here. On one of the agents where the DTM sync isnot working, can you check the contents of dtm.log ? Also, check if the notify was received succesfully by radexecd.log. Do you see dtm.xml created in the agent\lib folder.
You must also confirm the presence of SAP.EdM in the lib folder.
Using the above information we can try to figure out what is going on wrong.
Thanks for your reply. Actually in some of my clients DTM.xml lists the jobs perfectly fine and on some of them it does not list any job. I think that it is the RMA.CFG in the ETC folder of Management agent that is corrupted. So I am planning to uninstall all old agents using WMI command and then deploy agents from the Core. I guess it will resolve the issue. What do u suggest?
The DTM agent requests for the jobs using the RMADEVDN attribute. If for some reason this value is not available it just uses the device ( machine) name and then requests for the available jobs.
Hence it is quite possile that the jobs have been scheduled using either FQDN or the devicename and hence only 1 combination is working for the client. If you uninstall the RMADEVDN value may get refreshed and hence work.
If feasible you can try uninstalling . However I would rather suggest using rmareset.tcl option. Please talk to support on how to get and use this file. It mayhelp solving the corrupt rma.cfg file.