Everyday I come into work and see thousands of the same message in the title. This is happening in multiple floating pools. These pools are 24/7 always on kiosk type VM's using zero-clients. When this problem happens zero clients are unable to connect even though there are available VM's in the pool. They will connect but no until after I delete all the available VM's and let new ones spin up. After I do this things seem to work for about 15-20 hours and the same thing happens again.
Happening in both View 6.2.1 and Horizon 7.1 environments. Using Windows 10 LTSB 2016 for the parent image.
Has anybody seen this before? I had an SR open for this and they said to turn off client-side caching in the registry of the parent image but this did not resolve the issue.
Any suggestion would be great! If you need any other information I'd be happy to help provide that.
Zero Clients: Samsung NC190, Dell FX100, WYSE PxN
Firmware: All v4.7.1
Guest OS: Windows 10 Enterprise 2016 LTSB
Profile Mgmg: Persona
Please check If you have installed Dell KACE agent, If yes ensure to install the KACE agent first and then View agent
Did you find a solution for this? I am having the exact same problem. I changed the VDMConnectionTicketTimeout based on another thread I found for this issue and that took my number of errors from 66,000+ down to 10,000. I have a ticket open with support, but we have not found a solution yet.
What version of VMware Tools are you using? I think what ended up being the solution was updating Tools. We were using 10.1.7 and updated to most current at the time which was 10.1.10.
Curious if that helps you out. It was a mess getting it resolved thru VMware support on this one.
We are using 10.2.49. I am still working with VMware support. I have seen 3 or 4 different solutions to this now, but none have worked for me. I will post whatever works for us when we find it. If anyone has any thoughts, I will try anything at this point. 😃
We believe we've narrowed this down to a missing userinit registry key. Now we just need to figure out why the key is on the parent and missing from the linked clones.