Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Changing the log file behavior in the VMware Horizon components (1025887)

Last Updated: 12/8/2023Categories: InformationalTotal Views: 88561Language:
Chinese (Simplified)JapaneseEnglish

11 like this article

Subscribe to get an email
newsletter with new updates

11 people found this helpful Please provide article feedback:

Purpose

This article provides steps to manually configure the logging behaviour of these VMware Horizon components or enable logging connection:

VMware Horizon Connection Server

VMware Horizon Agent

VMware Horizon Client

For Horizon clients logs, see Horizon Client for Windows Log Files and respective documentation for your o/s variant.

Resolution

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:

Description

Key

Value Type

Value

Number of days logs are kept

MaxDaysKept

REG_DWORD

Integer value

Number of debug logs kept

MaxDebugLogs

REG_DWORD

Integer value

Max size (MB) of a debug log

MaxDebugLogSizeMB

REG_DWORD

Integer 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.

Related Information

For more information on the location of VMware View log files, see Location of VMware View log files (1027744).
Opening a command or shell prompt
Enabling verbose logging for View Composer related components
Location of VMware View log files
VMware View コンポーネントでログ ファイルの動作を変更する
更改 VMware View 组件中的日志文件行为
See Also, Enabling verbose logging for View Composer related components (1010388)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
重做或删除租户的域注册 (2100081)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Horizon

Related Versions:

VMware Horizon 8

VMware Horizon 7.x

VMware Horizon 7

Take Our Survey

Support Assistant