Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
This article provides steps to manually configure the logging behaviour of these VMware Horizon components or enable logging connection: VMware Horizon Connection ServerVMware Horizon AgentVMware Horizon Client For Horizon clients logs, see Horizon Client for Windows Log Files and respective documentation for your o/s variant.
The main available log levels are INFO, DEBUG and FULL. There are additional levels for certain components, These are component-specific and typically only enabled at the request of support after an initial analysis highlights the requirement to investigate. Horizon logging and level increases require certain o/s permissions. It is often better to run under an admin account.There is additional overhead with running logs at a higher level, please do so for a specific period of time with heightened awareness in terms of resource overhead and reset to defaults once the required event has been captured. Changing log levels VMware Horizon Connection Server: To change log levels for the View Connection Server: Go to Start > All Programs > VMware > Set View Connection Server Log Level.Select the appropriate logging level. 1: View Info 2: View Debug 3: View Full 0: Reset to installation defaults VMware Horizon Agent: To change log levels for the View Agent: Run the command: C:\Program Files\VMware\VMware View\Agent\DCT>support.bat loglevels Select the appropriate logging level: 1: View Info 2: View Debug 3: View Full 4: PCoIP Info 5: PCoIP Debug 6: Virtual Channel Info 7: Virtual Channel Debug 8: Virtual Channel Trace 0: Reset to installation defaults Notes: Each element is set separately. You must run the command once for each change you make.To enable trace log on a linux client, start vmware-usbarbitrator and vmware-view-usbd using these commands: #vmware-usbarbitrator --verbose #vmware-view-usbd -o log:trace Log location is /tmp/vmware-root/. Logging parameters To change the rotation, the number of log files kept, and the maximum file size parameter, you must change this registry key (this is in view servers and desktops):[HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VDM\Log]Note: Before making any registry modifications, ensure that you have a current and valid backup of the registry. For more information on backing up and restoring the registry, see the Microsoft article 136393 . Note: The preceding link was correct as of October 10, 2020. If you find the link is broken, provide feedback and a VMware employee will update the link.This table outlines the necessary changes: DescriptionKeyValue TypeValueNumber of days logs are keptMaxDaysKeptREG_DWORDInteger valueNumber of debug logs keptMaxDebugLogsREG_DWORDInteger valueMax size (MB) of a debug logMaxDebugLogSizeMBREG_DWORDInteger value Notes: By default, DWORD values are hexadecimal. Change this to decimal so that the data value is read in plain English.Some keys may not be defined by default. If undefined, the default values are: MaxDebugLogs: 10 MaxDebugLogSizeMB: 50. If you increase the MaxDebugLogSizeMB, you may need an advanced text editor to handle the file size. Note: You can also change the logging parameters by using the View Common Configuration ADM Template. This contains policy settings common to all View components. For more information, see VMware View Common Configuration ADMX Template Settings in the documentation. VMware Horizon Client: Horizon Windows Client: Run the command: C:\Program Files\VMware\VMware Horizon View Client\DCT\support.bat loglevels Note: The support.bat file is located here: C:\Program Files\VMware\VMware Horizon View Client\DCT. Legacy Clients may use a location of C:\Program Files\VMware\VMware View\Client\DCT. Select the appropriate logging level: 1: View Info 2: View Debug 3: View Full 4: PCoIP Info 5: PCoIP Debug 6: Virtual Channel Info 7: Virtual Channel Debug 8: Virtual Channel Trace 0: Reset to installation defaults Note: Each element is set separately. You must run the command once for each change you make. Horizon Mac Client: Enabling Mac client logging Horizon Client for Mac 2012 or later: List/Check the current log levels cd /Applications/VMware Horizon Client.app/Contents/Library/dct/ # directory of DCT on macOS sudo ./HorizonCollector.sh -l Set the USB log levels sudo ./HorizonCollector.sh -x USB:trace Collect the USB log sudo ./HorizonCollector.sh -c USB Note: "sudo ./HorizonCollector.sh -c All" can collect logs for all features preferred for troubleshooting. Reset all the log levels to default sudo ./HorizonCollector.sh -r Horizon Client for Mac 2006 and below (legacy clients) To enable Mac client debug logging, run these commands from a terminal window (click on Terminal found in Applications\Utilities) before launching the client: launchctl setenv VMWARE_VIEW_DEBUG_LOGGING 1 To apply this logging permanently, edit the /Applications/VMware Horizon Client. app/Contents/Library/services.sh file and append these options.
For more information on the location of VMware View log files, see Location of VMware View log files (1027744).Opening a command or shell promptEnabling verbose logging for View Composer related componentsLocation of VMware View log filesVMware View コンポーネントでログ ファイルの動作を変更する更改 VMware View 组件中的日志文件行为See Also, Enabling verbose logging for View Composer related components (1010388)