![]() var/opt/BESClient/_BESData/_Global/measure.log var/opt/BESServer/GatherDBData/GatherDB.log If the BESAdmin.exe command is run from within a Fixlet, for example the Fixlet running the upgrade, it logs into the %LOCALAPPDATA% of the LocalSystem user (for example C:\Windows\System32\config\systemprofile\AppData\Local) because that is the user running the client service triggered by the Fixlet action.Ĭ:\Program Files (x86)\BigFix Enterprise\BES Server\BESRelay.logĬ:\Program Files (x86)\BigFix Enterprise\BES Server\FillDBData\FillDB.logĬ:\Program Files (x86)\BigFix Enterprise\BES Server\GatherDBData\GatherDB.logĬ:\Program Files (x86)\BigFix Enterprise\BES Server\DownloadPlugins\\logsĬ:\Program Files (x86)\BigFix Enterprise\BES Server\Applications\LogsĬ:\Program Files (x86)\BigFix Enterprise\BES Server\Applications\Ĭ:\Program Files (x86)\BigFix Enterprise\BES Server\server_audit.logĬ:\Program Files (x86)\BigFix Enterprise\BES WebUI\WebUI\logs ![]() If the BESAdmin command is run manually, it logs into the user directory of the current user (for example C:\Users\Administrator\AppData\Local\BigFix\BESAdminDebugOut.txt). ![]() Note: The %LOCALAPPDATA% depends on the user running the BESAdmin.exe command. %LOCALAPPDATA%\BigFix\BESAdminDebugOut.txt Common file locations for BigFix on various operating systems:Ĭ:\Program Files\BigFix Enterprise\BES Client\_BESData\_Global\LogsĬ:\Program Files\BigFix Enterprise\BES ClientĬ:\Program Files\BigFix Enterprise\BES Console\QnAĬ:\Program Files\BigFix Enterprise\BES Client\actionsite.afxmĬ:\Program Files (x86)\BigFix Enterprise\BES Relay\logfile.txt ![]()
0 Comments
Leave a Reply. |