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.
- Rename registry value HKEY_LOCAL_MACHINE\SOFTWARE\Patchlink.com\cache\SYSTEM_HASH entry to bypass cache and rescan fully.
- Look in registry HKEY_LOCAL_MACHINE\SOFTWARE\Patchlink.com\Discovery Agent\NativeScan search below for the name of the patch to test. Example: 2018-02 Security Only Quality Update for Windows 7 x64 (KB4074587) is found under HKEY_LOCAL_MACHINE\SOFTWARE\Patchlink.com\Discovery Agent\NativeScan\038b7343-567a-489c-9a7b-99359061b585
- Or do a database query to get the guid from patch signature table.
Example: select type from patchsignature where name = '2018-02 Security Only Quality Update for Windows 7 x64 (KB4074587)' gives this: 038B7343-567A-489C-9A7B-99359061B585 (remove the brackets)
- Rename the registry key above so that it will force re-scan.
- Run the following command from %ZENWORKS_HOME%\zpm directory:
LM.Detection_x64.exe or LM.Detection.exe /ErrorStdOut /registry /loglevel 4 /e /g 038B7343-567A-489C-9A7B-99359061B585
"/g" is guid of the patch.
- Once the patch has run on the device
there will be a corresponding log file at the root of
- Confirm that the registry key under NativeScan is re-populated by the scan.
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:21-MAY-18
- NovellZENworks Patch Management
Did this document solve your problem? Provide Feedback