![]() ![]() … neither Nvidia nor Citrix can definitively say where the limitation is. There really isn’t anything NVIDIA can do here, their GPUs are working perfectly, are in no way at fault and there’s no need for NVIDIA to add it to any of their documentation, as it isn’t their limitation.ĭo you have the model number of a Chromebook you’ve selected for this POC that I can look at? Unfortunately, in this instance, an Operating System that isn’t widely used in enterprise environments (compared to something like Windows) is being used on the Client side, therefore feature development and configuration support will be lacking by comparison. Windows being the most popular Operating System globally moves it to the top of Citrix’s priority queue for feature development and support. It isn’t because of NVIDIA that it works with Windows as the GPU is located in the datacenter so has zero visibility of the Client or its Operating System being used, it’s because of Citrix and Microsoft. You can see this because as you’ve mentioned above, the solution works with a Windows Operating System on a Client instead of Chrome. You could use AMD GPUs and it still wouldn’t work, as it isn’t an AMD limitation either. The issue is with the combination of Citrix WorkspaceApp and Chrome, and that’s nothing to do with NVIDIA. They have the functionality and performance to encode multiple monitors (way more than two) per session or Client. The GPUs and vGPU software are doing what they’re sposed to. It may or may not be applicable in your case, but worth having a look just in case. Unrelated, but whenever I’m working with customers and they’re using vGPU / GPU technologies, I always recommend running CR, not LTSR. Lastly, I haven’t used XenDesktop 7.15 for a long time, I always run the CR to take advantage of the latest settings, but it may be worth checking which Citrix Policies are available in the LTSR vs CR in case there’s something in there that helps. Have you posted on the Citrix Forums? If no, you should be posting under these categories: There is nothing on the NVIDIA side that can be done here. The GPU is more than capable of encoding multiple monitors (or a single 4K monitor -) ). This is 100% a Citrix limitation or Citrix / Chrome configuration issue. You’ve already mentioned that other non-Chrome devices work, are you locked in to using Chrome as an OS? And as you’ve already confirmed, your POC works with a single monitor … It will also give you some future proofing, which 1080P doesn’t. If hardware encoding is critical, is having multiple monitors? How about removing a pair of low resolution 1080P monitors and replacing them with a single 4K monitor? This will free up desk space, remove cables and free up power sockets as well as giving your users much more screen estate to work with. Is using the GPU for encoding the protocol critical to the success of the POC at this time? If no, try using the CPU (server side) by changing the Citrix Policies appropriately and see if that works for your users. You can then either accept those limitations and carry on, or decide if you go down another route substituting different technologies until you get the functionality that you need. This is where you find the various limitations of each technology or combination of technologies and it’s all part of the process. Trying different configurations of hardware, software etc until you find what works and what’s acceptable for your support teams and more importantly end users. In addition to Simons answer (which is correct), the issues you’re experiencing are why it’s so important to run POCs before rolling out a new environment or set of technologies. We have played with google policy and used the chrome configuration utility from citrix: Citrix Workspace app (earlier known as Citrix Receiver) for Chrome and HTML5.Ĭitrix Workspace app (earlier known as Citrix Receiver) for Chrome and HTML5 Configuration Utility GPU: Tesla T4 Turing 16gb GPU, 2 in each host. There is an app layering nvidia fix we also perform prior to installing the drivers (regarding unifiltr) registry key. I am using the platform layer for nvidia drivers, then installing the vda afterwards. ![]() Imaging: Image created through app layering, and published with MCS (static persistent desktops). Nvidia driver version: 9.1 on both host and guest They are simple 1080p monitors and this issue happens across multiple chrome devices including i5 cpu chromebooks, chromeboxes, etc. This works fine when launching a single monitor Citrix session, however if we full screen it across 2 or more monitors it does not work. We are hoping to utilize hardware encoding for the entire screen, rather than selective h.264. We’re trying to get dual monitors working for chromebooks, with hardware encoding enabled for our GPU setup. I come here because Citrix and NVidia have both been struggling to provide me with any concrete information.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |