The various components of the FSLogix agent make extensive use of logging. Examination of the log files is the first place to look when trying to determine how the system is behaving.
At the top of each log file, the system records some basic information such as the versions of the FSLogix agent components, etc.
Each operation performed by FSLogix components will create a section that contains all of the relevent log entries for that operation.
At the beginning of each day, a new log file is begun. The daily log files are kept for 7 days by default. Log files older than this period are removed.
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.
|Value Name||Value Type||Description|
|LogDir||REG_SZ||Specifies the location where log files should be stored. Local and UNC paths are accepted. Default is |
New log files are begun each day. This specifies how many to keep. If the value is not set, the default is ‘7’.
|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.|
Component Log Files
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 Path|
|Profile Configuration Tool||ConfigTool|
|IE Plugin (Java Control)||IEPlugin|
|Java Rule Editor||JavaRuleEditor|
|FSLogix Agent Service (frxsvc.exe)||Service|
|Office 365 Container||ODFC|
|AD Computer Group Processing||AdsComputerGroup|
|Windows Search Roaming||Search|