T17:01:38.01Z> LVL:3 RC: 0 MGMT_IMG:(set_new_sub_session_rx): Imaging subsession changing from 0 to 1! Then a few minutes later the VMware remote console screen is opened and it tries to enforce a resolution of 1920x843 and now the port is configured with no source.Ī display with a native resolution of 1280x1024 cannot support a resolution of 1920xanything. T16:59:10.19Z> LVL:2 RC: 0 MGMT_IMG:(stats): Receiving video for videohead 1 with resolution 1280x1024 The zero client logs show after Session Active that both the client and the host agree on the monitor topology and timing. Notice the zero client is showing the primary display is on port 2 and only 1 display connected with a resolution of 1280x1024. The zero client was being forced to try to use a resolution that the attached display cannot support. It was observed in the zero client and host VM logs that when the VMware remote console screen was opened it was forcing a change in topology and this change was being pushed down to the zero client. While this may not be a big issue if you are using a persistent VM it may be a problem is the user is using an instant clone VM. The user will have to disconnect and in some cases will have to power cycle the zero client to recover. If VMware remote console screen is closed the session never recovers. When using a PCoIP zero client connecting to VMware VM running Horizon Agent 8.2 if the VMware remote console is open while user is in session the zero client will display a blank screen or you may receive a message "source signal on other port".
0 Comments
Leave a Reply. |