Knowledge Base
The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

|
Changing the log file behavior in VMware View components (1025887)
Purpose
- VMware View Connection Server and Security 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 and Security Server:
- Click 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
To change log levels for the View Client:
- Run the command:
C:\Program Files\VMware\VMware View\Client\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
Note: Each element is set separately. You must run the command once for each change you wish to make.
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
Note: Each element is set separately. You must run the command once for each change you wish to make.
To change 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.
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,
DWORDvalues are hexadecimal. Change this to decimal so that the data value is read in plain English. - Some keys may not already be defined by default. If undefined, the default values are:
MaxDebugLogs:10MaxDebugLogSizeMB:50. If you increase theMaxDebugLogSizeMB, you may need an advanced text editor to handle the file size.
Additional Information
Tags
See Also
Update History
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.
Actions
KB:
- Updated:
- Categories:
- Languages:
- Product Family:
- Product(s):
- Product Version(s):

