Hi,
I'm trying to set up the remote path, but i'm getting the following:
ERROR (0aec-1088) [VMWRollSessionLogFile] Failed Uploading Log File:
These are W7 clones going to a Server 2008 R2 Fileshare..
Hi,
I'm trying to set up the remote path, but i'm getting the following:
ERROR (0aec-1088) [VMWRollSessionLogFile] Failed Uploading Log File:
These are W7 clones going to a Server 2008 R2 Fileshare..
Can anyone confirm this is working as expected in 7.6 with no additional settings? We have never had an issue with this log populating locally until recent 7.1 to 7.6 update.
Hi Devin,
As of 7.6 the installer sets the Logon Monitor service to manual. You will need to set it to enabled if you want to use it.
Thanks,
Erik
My client is also getting the similar issue with 7.6. We have set the service to automatic no logs are created at login, only the VMLM.TXT file.
VMLM.TXT log messages
ERROR (0af4-18cc) [MailslotServer::ProcessMessage] Empty Message, Nothing To Do
TRACE (0de8-1464) [LogonMonitor::ProcessGroupPolicyEvent] Failed to find Session for User PolicyEvent Id: 4016,
In the windows Event Log it states the VMLM install was corrupt, we attempted to fix this with a reinstall of the horizon 7.6 image but we had the same issue.
After which we realized after the DNS Shortname was not resolving. After we fixed this issue the logs worked again.
CORRECTION. The DNS NetBios name only resolved the session log from being created it is still broke.
Erik-
Unfortunately, with this service on we still are not generating session logs locally for logins. Log directory is no longer empty but just showing generic vmlm log. Any ideas?
Hello all, same issue here with version 7.7.
I set the service as Automatic, and I get the vmlm log but nothing else.
Thanks !
Logon monitor not loading after running installation. Tried on a couple of Windows 7 machines. When launching the helper, you see the cmd prompt screen flash for a quick second and the VMLM is not launching
Hi Will,
Is this 7.6? If so, you will need to set the service to enabled.
Thanks,
Erik
I know this has been productized but I was wondering if this is still active.
I'm trying to dig into the long shell load times and was wondering if there is anyway we can get some debugging insight into what is happening. I see events like:
2019-05-15T14:21:54.666 INFO (1194-0cc0) [SensSink::ProcessPostShellEvent] Received Sens PostShell: Username: <USERNAME>, Session: 1
2019-05-15T14:22:37.041 TRACE (1194-14f8) [LogonMonitor::ShellLoadWorker] Found Taskbar. Session: 1
But what is going on for that ~42 seconds between Received Sens and Taskbar?