Log and trace files

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:

Table 1. Files for deployment failure problem determination
Filename	Path	Scenario
`peresult.ini` `pegrid.ini.update` `rbagent.trc` `osresult.ini` `osgrid.ini.update`	`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.
`peresult.ini` `pegrid.ini.update` `rbagent.trc` `osresult.ini` `osgrid.ini.update`	`C:\Deploy\$OEM$\BigFixOSD\RBAgent` on target workstation for reimaging	`C:\Deploy\$OEM$\BigFixOSD\RBAgent` on target workstation for reimaging
`bomnn-peresults.ini` `bomnn-pegrid.ini.update` `bomnn.trc` `bomnn-osresult.ini` `bomnn-osgrid.ini.update`	`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 (Windows Bundle scripts, OS Resources, WIM and WinPE)	`C:\mcastdownload` on the target workstation for reimaging.	Reimaging in multicast has failed.
`mcastdownload.log` `validateBMserver.log`	`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

During the reimaging process and during Bare Metal deployments, errors can occur when Windows Setup is installing and configuring the new operating system. To troubleshoot errors occurring during the Windows Setup phase, check the following log files in these locations:

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

To troubleshoot errors occurring during deployments on Linux systems, check the log files in this location:

/var/opt/BESClient/__BESClient/__Global/logs/DeploymentLogs

Files:

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.

Files for troubleshooting Console errors while importing files

When you import files using the Console (for example, when you upload an Windows Bundle, images, or drivers) all temporary files and logs used during the import process are stored in the Console working directory:

%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

If errors occur during deployment media creation, you can check the following 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 and rbagent.trc files under %ProgramFiles%\BigFix OSD.
For Example:
```
C:\Program Files\BigFix OSD
```
on the selected target machine.
If the selected target is not an OS Deployment Server, look at the rbagent.log and rbagent.trc files under <IEM Client>\_BESData\actionsite\_Download
For example:
```
C:\Program Files\BigFixEnterprise\BESClient>\_BESData\actionsite\_Download
```
on the selected target machine.

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=..

The following list provides details on the most frequent JoinDomain errors:

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

If client settings that were specified in a Bare Metal Profile deployed on a target are not correctly set, you can check the following file on the target system for the probable cause:

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. The Relay Downloader submits its request for a file to the BigFix relay through an url in an http connection. It is important to note that the download path follows the complete relay hierarchy in the BigFix infrastructure. Command usage:

RelayDownloader -r <relay url> [-p <port>] -f <file> -t <timeout(m)>

Table 2. Command parameter description
Parameter	Description
-r	Name of relay from which to download files through
-p	Port on relay which is used for BigFix traffic (Optional Default:52311)
-f	File containing downloads on each line with size, sha1, url separated by <tab>
-s	Sha1 of the file to individually download if not using the "-f" parameter
-q	Sha2 of the file to individually download if not using the "-f" parameter
-z	Size of the file to individually download if not using the "-f" parameter
-u	URL of the file to individually download if not using the "-f" parameter
-l	Log file to write
-d	Verbose debug logging
-o	Directory to save downloads to
-t	Amount of time in minutes to quit if download does not become available (Default: 60)

RelayDownloader SUCCESSFUL EXAMPLE:

A <NOT> Copying tem://bfsrv.osd.net:52311/Uploads/2363642e1992c04d57e38366d99ba2afe0c7f23d/2363642E1992C04D57E38366D99BA2AFE0C7F23Dpkg.BFOSD/2363642E1992C04D57E38366D99BA2AFE0C7F23D|9494|D56006C721D5CD452A2787BC6B00B6A331E0D647876F97239F8E652C318EB931/2363642E1992C04D57E38366D99BA2AFE0C7F23Dpkg.BFOSD to local://temp/tpm_ED33DECBED674649_1/ISO/.TPMfOSd/global/tem/drivers/2363642E1992C04D57E38366D99BA2AFE0C7F23Dpkg.BFOSD (133/805..) About to execute: cmd.exe /c RelayDownloader64.exe -r 10.10.50.66 -p 52311 -u "http://temsrv.osd.net:52311/Uploads/2363642e1992c04d57e38366d99ba2afe0c7f23d/2363642E1992C04D57E38366D99BA2AFE0C7F23Dpkg.BFOSD" -z 9494 -s 2363642E1992C04D57E38366D99BA2AFE0C7F23D -q D56006C721D5CD452A2787BC6B00B6A331E0D647876F97239F8E652C318EB931 -t 10 -o "C:\windows\TEMP\osdtemcache\D56006C721D5CD452A2787BC6B00B6A331E0D647876F97239F8E652C318EB931" && ren "C:\windows\TEMP\osdtemcache\D56006C721D5CD452A2787BC6B00B6A331E0D647876F97239F8E652C318EB931\2363642E1992C04D57E38366D99BA2AFE0C7F23Dpkg.BFOSD" "2363642E1992C04D57E38366D99BA2AFE0C7F23Dpkg.BFOSD" A <NOT> Copying tem://temsrv.osd.net:52311/Uploads/23b56e7b4c7a6ecc3e2c7a4088cd68f44ea557da/23B56E7B4C7A6ECC3E2C7A4088CD68F44EA557DApkg.BFOSD/23B56E7B4C7A6ECC3E2C7A4088CD68F44EA557DA|227372|469EBA978F879A78C5B5ED66D6A695BA1D6951E9E088926E2316798A55BAB8C8/23B56E7B4C7A6ECC3E2C7A4088CD68F44EA557DApkg.BFOSD to local://temp/tpm_ED33DECBED674649_1/ISO/.TPMfOSd/global/tem/drivers/23B56E7B4C7A6ECC3E2C7A4088CD68F44EA557DApkg.BFOSD (134/805..)

RelayDownloader ERROR EXAMPLE:

A <NOT> Copying tem://temsrv.osd.net:52311/Uploads/37039fc3d5be61c6473fd532c6fb58d5b205d1ff/37039FC3D5BE61C6473FD532C6FB58D5B205D1FFpkg.BFOSD/37039FC3D5BE61C6473FD532C6FB58D5B205D1FF|462500015|1F0D84A4270F2563238CD71D11E16032636EFB9BED9C12B1B7A6F146E96AFA44/37039FC3D5BE61C6473FD532C6FB58D5B205D1FFpkg.BFOSD to local://temp/tpm_ED33DECBED674649_1/ISO/.TPMfOSd/global/tem/drivers/37039FC3D5BE61C6473FD532C6FB58D5B205D1FFpkg.BFOSD (76/120..) About to execute: cmd.exe /c RelayDownloader64.exe -r 10.10.50.66 -p 52311 -u "http://temsrv.osd.net:52311/Uploads/37039fc3d5be61c6473fd532c6fb58d5b205d1ff/37039FC3D5BE61C6473FD532C6FB58D5B205D1FFpkg.BFOSD" -z 462500015 -s 37039FC3D5BE61C6473FD532C6FB58D5B205D1FF -q 1F0D84A4270F2563238CD71D11E16032636EFB9BED9C12B1B7A6F146E96AFA44 -t 60 -o "C:\windows\TEMP\osdtemcache\1F0D84A4270F2563238CD71D11E16032636EFB9BED9C12B1B7A6F146E96AFA44" && ren "C:\windows\TEMP\osdtemcache\1F0D84A4270F2563238CD71D11E16032636EFB9BED9C12B1B7A6F146E96AFA44\37039FC3D5BE61C6473FD532C6FB58D5B205D1FFpkg.BFOSD" "37039FC3D5BE61C6473FD532C6FB58D5B205D1FFpkg.BFOSD" notice: cannot open source file in uicopy A <ERR> A <ERR> A <ERR> A <WRN> (called from GeneratesWinPECD (load.rbc:12314)) A <WRN> (called from RAD_makewpeiso (load.rbc:12960)) A <WRN> (called from AgentDispatch (rbagent.rbc:4387)) A <WRN> (called from --toplevel-- (rbagent.rbc:4814)) A <ERR> A <ERR> A <WRN> (called from RAD_makewpeiso (load.rbc:12960)) A <WRN> (called from AgentDispatch (rbagent.rbc:4387)) A <WRN> (called from --toplevel-- (rbagent.rbc:4814)) A <INF> WinPE media creation has failed! A <ERR> A <ERR> Stopping Web extension Command error: No such file or directory, 1F0D84A4270F2563238CD71D11E16032636EFB9BED9C12B1B7A6F146E96AFA44 Error raised by CopyFile in utils.rbc, line 2966 [TMF:817] No such file or directory (1F0D84A4270F2563238CD71D11E16032636EFB9BED9C12B1B7A6F146E96AFA44) Error raised by GeneratesWinPECD in load.rbc, line 12381 [UFI:3038] Unknown error (Error when injecting items into WinPE deployment engine) Command error: Unknown error RbAgent command rad-makewpeiso has failed [AGT:4394]

The error displayed above is a typical error that occurs when the tool was not able to download the required file. In general, this error indicates that the timeout was reached. The default is 60 minutes or 10 minutes and can be retrieved by reading the -t option of the command. A timeout error occurs frequently because the download request didn't complete in the BigFix infrastructure. Considering that it is processed through the Relay chain, the error could be due to the last Relays that did not receive the file before the timeout period elapsed.

OFFLINE MEDIA CREATION CASE:

An offline media creation involves one or two machines. The Media creator machine, where the output (file, folder or the usb key) has to be created, and the Bare Metal Server machine that provides the required drivers and images. But the media creation can also be completed using the Bare Metal Server machine only, if it is also a Media creator machine. Note that the RelayDownloader runs on the Media creator machine.
When the file is downloaded it is stored in a cache folder, %TEMP%\osdtemcache, where %TEMP% is the system temporary directory. This path can be customized by adding a system variable named TEMCACHE or changing the system variable TEMP.

Generic steps for troubleshooting RelayDownloader issues:

Verify that you can download the file using the link in the RelayDownloader command (-u option) using a browser on the machine where the Relaydownloader is running. In case of media creation, it is the Windows Bundle creator machine. Considering the error example reported above, the url is: http://temsrv.osd.net:52311/Uploads/37039fc3d5be61c6473fd532c6fb58d5b205d1ff/37039FC3D5BE61C6473FD532C6FB58D5B205D1FFpkg.BFOSD
This step can be completed only if the machine where the RelayDownloader runs can connect to the BigFix root server.
Check the disk space available on the machine where the RelayDownloader is running and on each Relay in the hierarchy chain starting from the BigFix server.
Check if the file exists on the BigFix server and, if needed, on each Relay down the hierarchy that affects the machine where the RelayDownloader is running. Considering the error example reported above, the name to look for is: 37039FC3D5BE61C6473FD532C6FB58D5B205D1FFpkg.BFOSD
On each BES RELAY: must exist the file ...\BES Relay\wwwrootbes\bfmirror\downloads\sha1\37039FC3D5BE61C6473FD532C6FB58D5B205D1FF On the BES SERVER: must exist the folder ...\BES Server\wwwrootbes\Uploads\37039FC3D5BE61C6473FD532C6FB58D5B205D1FF and inside must exist the file 37039FC3D5BE61C6473FD532C6FB58D5B205D1FFpkg.BFOSD and, the file ...\BES SERVER\wwwrootbes\bfmirrow\downloads\sha1\37039FC3D5BE61C6473FD532C6FB58D5B205D1FF
As already mentioned, the Relaydownloader command caches the downloaded files locally in the directory %TEMP%\osdtemcache. If the space is insufficient in that partition, you can set the SYSTEM variable TEMCACHE to change it to a different partition. So, considering the error, it is important to check if the folder %TEMP%\osdtemcache\1F0D84A4270F2563238CD71D11E16032636EFB9BED9C12B1B7A6F146E96AFA44 exists or if the variable TEMCACHE is set in the system variables to a specific value reading the output of the command SET.
Related to the error described above, you must rerun the command that failed, and if it fails again, send the command output to the support team for further analysis. The command used here is only an example. The real command can be obtained only from the log file messages.
RelayDownloader64.exe -r 10.10.50.66 -p 52311 -u "http://temsrv.osd.net:52311/Uploads/37039fc3d5be61c6473fd532c6fb58d5b205d1ff/37039FC3D5BE61C6473FD532C6FB58D5B205D1FFpkg.BFOSD" -z 462500015 -s 37039FC3D5BE61C6473FD532C6FB58D5B205D1FF -q 1F0D84A4270F2563238CD71D11E16032636EFB9BED9C12B1B7A6F146E96AFA44 -t 60 -o "C:\windows\TEMP\osdtemcache\1F0D84A4270F2563238CD71D11E16032636EFB9BED9C12B1B7A6F146E96AFA44
At the end of the command you can add the -V option to log messages in Verbose mode.
The Relaydownloader timeout can be increased setting a system variable on the machine where the Relaydownloader runs. Then the same scenario sequence must be rerun.
1. Open the <System Properties> panel on the system machine where the Relaydownloader runs.
2. Click <Environment Variables...>.
3. In the lower section of the panel called System Variables, click on <new>.
4. In the variable name field write: TEM_RELAY_DOWNLOADER_TIMEOUT. For example, in the variable value field write 120 to set it to 120 minutes.
5. click OK.
6. Restart your local BES Client service.
If the RelayDownloader command continues to fail, considering that it runs a command equivalent to a prefetch command, to understand if there is an issue in the infrastructure and to provide elements to the BigFix platform engineers, we suggest to run a Fixlet that runs the prefetch of the same file. The Fixlet must be run on a BES client connected to the Bare Metal server and not on the Bare Metal server itself.
Starting from the Relaydownloader command that failed, and considering that, in the Relaydownloader command, the -z option report the size, the -s option reports the sha1, and the -q option reports the sha2, the Fixlet, for this example, can be written as
<?xml version="1.0" encoding="UTF-8"?> < BES xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="BES.xsd"> <SingleAction> <Title>RelaydownloaderPrefetch</Title> <Relevance><![CDATA[true]]></Relevance> <ActionScript MIMEType="application/x-Fixlet-Windows-Shell">prefetch 37039FC3D5BE61C6473FD532C6FB58D5B205D1FFpkg.BFOSD sha1:37039FC3D5BE61C6473FD532C6FB58D5B205D1FF size:462500015 http://temsrv.osd.net:52311/Uploads/37039fc3d5be61c6473fd532c6fb58d5b205d1ff/37039FC3D5BE61C6473FD532C6FB58D5B205D1FFpkg.BFOSD sha256:1F0D84A4270F2563238CD71D11E16032636EFB9BED9C12B1B7A6F146E96AFA44 </ActionScript> <SuccessCriteria ... ... ... </SingleAction> </BES>

Troubleshooting problems in retrieving Bare Metal Server Settings (Analysis 50 or Task 361)

Analysis 50 and Task 361 are used to retrieve current parameter settings for the Bare Metal servers so that they can be viewed and changed either from the Bare Metal Server Manager dashboard or by running Task 361. When there are problems, and the parameters cannot be retrieved, you can check the following files on the Bare Metal Server:

\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.

Troubleshooting Windows Capture Errors

The Windows Capture action is marked as Completed once the preparation phase finishes, but the actual capture process occurs afterward. If the action is completed but no files appear in the network share within a reasonable amount of time, check the target computer for a red error panel indicating a failed step (visible only if running in WinPE or if you are logged in to Windows OS as an administrator).

If the red error panel is displayed, you must click OK on it to close the task. Afterward, check the failure logs located in \Windows\Temp\DeploymentLogs and/or \MININT\SMSOSD\OSDLOGS. While these are usually on the C: drive in Windows, the drive letter in WinPE depends on partition mapping (often C:, D:, or E:).

Testing WinPE drivers

How to verify if a network or disk driver is applicable to a specific machine model in Windows PE?

When WindowsPE starts on the target, interrupt the process by typing Ctrl-C in the DOS shell.
Check your WindowsPE version by issuing the ver command.
If you are testing a driver that you injected offline, locate the .inf file by using the dir /s /b command.
If you are testing a driver you injected online using the Deployment Engine binding grid, it is stored in the x:\builtindrv folder after initialization completes.
If you are testing a driver that has not been injected yet, connect your USB/DVD device.
Verify that the driver can be loaded successfully by the drvload.exe command.
Check that you can see the network or your disk by issuing ipconfig /all for the network or diskpart >list disk for the disk.
Once you have identified the correct driver, bind it on the BigFix console > OSD Dashboards > Driver Library > Bindings.