Reference logs for BigFix Patch for Windows

When a Fixlet fails or a bug is reported, the BigFix Support team requires specific logs to identify the root cause. Follow the procedures below based on the type of patch being deployed.

BigFix Client Logs

BigFix Client log records the deployment details about BigFix client.

  • Default Path:
    <BigFix Installation Path>\BigFix Enterprise\BES
          Client\__BESData\__Global\Logs
    For example: 
    C:\Program Files (x86)\BigFix Enterprise\BESClient\__BESData\__Global\Logs

Patch Installation Logs

When providing installation logs, it is necessary to get the right type of installation log.
.msu
A common type of Windows kernel patch. For example, Patch in Fixlet ID 1513249 for Windows 7 SP1.
How to get the msu log
  1. Restart the target machine. Manually execute the patch by double clicking it. Take note of the message shown in the popup and take note of the date and time on the machine.
  2. Right after step 1, open C:\Windows\Logs\CBS folder. Get the three most recent files, based on the date modified. The latest file should be a CBS.log and there should be a few files named similar to CbsPersist_20141117123039.cab.
  3. Export again the registry key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing]
.msp
A common type of Windows Application patch. For example, Patch in Fixlet ID 1512887 for Lync 2010. Some .msp logs can help to gather the installation logs.
How to get the .msp log
  1. Run the patch from the Command Prompt using the /log switch. For example, patchname.exe /log:C:\patchname.install.log.
  2. After the log file is generated:

    • Attach the file C:\patchname.install.log

    • Include any other .log files generated under C:\.

      These logs will help Support analyze the installation behavior.
How to get the .msp log (advanced)
Ask the user to manually run the patch on the target machine. Gather the installation log using the information description in the following KB page:https://support.microsoft.com/en-us/kb/884290.
.msi
A common type of Windows Application patch. For example, Patch in Fixlet ID 1512887 for Lync 2010. Some .msp logs can help to gather the installation logs.
How to get the .msi log
To get the log, use the following in cmd: 
msiexec /l*vx patch name.msi
.exe
A common type of Windows Application patch. For example, Patch in Fixlet ID 311442701 for Office.
How to get the .exe log
Run the patch from Command Prompt using the /log switch. For example, 
patchname.exe /log C:\patchname.log
After the log file is generated:
  • Attach patchname.log (or .html log if generated)
  • Include any additional log files created during the installation process.