Agent Install Log or Upgrade Log Locations

Products

• Carbon Black App Control (formerly Cb Protection)

Issue/Introduction

Where is the default location of an Agent install log or upgrade log?

Environment

• App Control Agent: All Supported Versions
• Microsoft Windows: All supported Versions 
• macOS: All Supported Versions
• Linux: All Supported Versions

Resolution

Windows

• During manual upgrade or install the log location is part of the command used, examples:

  msiexec.exe /i C:\Temp\PolicyInstaller.msi /L*v C:\Temp\DebugInstall.log

• Active upgrades or installs may also contain a temporary log located in the user's temp folder:

  C:\Users\<USR>\AppData\Local\Temp\<GUID>\msi<GUID>.log

• Whenever an upgrade is attempted via the Console (even if unsuccessful), the log will be included in:

  C:\ProgramData\Bit9\ParityAgent\Logs\ParityHostAgentInstall_TIMESTAMP.log

• After any successful install or upgrade a copy is included in the ProgramData directory:

  Install: C:\ProgramData\Bit9\ParityAgent\Logs\Install_VERSION_TIMESTAMP.log
  Upgrade: C:\ProgramData\Bit9\ParityAgent\Logs\ParityHostAgent_TIMESTAMP.log

• These paths differ slightly when installed on Windows XP or Windows Server 2003:

  During install or manual upgrade:
  C:\Documents and Settings\<USR>\Local Settings\Temp\<GUID>\msi<GUID>.log
  
  After successful install:
  C:\Documents and Settings\All Users\Application Data\Bit9\Parity Agent\Logs\Install_VERSION.log
  
  Upgrade:
  C:\Documents and Settings\All Users\Application Data\Bit9\Parity Agent\Logs\ParityHostAgentInstall_TIMESTAMP.log

Linux

• During install or upgrade:

  /var/log/.B9_DEBUG_INSTALL

• After successful install or upgrade these are moved to:

  /srv/bit9/data/Logs/

macOS

Agent installation and upgrade is done via pkg and the pkg installation logs are included in the file:

/private/var/log/install.log