Search the VMware Knowledge Base (KB)
View by Article ID

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

  • 13 Ratings
Language Editions

Purpose

This article provides steps to manually configure the logging behavior of these VMware View components:
  • VMware View Connection Server, Security Server and Enrollment Server
  • VMware View Agent
  • VMware View Client
  • VMware View Composer

Resolution




In VMware View 4.0, the available log levels are INFO, DEBUG and FULL.

In VMware View 4.5 and later, in addition to the View log levels, there are two additional components that can be set on the View Agent and Client: PCoIP and Virtual Channel, each with their own levels.

Changing log levels

To change log levels for the View Connection, Security Server and Enrollment Server:
  1. Go to Start > All Programs > VMware > Set View Connection Server Log Level.
  2. Select the appropriate logging level.

    1: View Info
    2: View Debug
    3: View Full
    0: Reset to installation defaults

To change log levels for the View Client:
  1. Run the command:

    C:\Program Files\VMware\VMware View\Client\DCT>support.bat loglevels

    Note: In View Client 2.1 or later, the support.bat file is located at C:\Program Files\VMware\VMware Horizon View Client\DCT\support.bat.

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

To change log levels for the View Agent:
  1. Run the command:

    C:\Program Files\VMware\VMware View\Agent\DCT>support.bat loglevels

  2. 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/.

For more information on changing the View Composer logging level, see Enabling verbose logging for View Composer related components (1010388).

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 November 18, 2015. If you find the link is broken, provide a 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 View Common Configuration ADM Template Settings in the VMware View 5.1 Administration Guide.

Enabling Mac client logging

To enable Mac client 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
launchctl setenv VMWARE_VIEW_USBD_LOG_OPTIONS "-o log:trace"
launchctl setenv VMWARE_VIEW_USBARBITRATOR_LOG_OPTIONS "--debug 3"

To permanently these logging permanently, edit the /Applications/VMware Horizon View Client.app/Contents/Library/services.sh file and append these options. 

Additional Information

For more information on the location of VMware View log files, see Location of VMware View log files (1027744).

Tags

view-log-files

See Also

Update History

06/15/2012 - Added View Manager 5.1 to list of products. 09/26/2012 - Added Option "0. Reset to installation defaults" to all components. 10/12/2012 - Added link to: "View Common Configuration ADM Template Settings". 05/08/2013 - Added (this is in view servers and desktops)to the resolution section under "logging parameters". 05/19/2011 - added latest product version. 07/25/2013 - Added KB-1003892 to see also section. 01/14/2014 - Added Horizon View 5.3 to Product Versions.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 13 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 13 Ratings
Actions
KB: