Check Point HARMONY R81 Administration Manual page 223

Use an external USB device to collect the Pre-boot data. The device must have at least 128
MB of free space, and sufficient storage for the output cab file. CPinfoPreboot cannot run
on boot media prepared with the Full Disk Encryption filter driver
To collect Pre-boot data:
1. Copy CPinfoPreboot.exe to an external USB device.
2. Boot the client from the USB device.
Note - Microsoft Windows does not automatically detect USB devices after
boot up. The USB device must be connected while booting the computer.
3. Open the command prompt and type: <path to CPinfoPreboot>
<CPinfoPreboot.exe <output cap filename> <output folder name>.
For example: C:\path\>CPinfoPreboot.exe SR1234 temp.
4. CPinfoPreboot stores the output file to the designated folder.
n If no output name is specified, the output file has the same name as the output
folder.
n If no output folder is specified, CPinfoPreboot saves the output file to the
working directory on the external media. An output folder is required if the
working directory is on read-only media.
Debug Logs Collected by CPinfo and CPinfoPreboot
You can use the debug logs to examine the deployment phase or problems that occur. The
information there is included in CPinfopreboot. Send the full results of CPinfopreboot
to Check Point Technical Support for analysis.
The client debug log file is on the user's Endpoint Security client computer (for Windows 7
and higher) at:
C:\ProgramData\CheckPoint\Endpoint Security\Full Disk Encryption
The log file name is dlog1.txt. For BitLocker it is called Win_Nem.log. For an
explanation of the error messages that can show in Win_Nem.log, see sk157995.
Pre-boot Issues
Note - Pre-boot issues are not relevant for BitLocker-encrypted computers
Mouse or Keyboard Trouble
Troubleshooting Full Disk Encryption
R81 Harmony Endpoint Server Administration Guide | 223