![what is vmware horizon client what is vmware horizon client](https://cdn.windowsreport.com/wp-content/uploads/2016/09/vmware.jpg)
Our users typically use 3 monitors, one being the screen on the laptop/surface. The remaining entries in the log look just like a startup sequence for all the monitors. Once the timer expires, the next command is MGMT_IMG :Resetting encoder (reset_type=1). The thought is that 60 seconds of not-connection or packets arriving out of order (which PCoIP also considers a "loss") are causing this. More info: Looking at the PCoIP log, it's definitely disconnecting, via MGMT_IMG :Imaging Timer expiry. Please, any suggestions, advice, tips? How about where to look to see the screen freeze recorded in a log? I've looked at C:\Program Data\VMWare\VDM\logs, but nothing really conclusive. We are using vmware ESXi 6.0, so PCoIP is the only protocol available, you can't use RDP on 6, like you could with 5. To me, it seems like PCoIP protocol is the culprit, since this is the mechanism the client uses to show you the VDI on your computer. We use a master image, then clone that for all our VDIs, so everyone should have roughly the same settings and devices. The mouse and keyboard are not affected, as you can see if you were typing or mousing during the incident. All users make use of 2 to 3 monitors including their laptop screen. Everything works fine, except 2 to 3 times a day (sometimes more, sometimes over 2 days), the screen FREEZES for a second or two, then all black, then within 30 seconds to 2 minutes, it pops back to normal. They open the client, connect to their assigned VDI vm machine. Everyone has a laptop or a Surface, with the Horizon View Client ver. This is affecting almost all of our Virtual Desktop Interface or VDI users.