Logging and diagnostics
The various components of the FSLogix create comprehensive logs. Examination of log files is the first place to look when diagnosing system behavior.
At the top of each log file, the system records basic information including versions of the FSLogix agent components.
Each operation performed by FSLogix components will create a section that contains all of the relevant log entries for that operation.
At the beginning of each day, a new log file is created. The daily log files are kept for seven days by default. Log files older than this period are deleted.
The default path for the log files can be changed. For example, it may be useful to redirect the log files to a network share when using non-persistent machines.
For each log entry, an entry of zero indicates success. When looking for problems, scan for non-zero entries.
A new install (or an install after an uninstall) will set the default level of logging. A new install will also clear previous logging settings and return to defaults. An upgrade install will leave all logging settings as they exist before the ungrade install.
Logging settings and configuration
The following settings are set in: Registry Key: HKLM\SOFTWARE\FSLogix\Logging
|Value name||Value Type||Value Definition|
|LogDir||REG_SZ||Specifies the location where log files should be stored. Local and UNC paths are accepted. Default is %ProgramData%\FSLogix\Logs. logging is done as SYSTEM when logging to a local drive, and as the Computer Object when logging to a network share. When logging to the network, be sure to grant access for the Computer Object to the network share and the folder.|
|LogFileKeepingPeriod||DWORD||New log files are begun each day. This specifies how many to keep. If the value is not set, the default is '7'. Default set by install is 2.|
|LoggingEnabled||DWORD||This value can be '0', '1', or '2'. When set to '0', the specific settings for each log file are ignored and all log files are disabled. When set to '1' the specific settings for each log file are honored. When set to '2', the specific settings for each log file are ignored and all log files are enabled. Default set by install is 2.|
|LoggingLevel||DWORD||This value is set between 0 and 3 inclusive, with the following meanings. Changing this value will take effect at the next reboot. 0 - Log DEBUG level messages and higher 1 - Log INFO level messages and higher 2 - Log WARN level messages and higher 3 - Log ERROR level messages and higher|
|RobocopyLogPath||REG_SZ||Specifies a log file name and path where the output of robocopy calls (for example, during mirroring of data in or out of a VHD) will be logged. If the value is non-existent, then the robocopy results are not logged at all. This setting is recommended to be used only for troubleshooting.|
Component-specific log files
The following settings are set in: HKLM\SOFTWARE\FSLogix\Logging
All values are of type DWORD and are set to '0' to disable logging for the component, or '1' to enable logging for the component.
|Component||Value Name||Default||Default Path|
|Profile Configuration Tool||ConfigTool||1||%ProgramData%\FSLogix\Logs\ConfigTool.|
|IE Plugin (Java Control)||IEPlugin||0||%UserProfile%\AppData\LocalLow\FSLogix\Java\Logs|
|Java Rule Editor||JavaRuleEditor||0||%ProgramData%\FSLogix\Logs\JavaRuleEditor|
|FSLogix Agent Service (frxsvc.exe)||Service||0||%ProgramData%\FSLogix\Logs\Service|
|Office 365 Container||ODFC||0||%ProgramData%\FSLogix\Logs\ODFC|
|AD Computer Group Processing||AdsComputerGroup||0||%ProgramData%\FSLogix\Logs\AdsComputerGroup|
|Windows Search Roaming||Search||1||%ProgramData%\FSLogix\Logs\Search.|
|Windows Search Plugin||SearchPlugin||0||%ProgramData%\FSLogix\Logs\SearchPlugin|
|Process Start Monitor||ProcessStart||0||%ProgramData%\FSLogix\Logs\ProcessStart|