Only enable logging if you experience an issue in your Profile management deployment and want to troubleshoot it. In addition, disable logging when the issue is resolved and delete the log files, which may contain sensitive information.
This policy enables or disables logging. Only enable this policy if you are troubleshooting Profile management.
If Enable logging is disabled, only errors are logged. If this policy is not configured in GP, the value from the .ini file is used. If this policy is not configured in GP or the .ini file, only errors are logged.
This policy is a set of options that you can use to focus on specific actions and events. Only set these options if you are troubleshooting, and set them all unless you are requested to do otherwise by Citrix personnel.
If Log settings is not configured in GP, Profile management uses the settings from the .ini file. If this policy is not configured in GP or the .ini file, errors and general information are logged.
The default value for the maximum size of the Profile management log file is 1 megabyte (MB). If you have sufficient disk space, increase it to 5 or 10 MB, or more. If the log file grows beyond the maximum size, an existing backup of the file (.bak) is deleted, the log file is renamed to .bak, and a new log file is created. The log file is created in %SystemRoot%\System32\Logfiles\UserProfileManager.
In XenDesktop deployments that use Machine Creation Services a persistent folder imposes a 15 MB limit on log files (not just Profile management ones). You can store your log files on a system disk, where this limitation does not apply, or use this policy to restrict the log file size to a maximum of 7 MB; Profile management can then store, on the persistent folder, the current log file and the previous one as a .bak file.
If this policy is disabled, the default value of 1 MB is used. If this setting is not configured in GP, the value from the .ini file is used. If this setting is not configured in GP or the .ini file, the default value is used.
You can set an alternative path to which the log files are saved. The path can be to a local drive or a remote, network-based one (a UNC path). Remote paths can be useful in large, distributed environments, but they can create significant network traffic, which may be inappropriate for log files.
For profiles on virtual machines, consider whether drives on the desktops are persistent because this affects logging. If a desktop has a persistent drive (for example, if it was created with a personal vDisk using Citrix XenDesktop), set a local path to it; the log files are preserved when the machine restarts. If a desktop does not have a persistent drive (for example, it was created without a personal vDisk using XenDesktop), set a UNC path; this allows you to retain the log files but the system account for the machines must have write access to the UNC share. Use a local path for any laptops managed by the offline profiles feature.
If a UNC path is used for log files:
If Path to log file is not configured in GP, the value from the .ini file is used. If this policy is not configured in GP or the .ini file, the default location %SystemRoot%\System32\Logfiles\UserProfileManager is used.
For the special case of XenDesktop Machine Creation Services, a local, persistent folder is mapped to the C drive at C:\Program Files\Citrix\PvsVM\Service\PersistedData. This is a good location to store up to 15 MB of log data, but, if you use it, note the limit on Maximum size of the log file.