SIRRenens
Contributor
Contributor

Display protocol not correctly enforced

Jump to solution

Hello,

We have noticed that some users connecting to our virtual desktops are not using the enforced protocol we have choosen on our VMware Horizon desktop pools. 

Context:

We have a few virtual desktop pools using linked clone virtual machine with floating attribution. For technical purposes, we have choosen recently to enforce the use of the PCoIP display protocol only for all these pools (users are not able to change the display protocol from the pool's settings).

What we are expecting:

  • Users cannot anymore choose which display protocol they want to use, no matter how they access the pool (i.e. VMware Horizon Client, Zero Client, etc...).
  • In the "Session" menu of the VMware Horizon Admin console, we should see only "PCoIP" as the display protocol for every session.

What is happening:

  • We have still a few users using another display session protocol (such as "VMWare Blast") despite that the PCoIP protocol has been enforced on the pool.
  • Applies to users accessing the pool outside from office via VMware Horizon Client (passing through the UAG).

Question:

How is it possible ?

We expected at first that these users have not disconnected from their VMware Horizon Client and therefore the enforcement settings are still not applied... However it's been almost 1 week now and we seriously doubt that users never disconnect or even never shutdown their personal computer.

Thank you for your help and suggestions.

 

Infrastructure details:

  • VMWare Horizon 7.13.1
  • VMWare Horizon Agent  7.13.1 (
  • VMWare Tools 11329
  • Windows 10 Pro 20H2 x64
0 Kudos
1 Solution

Accepted Solutions
SIRRenens
Contributor
Contributor

Got the answer.

The user was accessing trough a web browser and not with VMware Horizon Client, therefore the only available protocol is VMware Blast.

View solution in original post

0 Kudos
1 Reply
SIRRenens
Contributor
Contributor

Got the answer.

The user was accessing trough a web browser and not with VMware Horizon Client, therefore the only available protocol is VMware Blast.

0 Kudos