The ProfileUnity Diagnostic Tool collects log files and system information from a client machine into a single zip file that can be sent to Liquidware Technical Support. This article covers how to run the tool on a standard ProfileUnity client machine, on other machines such as the FlexApp Packaging Console, and how to scrub sensitive data from the results before sending.
ℹ️ Set logging to Debug before running
To capture the most detailed diagnostic information, set the client logging level to Debug before logging on to the machine. See: How to Change Enhanced Client Logging to Debug Mode
Running the Diagnostic Tool on a ProfileUnity Client Machine
Follow these steps on the endpoint where the issue is occurring.
-
Log in to a ProfileUnity client machine and run the diagnostic tool. Do NOT run as Administrator.
C:\Program Files\ProfileUnity\Client.NET\LwL.ProfileUnity.Client.Diagnostic.exe -
After the tool finishes, a zip file will be created in %temp% with the following name pattern:
%temp%\LwL_ProfileUnity_Client_Diagnostic_*.zipVersions prior to 6.8.3
The diagnostic bundle is created in C:\Program Files\ProfileUnity\Client.NET instead of %temp%. -
If you need the latest version of the diagnostic tool, download it from:
https://cdn.liquidware.com/support/DiagTool.zip -
Send the zip file LwL_ProfileUnity_Client_Diagnostic_*.zip to the support engineer assigned to your case.
If the file contains sensitive data that needs to be removed before sending, follow the steps in the Scrubbing Sensitive Data section below.
Running the Diagnostic Tool on Other Machines
The diagnostic tool can also be run on machines that are not standard ProfileUnity client endpoints, such as the FlexApp Packaging Console or a FlexApp Packaging Automation server.
When running the diagnostic tool from any location other than C:\Program Files\ProfileUnity\Client.NET, it must be run as Administrator to capture all data. If the current user is not an administrator, run it once normally and once using Run as Administrator with alternate admin credentials if possible.
-
The latest diagnostic tool is always available for download at:
https://cdn.liquidware.com/support/DiagTool.zip -
FlexApp Packaging Console (6.8.6 and later)
Starting in ProfileUnity 6.8.6, the diagnostic tool is included with the FPC at:
C:\Program Files (x86)\Liquidware Labs\FlexApp Packaging Console\LwL.ProfileUnity.Client.Diagnostic.exe -
FlexApp Packaging Automation (version 1.5 and later)
Starting in version 1.5, the diagnostic tool is included with the Packaging Automation framework at:
C:\Program Files (x86)\Liquidware Labs\FlexApp Packaging Automation\punc\LwL.ProfileUnity.Client.Diagnostic.exe
If you are in a government or restricted network environment and cannot send diagnostic data externally, please contact your Liquidware support engineer to discuss alternative collection or transfer methods before running the tool.
Scrubbing Sensitive Data (Optional)
In certain situations the diagnostic results may contain sensitive or classified information such as usernames, server names, or IP addresses that must be removed before the file can be shared with Liquidware Support. Follow the steps below to scrub the data using a text editor such as Notepad++.
Instead of replacing all sensitive data with a generic label like “Scrubbed”, use distinguishable placeholders such as ProUServer1, VMwareCS2, or ServerIP1. This helps the support engineer understand the structure of your environment without exposing sensitive details.
- Extract the zipped diagnostic results file to a local folder.
- Open all extracted files in Notepad++ (or a comparable text editor that supports multi-file find and replace).
- Use Find and Replace (Ctrl+H in Notepad++) to search for and replace sensitive values. Enable the option Replace All in All Opened Documents to apply changes across every file at once.
- After scrubbing all files, use Save All to save every file.
- Zip the scrubbed files and send the zip to the support engineer assigned to your case.