03-07-2013 08:52 AM
I have client computers with HPCAE agent installed on them with Patch notify working fine.
I try to create a DTM job and then run a notify refesh DTM but the job does not get reflected on the Clients hence
I uninstall the agent on client and reinstall agent manually. Now i can create a DTM job succesfully....
I am puzzled, Do I have to uninstall clients manually on all computers to create DTM sync successfull.
I have another question, How do i uninstall agents from client computers using Agent deployment wizard.
03-14-2013 09:26 AM
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.
03-17-2013 10:53 AM
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?
03-26-2013 06:35 AM
In order to schedule agent connects (software, patch, etc) HP strongly recommends the use of TIMERS.
Information and examples on TIMERs can be found in the "HP 8.10 Client Automation Administrator Guide”, page 235, section E- Creating Timers in Configuration Server Database.
I hope this helps.
04-05-2013 01:25 AM
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.