Installation Logs When VMware Tools is Automatically Upgraded on Windows OS
Article ID: 422287
Updated On:
Products
Issue/Introduction
When upgrading VMware Tools using vSphere Lifecycle Manager (vLCM) or Update-Tools command of PowerCLI, upgrade is performed under system account.
Therefore, installation logs are generated in a different location than when upgrade is performed manually after login to Windows OS.
Note: After login to Windows OS and perform upgrade manually, log files such as following are generated in C:\Users\<User Name>\AppData\Local\Temp (%Temp%).
- vminst.log
- vmmsi.log, vmmsi.log_YYYYMMDD_HHMMSS.log
Environment
VMware vSphere ESXi
Resolution
When automatically upgrade VMware Tools on a Windows OS using vSphere Lifecycle Manager (vLCM) or Update-Tools command of PowerCLI , following log file is generated in C:\Windows\Temp (%windir%\Temp) or C:\Windows\Temp\vmware-SYSTEM (%windir%\Temp\vmware-SYSTEM) :
- vminst.log (Install log): Contains VMware controlled components log output.
- vmmsi.log, vmmsi.log_YYYYMMDD_HHMMSS.log (MSI log): Contains Microsoft MSI controlled log output.
Note: VMware Tools upgrade fails during device driver installation, setupapi.dev.log located under C:\Windows\INF (%windir%\INF) may also be used for investigation.
- setupapi.dev.log (Device Installation Log): A log file generated by SetupAPI of Windows OS that records information regarding device installations.
Additional Information
Feedback
