How to Configure the Client Log File
Applies To: Application Virtualization
You can use the following procedures to configure the Application Virtualization (App-V) Client log file.
To change the log file location
Edit the following registry key value to specify the new path for the log file. You must restart the sftlist service after changing this value. This location can also be changed interactively after installation.
To change the log reporting level
By default, the type of messages that are written to the log include all events of severity level 4 (Informational) or higher. The severity level is stored in the following key value. Set this key value to 5 to enable verbose logging. Use verbose logging only for short periods during troubleshooting because it will generate a very large volume of messages and cause the log to fill up quickly.
To change the log size
In Application Virtualization (App-V) 4.5, the log size is controlled by the following registry key value. This value defaults to 256 MB and defines the maximum size, in MB, that the log can grow to before being reset.
Caution This registry key value must be set to a value greater than zero to ensure the log file does get reset.
To change the number of backup copies
When the log file reaches the maximum size, a reset is forced when the next write to the log occurs. A reset causes a new log file to be created, and the old file is renamed as a backup. The following registry setting controls the number of backup copies of the log file that are kept when the file is reset. The default value is 4.
The format of the backup log file names is: sftlog_YYYYMMDD_hhmmss-uuu.txt and is based on the reset time, in Universal Coordinated Time (UTC). The following table lists the symbols used in creating the file names and their descriptions.
2-digit month (01–12)
2-digit day of the month (01–31)
You can learn more about MDOP in the TechNet Library, search for troubleshooting on the TechNet Wiki, or follow us on Facebook or Twitter.