The logs won't necessarily show you the entire picture, a DPDTrace would help us verify you are see scan issue with LDR/GDR. I would suggest creating a case and then uploading the DPDtrace information from the following document:
DPDTrace Logging Tool Used For Patch Detection Issues (Include the registry exports from the bottom of the document)
Let me know if you have any issue creating the case.
Thanks. Well in fact . I am a BladeLogic user, which use Shavlik engine under the hood. So yes I already last Friday opened an BMC official Ticket. BMC confirmed on behalf of Shavlik, using my DPDTrace I have provided, that a new xml version would fix this.
Note : Above case/behavior and official BMC ticket I did open, IS ONLY one example of MANY CASE'S I did found so far regarding's this type of behavior.
Question : Will I have each time to open a case with BMC BladeLogic ?
Question : Because I am a BladeLogic user, may I open case/ticket directly to shavlik ?
We are definitely aware of the issues LDR/GDR branching can cause during the detection process. The only course of action now is to submit the issues so the Content Team We are working toward 'next gen' data for Protect 9.2 that should virtually eliminate issues like this in the upcoming months. That being, you should speak with your BladeLogic contact to see when they will implement the 9.2 SDK once it is release later this year.
Yes, you will need to work through the BladeLogic to report these issues.
Thanks a lot, about those fresh news and details. Appreciate.