Log and trace files
When problems occur, you can determine what went wrong by viewing messages in the appropriate log files which provide information about how to correct errors.
Files for troubleshooting deployment failures on Windows targets
When a deployment fails you can troubleshoot the problem by analyzing the following files depending on the scenario you are running:
Filename | Path | Scenario |
---|---|---|
|
C:\Program Files\BigFix Enterprise\BES
Client\__BESData\__Global\Logs\OSDeploymentLogs\OSDeploymentBindingGrids on target
workstation |
Reimage was successful but drivers were missing in the new operating system. You can find Windows PE binding grid in the specified location. |
|
C:\Deploy\$OEM$\BigFixOSD\RBAgent on target
workstation for reimaging |
C:\Deploy\$OEM$\BigFixOSD\RBAgent on target
workstation for reimaging |
|
C:\BFOSD Files\global\hostactitiestasknnnnn on
relay server for bare metal |
Bare metal jobs have failed. You can find the generated driver binding grid on the endpoint in the specified location. |
OSD Log files | C:\BFOSD Files\logs on relay server
for bare metal |
OSD PXE component logs |
All deployment files (MDT, OS Resources, WIM and WinPE) | C:\mcastdownload on the target
workstation for reimaging. |
Reimaging in multicast has failed. |
|
C:\Program Files\BigFix Enterprise\BES
Client\__BESData\__Global\Logs\OSDeploymentLogs\McastDownload on the target
workstation after reimaging. |
Reimaging in multicast (reimage profile) was successful. These logs contain statistical information about the files downloaded during the deployment and about the validation completed by the relay/Bare Metal Server to which the target is connected. You can also view if the deployment was switched to unicast mode. |
Files for problem determination during Windows setup
C:\Windows\Panther
C:\Windows\Panther\setuperr.log
C:\Windows\Panther\miglog.xml
C:\Windows\Panther\PreGatherPnPList.log
C:\Windows\setupact.log
C:\Windows\setuperr.log
C:\WINDOWS\INF\setupapi.dev.log
C:\WINDOWS\INF\setupapi.app.log
C:\WINDOWS\Performance\Winsat\winsat.log
Files for problem determination during Linux deployments
/var/opt/BESClient/__BESClient/__Global/logs/DeploymentLogs
cleanupbesclientcache.log
instpostscript.log
instpostscriptnochroot.log
instprescript.log
limunpack.log
patchlinuxconf.log
prepareimageprovider.log
setlinuxboot.log
testlinuxboot.log
Depending on the type of deployment, some of these files
may not be available.For more information about troubleshooting reimaging process failures, see the BigFix wiki page: Re-Image Process
Files for troubleshooting Console errors while importing files
%USERPROFILE%\OSDeployment
If
any errors occur during the import step, you can troubleshoot the
problem by analyzing the general trace file %USERPROFILE%\OSDeployment\rbagent.trc.All files being uploaded are tracked in the %USERPROFILE%\OSDeployment\UploadManagerFiles folder.
Deployment media creation problem determination files
- From the BigFix Console,
check the
GenerateDeploymentMedia
Action Info that was executed on the selected target. - If the selected target is an OS Deployment Server look at the
rbagent.log
andrbagent.trc
files under %ProgramFiles%\BigFix OSD.For Example:on the selected target machine.C:\Program Files\BigFix OSD
- If the selected target is not an OS Deployment Server, look at
the
rbagent.log
andrbagent.trc
files under <IEM Client>\_BESData\actionsite\_DownloadFor example:on the selected target machine.C:\Program Files\BigFixEnterprise\BESClient>\_BESData\actionsite\_Download
Troubleshooting JoinDomain errors during Bare Metal and reimaging deployments
Failures
that occur when joining targets to domains are not unrecoverable errors.
The deployment completes successfully. If the target fails to join
the domain, you can determine the cause of the problem by looking
in the c:\Windows\Temp|Deployment Logs\ZTIDomainJoin.log file
and searching for the string
.RC=
.
Case 2 Explanation = "Missing OU"
Case 5 Explanation = "Access denied"
Case 53 Explanation = "Network path not found"
Case 87 Explanation = "Parameter incorrect"
Case 254 Explanation = "The specified extended attribute name
was invalid."
-> probably the specified OU (organizational Unit) parameter
is incorrect or OU doesn't exist
Case 1326 Explanation = "Logon failure, user or pass"
Case 1355 Explanation = "The specified domain either does not exist or could not
be contacted."
-> probably there is a DHCP/DNS configuration error
Case 1909 Explanation = "User account locked out"
Case 2224 Explanation = "Computer Account allready exists"
Case 2691 Explanation = "Allready joined"
For more information about error codes, see https://msdn.microsoft.com/en-us/library/ms681381(v=vs.85).aspx.
Troubleshooting Client settings problems after a Bare Metal deployment
C:\Windows\temp\...\BFCloseBareMetalTask.log
Troubleshooting RelayDownloader errors
The RelayDownloader tool is used to retrieve files from the BigFix server, for example during the creation of deployment media or for Bare Metal Deployments. For tips about troubleshooting RelayDownloader errors, see the BigFix wiki at this link: RelayDownloader Troubleshooting Tips.
Troubleshooting problems in retrieving Bare Metal Server Settings (Analysis 50 or Task 361)
\global\tem\baremetalsettings.conf
is the file where the settings are stored.C:\Program Files\BigFix OSD\rbagent.trc
If the configuration file does not exist or is invalid, the rbagent.trc file logs any errors to help you troubleshoot the problem.