How To: Run a Diagnostic Patch Scan When Unable to Perform a DPDTrace

Version 5



    The purpose of this document is to instruct how to run a diagnostic patch scan when you are unable to perform a DPDTrace for a detection issue.





    1. Go to Tools > Options > Logging in your console and set the Logging Levels to "All" and check the "Diagnostic patch scanning" checkbox.
      Note as the message below the Diagnostic option says, you should only turn this option on at the request of Support.


      2. Save your changes and select to restart the service now then close your console, then stop the Ivanti Patch for Windows Servers Console Service.



       3. Go to C:\ProgramData\LANDESK\Shavlik Protect\Logs and delete or move the contents of the directory.



      4. Restart the console service from step 2 and then open your console and scan the machine that Support has requested the diagnostic scan for using the scan template that Support specifies. For instance, if the problem patch on the machine is a security patch, you would use the security patch scan template.

    Scan Results.PNG


       5. Save a screenshot of your scan results (similar to the screenshot above showing the machine name, definition date, scan template, Bulletin ID, and Qnumber of the patch having the issue).


       6. Go to Tools > Options > Logging and uncheck the Diagnostic Patch scanning checkbox and save your changes.


       7. Zip up the contents of the C:\ProgramData\LANDESK\Shavlik Protect\Logs folder.


       8. Send the zipped Logs folder from step 7 and the screenshot from step 5 to Support.



    Additional Information


    You will still need to obtain Registry Exports from the problem client machine to send to Support along with the Diagnostic Patch Scan or DPDTrace. You will find instructions for obtaining these Registry Exports here Batch File for Obtaining Registry Exports for Detection Related Issues



    Affected Products


    Ivanti Patch for Windows Servers 9.3