Horizon View Logon Monitor Deprecated?

[alexhselene]

I am unsure if this has been addressed before--if so I was not able to find much on the topic.

I am deploying new parent images with Windows 10 1809 to get us off our current Win7 environment. As part of our development process we are trying to get our logon times down. Currently using Persona with a decent sized profile, we are seeing logon reach about 1min plus some change. This is about a 30 second increase from the current logon time in our Win7 Production environment.

Onto the issue.....we have installed Horizon agent 7.7 on the parent image and enabled the Horizon View Logon Monitor service(the Logon monitor in bundled into the agent after version 7.5 I believe). However, after casting this image out to a test pool, the logs (located: C:\ProgramData\VMware\VMware Logon Monitor\Logs)are not showing almost any of the information that is promised in this article. It is mostly just gibberish in the main log, and the session log file itself is just MIA.

Has the Logon Monitor been deprecated? Or is it no longer being supported?

It seems like a tool that would be very useful to have when troubleshooting the logon time issues, without it we are flying blind trying to determine where the issues may be.

[vJoeG]

Logon monitor definitely hasn't been deprecated. Were you using it with your Windows 7 images and getting good data there?

On the connection servers is the timing profiler enabled? If you answered yes to monitoring the Windows 7 VM's it likely is but I figured it best to ask.

Logon Monitor Configuration Settings (for Timing Profiler)

I recently set up a Windows 10 1809 image with Logon Monitor enabled and am seeing the login data both in the logs and in the GUI from the newadmin console.

[alexhselene]

We have never used the Logon monitor for our Win7 environment since the logon times have been reasonable.

The timing profiler is enabled on the connection servers. I went through that article you linked and as far as I can tell everything is configured. The reg keys are setup, and the service is started. It still only generates a 'vmlm' log and no session log. I have attached the log here, and as you can see there really isn't any super useful information in there.

I also uploaded an image from the Horizon Admin console and as you can see the metrics are all blank.

[sjesse]

There is a service for logon monitor is set to manual or disabled? I forgot what version the below kb article referenced

VMware Knowledge Base

Its sometime after the helpdesk tool was released, I think it was 7.5 or 7.6 that started happening, I'm not sure if the newer versions fixed it.

[sjesse]

Sorry reread the first post saying its enabled, its basically the service being enabled and the userinit string that starts this. In the vlmn file whats in there, is there something thats causing the monitor tool to think the session hasn't finished loading.

[alexhselene]

It's possible, but I am not sure how to spot that.

[alexhselene]

vJoeG​ what is your configuration for the Logon Monitor? So far I still cannot get it working.

Our registry settings on the parent:

flags                         REG_DWORD     (0x3)

LogKeepDays          REG_DWORD     (0x14)

LogMaxSizeMB       REG_DWORD     (0x256)

RemoteLogPath      REG_SZ               \\remotelogpathhere  (is this necessary?)

The service is set to Automatic. No session log is being generated and the Fling is not an option. Any ideas what I may be doing wrong?

[vJoeG]

The RemotePath is optional and only if you want to save the logs off onto a server. I do not have that set nor have I set it for any clients in the past.

I also didn't specify the log file size.

Here are my other 2 settings

flags                         REG_DWORD     (0x3)

LogKeepDays          REG_DWORD     (0x7)

Otherwise, just the Service set to automatic and that was it for my lab.

[alexhselene]

That is very strange. I am still getting these weird text files that don't contain all the information and no session log. Maybe something with GPO is interfering with the logon monitor?

I am going to check again to ensure the setting is enabled for the Timing Profiler on the connection servers.

[Barker2015]

I'm having the same issue with Horizon Agent 7.7.  I thought I was going crazy, because I thought in the past it generated a clean session log with timings.  Now I just get debug and trace info in the text files.

*****edit****

Oh disregard, I just found the session logs in that folder, they have a bak file extension, but when I opened them in notepad it had the info I was used to.

I was expecting a log or txt file.

Sorry, I guess my issue isn't the same as yours...

[alexhselene]

So, I did get the Logon Monitor working after upgrading to the newest version of Horizon Agent. However something seems off about the logs. The session log is always timestamped as yesterday, and the logon time is far shorter than it should be. Timing the logon myself I get around 40 seconds, but on the session log it says the time is 4.36 seconds. Does anyone know what might be going on?

[Techstarts]

vJoeG​

One question, as this service is not enabled by default, should we enabled this always or it is the purely troubleshooting purpose?

[larstr]

Preetam Zare,

IMHO it's a good idea to leave it running. In addition to making troubleshooting easier it's also required to get the logon statistics working within the html5 interface.

Lars