andiwe79's Posts

You are right, there was an issue with the config file. The elux manager added a section line "[ ]" above the rtav.codec line and that seemed to make the client ignore this setting. I removed the section line and restarted the client. RTAV worked instantly. Thank you for this workaround! Can you tell if this will be fixed - so a workaround is not needed anymore - with a future client version? Best regards Andreas

Hello Mangui, thanks for your recommendations but had no success to resolve the issue. 1. When you use Blast protocol by eLux Linux client, did you enable H.264 or HEVC? If no, please try enable H.264 and HEVC to see if RTAV works or not.  No changes to the issue with h.264 enabled (was already) or disabled. Also HEVC Option enabled makes no difference. Also tested with PCoIP as Display Protocol, absolutely same result. 2. Please check the libraries under "/usr/lib/vmware/view/software", "/usr/lib/vmware/view/vaapi", "/usr/lib/vmware/view/vaapi2" and "/usr/lib/vmware/view/vdpau", show the libraries under these four folders and run "ldd" command for all these libraries to check their dependency libraries available or not /usr/lib/vmware/view/software is non existent here: elux> ls -l total 6 drwxr-xr-x 2 root root 1024 Jul 21 06:12 bin drwxr-xr-x 2 root root 1024 Jul 21 06:12 client drwxr-xr-x 2 root root 1024 Jul 21 06:12 vaapi drwxr-xr-x 2 root root 1024 Jul 21 06:12 vaapi2 drwxr-xr-x 2 root root 1024 Jul 21 06:12 vdpau drwxr-xr-x 2 root root 1024 Jul 21 06:12 vdpService   Following the results of the dependency check. I am not sure if the "not found" is really an issue. Keep in mind that when i connect the same client to an Agent Version 7.13.1 it works just fine. The issue is only when connecting to Agent in Version 8.x (e.g. 2103,2106) elux> ldd vdpau/libavcodec.so.58 linux-vdso.so.1 => (0x00007ffc68b78000) libavutil.so.56 => not found libx264.so.157.6 => not found libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fbdd8845000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fbdd847b000) /lib64/ld-linux-x86-64.so.2 (0x00007fbdd8f19000) elux> ldd vaapi2/libavcodec.so.58 linux-vdso.so.1 => (0x00007ffcbd7da000) libavutil.so.56 => not found libx264.so.157.6 => not found libva.so.2 => /usr/lib/x86_64-linux-gnu/libva.so.2 (0x00007feb564ed000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007feb55c23000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007feb55859000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007feb55655000) /lib64/ld-linux-x86-64.so.2 (0x00007feb562fc000) elux> ldd vaapi/libavcodec.so.58 linux-vdso.so.1 => (0x00007ffce6246000) libavutil.so.56 => not found libx264.so.157.6 => not found libva.so.1 => not found libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f1629a5b000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f1629691000) /lib64/ld-linux-x86-64.so.2 (0x00007f162a134000) elux> ldd vdpau/libavutil.so.56 linux-vdso.so.1 => (0x00007ffcbbdc5000) libvdpau.so.1 => /usr/lib/x86_64-linux-gnu/libvdpau.so.1 (0x00007fd53eb27000) libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007fd53e7ed000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fd53e4e4000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fd53e2c7000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fd53defd000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fd53dcf9000) libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007fd53dae7000) libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007fd53d8c5000) /lib64/ld-linux-x86-64.so.2 (0x00007fd53f03f000) libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007fd53d6c1000) libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007fd53d4bb000) elux> ldd vaapi2/libavutil.so.56 linux-vdso.so.1 => (0x00007ffd379ed000) libva-x11.so.2 => /usr/lib/x86_64-linux-gnu/libva-x11.so.2 (0x00007f820fc3e000) libva.so.2 => /usr/lib/x86_64-linux-gnu/libva.so.2 (0x00007f820fc19000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f820f410000) libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007f820f0d6000) libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007f820eec4000) libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3 (0x00007f820ecbe000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f820eaa1000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f820e6d7000) libdrm.so.2 => /usr/lib/x86_64-linux-gnu/libdrm.so.2 (0x00007f820fc05000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f820e4d3000) /lib64/ld-linux-x86-64.so.2 (0x00007f820fa2f000) libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f820e2b1000) libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007f820e0ad000) libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f820dea7000) elux> ldd vaapi/libavutil.so.56 linux-vdso.so.1 => (0x00007ffd4aae6000) libva-x11.so.1 => not found libva.so.1 => not found libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f5aad11f000) libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007f5aacde5000) libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007f5aacbd3000) libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3 (0x00007f5aac9cd000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f5aac7b0000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f5aac3e6000) /lib64/ld-linux-x86-64.so.2 (0x00007f5aad73d000) libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f5aac1c4000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f5aabfc0000) libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007f5aabdbc000) libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f5aabbb6000)   3. To make RTAV works in this eLux Linux client, you can try add below string in /etc/vmware/config(if file not exists, create one)      rtav.codec="VmwTheoraSpeex" Added this one but also no results. Hope we can get this sorted.   Best regards Andreas  

@larstr wrote: Andreas, I guess we could be experiencing the same issue as you're seeing here: https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-client-2106-for-Linux-issue-with-Teams/td-p/2858324/jump-to/first-unread-message   Lars Ours looks bit different, because actually i can select the device (audio/video) in the dropdown menu of the application. But then it just displays nothing. Despite the webcams control light is switched on.

meanwhile i have tested some more scenarios: Elux Linux Client 2006 and 2103 working with Agent 7.13.1 Elux Linux Client 2006 and 2103 Not working with Agent 2006, Agent 2103 or Agent 2106 Windows Clients always work. Can not test 2106 Elux Client yet because our Client management has no image yet. But i doubt this will bring any improvement as all clients are working with Horizon 7.x Agents. Keep in mind that we are using direct connect agent plugin if that would make any difference. i think it is the same topology as for non tunneled connection (no uag) isn't it?  

Did you check Product Interoperability Matrix? https://interopmatrix.vmware.com/#/Interoperability?isHideGenSupported=true&isHideTechSupported=true&isHideCompatible=false&isHideIncompatible=false&isHideNTCompatible=false&isHideNotSupported=true&isCollection=false&col=569,5588,5372,5080,4094,5355,4718,3938,3782,4802,4059,3941,3613,3445,3218,3002,2877,3940,3746,3377,2917,2704,2827,2572,3006,2629,2577,2483,2369,2181,2147,2022,1075,945,3492,3427,2955,2711,2487,2158,1040,974,928,868,872,729,823,730,454,2034,942,902,866,726,710,635,474,328,473,418,377,329,297,150,472,417,298,185,112,113&row=108,5609,5750,5354,5444,5172,4760,4153,5504,5469,4784,5035,4674,4150,4138,3925,3843,3741,3861,3605,3664,3465,3249,2982,2904,2920,2749,2570,2578,2482,2393,2222,2144,2114,1086,1037,1041,1019,1676,1672,889,875,842,824,738,737,736   Maybe this is the reason depending on your environment. I would check if upgrading to 2106 is a better option.

Seems to be working on Windows Clients but to be an issue at least with the Linux Client on our Thin-Clients. Version 2006 is used on eLux. Will try to let our Client Management upgrade this and see what happens.

Like #1 suggested by preetam check if the performance is same with a e.g. Windows Desktop Client. Did you enable h264 on the wyse 5070? I had also performance issues when setting the h264 option on this thin client. Just do not enable that checkbox for the 5070. It will use h264 in newer firmwares automatically. Best regards Andreas

I have multiple customers with RSA SecurID 2FA working on UAG without having anything enabled on Connection Servers. Maybe you have missed something in UAG Config. Did you set the auth-method on the Horizon Settings page? Just enabling the RSA SecurID is not enough.

Maybe you can try disabling view storage accelerator for that full clone pool if it has been enabled. Had a similar issue with this but HZ 7.7 on vSphere 6.0. Is the storage accelerator enabled for your pool/vcenter? Best regards Andi

If you are using vGPU then maybe it is a NVIDIA Driver related issue. I had some issues at Customers with this when Driver Versions did not match or NVIDIA Licensing Server had issues. Could be worth checking this.

I had a similar issue with a full clone pool. I disabled View Storage Acceleration on that pool and VMs could be provisioned successfully again. Horizon 7.7 with ESX 6.5 Build 10884925 Best regards Andreas

What NVIDIA Driver Version is installed in your environment. vMotion Support came with NVIDIA Software Family 7.0 - which is a Driver Version >V410. What's New :: NVIDIA Virtual GPU Software Documentation Maybe you need to upgrade your ESXi vib and Windows Driver to a new Version. Best regards

The Teradici Protocol does not support the S4B Virtualization Pack afaik. You need the Client Component installed that comes only with the VMware installers for your OS. See supported OSes here: Configuring VMware Virtualization Pack for Skype for Business Best regards Andreas

Did you already re-enter the Credentials as described in this KB article: VMware Knowledge Base If you reinstalled the Composer Service to a new machine you may need to migrate the RSA keys from the old composer. VMware View 5.0 Documentation Center I know this is from view 5 but the .net will work with newer versions too . Best regards Andreas

This is hard to tell without any further info. What is exactly the status of the Machines in View Admin? Please klick on the "..." behind the error. Do your VMs have the correct DNS Name? Have the computer accounts been created in the AD Structure? Have the created VMs the correct windows license activated (use of KMS is supported - MAK only with Skiplicenseactivation RegKey!) Are you using Quickprep oder Sysprep? If using Sysprep i would check the Panther logs for more information. Maybe there are some windows apps blocking the sysprep. What Horizon Version / Agent are you using exactly with what Windows 10 Version? Horizon 7.5 Agent is not supported with Win10 1809 AFAIK. Best regards Andreas

I also don't think WAN accelerators could do a great benefit to encrypted and latency relevant workloads. Did you try optimizing PCoIP at the Agent with the ADMX Files? e.g. PCoIP Bandwidth Settings Configure the PCoIP session bandwidth floor Specifies a lower limit, in kilobits per second, for the bandwidth that is reserved by the PCoIP session. This setting configures the minimum expected bandwidth transmission rate for the endpoint. When you use this setting to reserve bandwidth for an endpoint, the user does not have to wait for bandwidth to become available, which improves session responsiveness. Make sure that you do not over-subscribe the total reserved bandwidth for all endpoints. Make sure that the sum of bandwidth floors for all connections in your configuration does not exceed the network capability. The default value is 0, which means that no minimum bandwidth is reserved. When this setting is disabled or not configured, no minimum bandwidth is reserved. This setting applies to Horizon Agent and the client, but the setting only affects the endpoint on which it is configured. When this setting is modified during an active PCoIP session, the change takes effect immediately. 80ms is quite high, i have sub 30ms and it is working fine. Both Blast and PCoIP. ATM i prefer Blast in my Home Office from a fat client. Best regards Andreas