When searching for a solution to why VDI logins are to slow, i stumbled across the following inside the VMLM.TXT logfile.
2017-11-09T11:54:35.105 TRACE (0f20-044c) [LogonMonitor::ProcessGroupPolicyEvent] Failed to find Session for User PolicyEvent Id: 4016, ActivityID: {326CBB71-4DA3-44D2-9C4B-C03388944437}, Account:
2017-11-09T11:54:35.105 TRACE (0f20-044c) [LogonMonitor::ProcessGroupPolicyEvent] Failed to find Session for User PolicyEvent Id: 5314, ActivityID: {326CBB71-4DA3-44D2-9C4B-C03388944437}, Account:
2017-11-09T11:54:35.105 TRACE (0f20-1660) [LogonMonitor::ProcessGroupPolicyEvent] Failed to find Session for User PolicyEvent Id: 5326, ActivityID: {326CBB71-4DA3-44D2-9C4B-C03388944437}, Account:
2017-11-09T11:54:35.105 TRACE (0f20-1660) [LogonMonitor::ProcessGroupPolicyEvent] Failed to find Session for User PolicyEvent Id: 5327, ActivityID: {326CBB71-4DA3-44D2-9C4B-C03388944437}, Account:
2017-11-09T11:54:41.152 INFO (0f20-1660) [LogonMonitor::ProcessWFREvent] Windows Folder Redirection Processing Started
2017-11-09T11:54:56.746 TRACE (0f20-1660) [LogonMonitor::ProcessGroupPolicyEvent] Failed to find Session for User PolicyEvent Id: 5016, ActivityID: {326CBB71-4DA3-44D2-9C4B-C03388944437}, Account:
2017-11-09T11:54:56.746 TRACE (0f20-17a0) [LogonMonitor::ProcessGroupPolicyEvent] Failed to find Session for User PolicyEvent Id: 4016, ActivityID: {326CBB71-4DA3-44D2-9C4B-C03388944437}, Account:
2017-11-09T11:54:56.746 TRACE (0f20-1660) [LogonMonitor::ProcessGroupPolicyEvent] Failed to find Session for User PolicyEvent Id: 4016, ActivityID: {326CBB71-4DA3-44D2-9C4B-C03388944437}, Account:
2017-11-09T11:54:56.746 TRACE (0f20-17a0) [LogonMonitor::ProcessGroupPolicyEvent] Failed to find Session for User PolicyEvent Id: 5016, ActivityID: {326CBB71-4DA3-44D2-9C4B-C03388944437}, Account:
2017-11-09T11:54:56.746 TRACE (0f20-1660) [LogonMonitor::ProcessGroupPolicyEvent] Failed to find Session for User PolicyEvent Id: 4016, ActivityID: {326CBB71-4DA3-44D2-9C4B-C03388944437}, Account:
2017-11-09T11:54:56.746 TRACE (0f20-17a0) [LogonMonitor::ProcessGroupPolicyEvent] Failed to find Session for User PolicyEvent Id: 5016, ActivityID: {326CBB71-4DA3-44D2-9C4B-C03388944437}, Account:
2017-11-09T11:54:56.746 TRACE (0f20-17a0) [LogonMonitor::ProcessGroupPolicyEvent] Failed to find Session for User PolicyEvent Id: 5016, ActivityID: {326CBB71-4DA3-44D2-9C4B-C03388944437}, Account:
2017-11-09T11:55:39.997 INFO (0f20-17a0) [LogonMonitor::ProcessWFREvent] Windows Folder Redirection Processing Finished
This showed me 2 things:
1) Folder redirection is taking a very long time thus i need to find out why. This delay is a hit and mis. Sometimes login is 17 sec, the other time it is about 120 sec!
2) I see a lot of messages about "Failed to find Session for User PolicyEvent id..."
Does anyone know what the Failed to find.. messages are about and i there is something i need to check/fix?
Can you provide the value of the environment variable "ViewClient_Machine_Name"? This would allow us to track the endpoint from were the connection was initiated.
Excuse me for the delayed response!
I have added 2 vmlm files that were logged during a login that took a very long time. As you can see there are numerous "Failed to find Session for User PolicyEvent ..." events.
We also frequently notice a long delay when processing Folder Redirection, don't know if it's related:
2017-11-30T19:24:14.093 INFO (0f50-0c54) [LogonMonitor::ProcessWFREvent] Windows Folder Redirection Processing Started
2017-11-30T19:25:53.403 INFO (0f50-0c54) [LogonMonitor::ProcessWFREvent] Windows Folder Redirection Processing Finished
Value of "ViewClient_Machine_Name" within this session was: NOT33976
Any assistance would be very appreciated