DPDTrace GUI Tool: Used to troubleshoot patch detection issues in Endpoint Manager (formerly LDMS)

Version 9

    Verified Product Versions

    Endpoint Manager 2017.xEndpoint Manager 2018.x


    Please read this disclaimer before using this tool:  LANDESK Share IT Disclaimer




    We created a GUI tool to simplify diagnostic scanning to troubleshoot patch scan issues.


    The DPDTrace GUI interface requires .Net 2.0 or greater to work.


    How to use the DPDTrace GUI


    1. Download the latest version of the DPDTrace GUI (See attached file at the bottom of this document)
    2. Extract the DPDTrace.zip to the desktop of the machine you will scan from.  This can be on a server remote to the target machine or on the target machine itself.  Support may specify where to scan from depending on the issue being diagnosed.
    3. Open the DPDTrace GUI by double-clicking DPDTraceGUI.exe from the extracted folder.


    4. Choose Local to scan the local machine. The IP address or the Machine Name of the local machine will automatically populate.    

    5. Choose Remote to scan a remote machine. You will need to provide a valid Machine Name or IP Address to scan.    

    6. Enter a username with administrator access to the target machine.        

          a. The format must be DomainName\UserName or MachineName\UserName depending on how you are authenticating to the target machine.    

    7. Enter a valid Password. You can choose to un-check the Hide option if you wish to see your password for troubleshooting purposes.


    OEM Version: (EPM Customers)


    8. Choose the OEM scan engine version  9.3.2644 to be used during the scan.


    Patch Type:


    9. Choose Patch Type to be used during the scan.

              a. We highly suggest leaving the defaults of Security Patches and Non-Security Patches selected unless a support tech requests a change.


    10. Click Run to start the scan.


    The DPDTrace GUI tool will automatically download the latest data files  (WindowsPatchData.zip).

    If your machine does not have internet connectivity or a proxy is blocking the downloads, you will need to manually download the data files and place them in the DataFiles folder in the extracted DPDTrace folder on the desktop.



    11. You will see Command Prompt popups and popups for the Rename HF.Log utility during the scan process.  Do not close either these.



    12. All popup windows will close and a new popup will occur once the scan is complete.  Click OK.


    13. The scan diagnostic is complete and all of the trace logs, scan outputs and registry exports have been zipped to this folder:  C:\Users\UserName\Desktop\DPDTrace\SendToSupport

              a. The zip file will be named HFCLi_YearMonthDay.zip


    14. Provide this zip files to support!  If you have any issues attaching this zip to the case, please let the support tech know so they can provide you with more options.


    Additional Information


    A command line DPDTrace tool can be used by customers who cannot run this GUI version:  DPDTrace command line logging tool used for patch detection issues