Novell is now a part of Micro Focus

My Favorites

Close

Please to see your favorites.

How to get verbose debug logging from LM.Detection.exe

This document (7014131) is provided subject to the disclaimer at the end of this document.

Environment

Novell ZENworks Patch Management 11

Situation

How to get verbose debug logging from LM.Detection.exe

Note:  Note:  It may be necessary to first rename registry keys HKEY_LOCAL_MACHINE\SOFTWARE\Patchlink.com\cache\SYSTEM_HASH and HKEY_LOCAL_MACHINE\SOFTWARE\Patchlink.com\Discovery Agent\NativeScan entry to bypass cache and rescan fully.

Resolution

LM.Detection.exe /ErrorStdOut /registry /loglevel 4 /e /g 83350760-5AE5-ABAA-46178CBAA48E
"/g" is guid of the patch. Once the patch has run on the device there will be a corresponding _results.txt file at the root of "%ZENWORKS_HOME%\zpm".
Example:  "Update for Windows 7 x64 (KB2882822).pls_83350760-5AE5-ABAA-46178CBAA48E.plp.results.txt"

Output: %ZENWORKS_HOME%\zpm\lm.detection-83350760-5AE5-ABAA-46178CBAA48E.txt

Cause

At times the need to troubleshoot LM.Detection.exe is needed to isolate why a patch will not install.

Additional Information

Other things to help with lm.detection.  Disable PD cache in case files in workdir are corrupt.  Ensure latest ospx files are present.  Sometimes corruption in system %temp% files also can contribute.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7014131
  • Creation Date:18-NOV-13
  • Modified Date:16-FEB-18
    • NovellZENworks Patch Management

Did this document solve your problem? Provide Feedback