Log files

Platform	Logpath
1E Client logs on Windows	%ALLUSERSPROFILE%\1E\Client\1E.Client.log (used by 1E Client and 1E features, and Shopping client) %ALLUSERSPROFILE%\1E\Client\NomadBranchUninstall-YYYY_MM_HHTMM_HH_SS_000Z.log
1E Client logs on macOS	/Library/Logs/1E.Client.Daemon.log (shows any service start errors) /Library/Logs/1E.Client.log (shows the current operation of the 1E Client)
1E Client logs on other non-Windows platforms	/var/log/1E/Client/1E.Client.log
Nomad client log	%ALLUSERSPROFILE%\1E\NomadBranch\LogFiles\NomadBranch.log
PXE Everywhere Agent log	%ALLUSERSPROFILE%\1E\PXEEverywhere\PXEEverywhere.log
Shopping client log	%ALLUSERSPROFILE%\1E\Client\Shopping.log
WakeUp client log	%ALLUSERSPROFILE%\1E\Agent\WakeUpAgt.log By default, Windows resolves %ALLUSERSPROFILE% as C:\ProgramData\

Configuration

1E Client log:

The LogPath setting is stored in the 1E.Client.Conf file and determines the full path and filename of the 1E Client log file.

The 1E Client log is shared by:

• 1E Client.

• 1E client features.

• Shopping client module (only available on Windows OS).

To change the logging level, please refer to LoggingLevel in the 1E.Client.CONF file.

The following are not configurable in this version:

• Maximum size of 5MB

• 5 rollover files numbered 1 (newest) to 5 (oldest) with the rollover number included as n.log

Nomad client log:

LogFileName registry is configurable using MODULE.NOMAD.LOGPATH and MODULE.NOMAD.LOGNAME installer properties.

• MaxLogFileSize is configurable using MODULE.NOMAD.MAXLOGSIZE. Default is 5242880 (5MB).

• When the log file reaches its maximum size, it is renamed with a .LO_ extension and a new .LOG file is created. The .LO_ file is overwritten each time.

PXE Everywhere Agent log:

LogFileName registry is configurable using MODULE.PXEEVERYWHERE.LOGPATH installer property, with the default filename PXEEverywhere.log.

• MaxLogfileSize is configurable using MODULE.PXEEVERYWHERE.MAXLOGFILESIZE. Default is 1048576 (1MB).

• When the log file reaches its maximum size, it is renamed with a .LO_ extension and a new .LOG file is created. The .LO_ file is overwritten each time.

• The logfile format is configurable using MODULE.PXEEVERYWHERE.LOGFORMAT default (1) is Configuration Manager-compatible format.

Shopping client log:

Not configurable using installer properties. Configurable by modifying the Log4Net settings in the Shopping.UI.exe.config file, located in %ProgramFiles%\1E\Client\Extensibility\Shopping folder.

WakeUp client log:

LogFileName registry is configurable using MODULE.WAKEUP.LOGPATH and MODULE.WAKEUP.LOGFILENAME installer properties.

• MaxLogFileSize is configurable using MODULE.WAKEUP.MAXLOGFILESIZE. Default is 1048576 (1MB).

• 5 rollover files numbered 1 (newest) to 5 (oldest) with the rollover number included as n.log

• In previous versions of WakeUp the .LOG file was renamed with a .LO_ extension and a new .LOG file is created. The .LO_ file is overwritten each time.

Names and locations of log files created by Content Distribution.

Content Distribution logs

The default location for all Content Distribution logs is the folder %ALLUSERSPROFILE%\1E

For issues relating to	Required log files	Location of log files
1E Client	1E.Client.log NomadBranchUninstall-YYY-MM-DDThh_mm_ss_000Z.log	Default location: %ALLUSERSPROFILE%\1E\Client\
Content Distribution client	NomadBranch.log	Default location: %ALLUSERSPROFILE%\1E\NomadBranch\ Optional location if installed using 1E Client Deployment Assistant (CDA): C:\WINDOWS\CCM\Logs\
OS deployment	NomadPackageLocator.log NBCacheActions.log All Configuration Manager logs including SMSTS.log	The path changes at the different stages of an OS deployment.
ContentDistribution integration	ContentDistribution.log	%ALLUSERSPROFILE%\1E\ContentDistribution\
Delivery Optimization monitoring and reporting	NomadBranch.DO.log	Default location: %ALLUSERSPROFILE%\1E\NomadBranch\ NomadBranch.DO.log is created when Delivery Optimization monitoring and reporting are enabled using the DeliveryOptimizationReportingEnabled registry value.

• Mandatory uninstall logs: This is only logged when a mandatory uninstall is attempted on 1E Client devices. If uninstall fails, you can troubleshoot by using this log): C:\Windows\Temp\AppClarity.SofwareReclaimer.log

• 1E Client logs: Containing Reclaimer module logs: C:\ProgramData\1E\Client\1E.Client.log

• Optional/Mandatory API logs: This is on server side and will log all incoming APIs from the 1E Client Reclaim module and their response: C:\ProgramData\1E\SLA Platform\WebExternal.log

• ReclaimConsolidation: If the report fails or does not trigger after an Optional/Mandatory respond to the server with results, then refer to: C:\ProgramData\1E\SLA Platform\Web.log

The table below describes the logging levels which are configurable for server components.

Value	Description
Error	Only outputs errors. An error is a serious problem, typically requiring operator intervention of some sort to restore full functionality.
Warn	Outputs errors and warnings. A warning indicates a potential problem, where the system can nonetheless function without intervention.
Info	Outputs general information in addition to errors and warnings. This is the default.
Debug	Outputs debugging information in addition to all the previous levels.
Trace	Outputs the maximum information available. Used only in exceptional circumstances as it will generate huge amounts of logging output.

The method of configuring logging levels uses the above text values, where -log=0 is the default to mean the same as -log=info.