Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Location of VMware View log files (1027744)

Purpose

This article provides the locations of VMware View Manager log files.

Resolution

Note: This article references shell folders and shell folder variables. If you have performed a custom installation, your installation may differ and your log files may not be available in the path mentioned in this article.

When you install these products, the installation log is created at %TEMP%\vminst.log_date_timestamp:
  • Connection Server
  • View Transfer Server
  • Security Server
  • View Agent
  • View Client
  • View Composer
In addition, an MSI installation log is created at %TEMP%\vmmsi.log_date_timestamp.

Connection Server, Transfer Server, and Security Server logs

The Connection Server, Security Server, and Replica Server logs reside on the servers themselves.

In the View Connection Server or Security Server host, you can find the log files in one of these locations:
  • Windows 2003
    • %ALLUSERSPROFILE%\Application Data\VMware\VDM\logs
    • DriveLetter:\Documents and Settings\All Users\Application Data\VMware\VDM\logs

  • Windows 2008
    • DriveLetter:ProgramData\VMware\VDM\logs
Connection Server Backups

You can find the Connection Server backups at one of these locations in the View Connection Server:
  • %ALLUSERSPROFILE%\Application Data\VMware\VDM\backups
  • DriveLetter:\Documents and Settings\All Users\Application Data\VMware\VDM\backups

View Agent logs

The location of View Agent log files depends on the version of Windows operating system used.

View Agent log files are found in:
  • Windows XP:

    DriveLetter:\Documents and Settings\All Users\Application Data\VMware\VDM\logs

  • Windows Vista and Windows 7 and 8:

    DriveLetter:\ProgramData\VMware\VDM\logs
Note: If you have a User Data Disk (UDD), the profiles directory may redirect the log files to the UDD. In this case, substitute the DriveLetter with the UDD.

PCoIP logs

The virtual desktop PCOIP logs are called pcoip_agent*.log and pcoip_server*.log and they are located in the same location as the agent logs on the view desktop.

The client PCoIP logs are called pcoip_client*.txt and are located in the user's %temp% directory on Windows Clients.

Note: The PCOIP logs are also gathered in the Client and Agent log bundles.

Persona Management logs

Persona Management logging is managed through the View Persona Management ADM Template. By default, logging is disabled.

To enable Persona Management logging, see View Persona Management Group Policy Settings in the VMware View Administration Guide.

The default location of the Persona Management log is:
  • Windows XP: C:\All Users\Application Data\VMware\VDM\logs\VMWVvp.txt
  • Windows 7 and 8: C:\ProgramData\VMware\VDM\logs\VMWVvp.txt

View Client and View Client with local mode logs

View Client logs for local mode operations are located on the file system of the operating system in which the VMware View Client is installed. The location of the log files depends on the version of Windows operating system used.

The location of View Client log files:
  • Windows XP:

    C:\Documents and Settings\%username%\Local Settings\Application Data\VMware\VDM\Logs\

  • Windows 7 and 8,  and Windows Vista:

    C:\Users\%username%\AppData\Local\VMware\VDM\Logs\

  • Linux client:

    • MKS log: /tmp/vmware-username
    • PCoIP log: /tmp/teradici-username

  • The Linux client log collector is located at:

    /usr/bin/vmware-view-log-collector

  • Macintosh Clients do not have a script to collect the logs.

    You must manually collect these files for diagnostic and troubleshooting purposes:

    • ~/Library/Logs/VMware View Client.log
    • ~/Library/Preferences/ByHost/com.microsoft.rdc.plist
    • ~/Library/Preferences/com.microsoft.rdc.plist

    Where ~ indicates the name of the user logged into the Macintosh Client.

QuickPrep/Sysprep Script and Composer Customization logs

The View Composer Guest Agent log contains information about QuickPrep and Sysprep script execution. This log records the start and end time of script execution and contains output or error messages. The View Composer Guest Agent log is located in the Windows Temp directory on the linked clone desktop at:

%system_drive%\Windows\Temp\vmware-viewcomposer-ga-new.log

Composer logs

The View Composer logs are located in the computer in which View Composer and vCenter Server are installed.
  • In Windows 2003, the logs are located at:

    C:\Documents and Settings\All Users\Application Data\VMware\View Composer\Logs\

  • In Windows 2008, the logs are located at:

    C:\ProgramData\VMware\View Composer\Logs\

Additional Information

To change the logging level or configure log retention, see Changing the log file behavior in VMware View components (1025887).

To collect log bundles, see Collecting diagnostic information for VMware View (1017939).

Note: In some operating systems, the folders where the log files are located may be hidden from display. In such cases, ensure to unhide the folders or type the full path when searching for the log files.

For translated versions of this article, see:

Tags

view-log-files

See Also

Update History

02/14/2011 - Added the View Composer log locations 08/23/2011 - Added note on unhiding folders that contain the log files 08/31/2012 - Added Persona Management and Macintosh Client log location 10/22/2012 - Added version 5.1 05/27/2013 - Added the transfer server to the list of the servers in resolution section. 06/10/2013 - added the latest product release 06/21/2013 - Fixed the error regarding the location of the vdi server logs in windows 2008.

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

  • 19 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)
  • 19 Ratings
Actions
KB: