Jump to content

Fabian

Members
  • Posts

    3
  • Joined

  • Last visited

Posts posted by Fabian

  1. 27 minutes ago, Marcos said:

    Didn't the above mentioned workaround work? Ie. setting HKLM\SOFTWARE\Policies\VMware, Inc.\VMware Blast\Config\UdpEnabled to 0.

    VMware is working on a fix in their driver. In the mean time, we've implemented a workaround in our driver so that issues don't occur if there's a faulty VMware driver installed together with our product.

    WORKS FINE for me !!!!

    THX a lot

  2. On 6/19/2019 at 2:07 PM, Peter Randziak said:

    Hello @AlessandroG


    We got an update from the development team.

    As a work-around please try to may disable the UDP in the Blast protocol, it helped in the testing environment, can you please confirm?

    To do that please refer to Vmware documentation: (basically set HKLM\SOFTWARE\Policies\VMware, Inc.\VMware Blast\Config\UdpEnabled to 0 (string value) on machines with Horizon agent)
    https://techzone.vmware.com/sites/default/files/vmware-horizon-7-view-blast-extreme-display-protocol.pdf
    https://techzone.vmware.com/sites/default/files/resource/blast_extreme_display_protocol_in_vmware_horizon_7.pdf

    Please keep us posted.

     

    Regards, Peter

    disabled the UDP in the registry as you mentioned above.

     

    WORKS FINE  for me!!

  3. Same Problem here.

    Horizon 7.9  W2K16

    VDI Clients = Windows 10 1903 with or without NVidia GPU

    Blast = Bluescreen if ESET  is installed.

    PCOIP/RDP = OK.

    opened case with VMware, but they only "keep the customer busy" ( make different pool, try E1000, reinstall Win10, reinstall Connection Server, …..)

     

×
×
  • Create New...