Fixing the “No VMware Horizon View Logon Monitor session logs are created” issue

Recently I came across an issue at a VMware Horizon View customer, where VMware Horizon View Logon Monitor session logs were not being created. The fix for this issue is described in this blog post.

The issue

The VMware Horizon View Logon Monitor session log file starts with vmlm_session_<guid>_<session_id>.txt.bak and should normally be located in C:\ProgramData\VMware\VMware Logon Monitor\Logs.

In our case, there was no session log file. Only the generic vmlm.txt file. But that doesn’t contain all the specifics you want to see.

Cause

Normally, the VMware Horizon View Logon Monitor service is set to Manual after installation. Because we have group policies with certain settings that need to be part of the golden image, because of instant cloning, they are applied during automated installation. One of those settings is setting the VMware Horizon View Logon Monitor service to Automatic, which creates the roque log files.

The fix

To fix the issue, make sure you perform the following steps in the golden image, just before sealing it.

Go to Services (services.msc) and search and select the VMware Horizon View Logon Monitor service. Stop this service. Also, make sure the service startup type is set to Automatic. Which may be your issue for not having the logs in the first place 😉 .

Go to the folder C:\ProgramData\VMware\VMware Logon Monitor\Logs and empty this folder.

Shutdown the machine, create a snapshot and use it for (instant) cloning.

Ivan de Mes

Ivan de Mes

Ivan de Mes works as an EUC Solution Architect for Login Consultants in The Netherlands. Ivan has over 19 years of experience in delivering workspace solutions at large customers in banking, health care, education and others.

In 2017, 2018 and 2019, Ivan was rewarded with the VMware vExpert status. In 2018 and 2019 Login VSI rewarded Ivan with the Login VSI Technology Advocate status.

 

For more information, please read the about page.

You may also like...