VDINinja311's Accepted Solutions

JaeseongLee​ Are the desktops licensed via a GRID licensing server? If the desktops are not licensed, it will cap the frames per second at 3 until it is licensed. You can verify it's licensed ... See more...
JaeseongLee​ Are the desktops licensed via a GRID licensing server? If the desktops are not licensed, it will cap the frames per second at 3 until it is licensed. You can verify it's licensed in the Nvidia Control Panel. See Client Licensing User Guide :: NVIDIA Virtual GPU Software Documentation From the link: NVIDIA vGPU is a licensed product. When booted on a supported GPU, a vGPU runs at reduced capability until a license is acquired. The performance of an unlicensed vGPU is restricted as follows: Frame rate is capped at 3 frames per second. GPU resource allocations are limited, which will prevent some applications from running correctly. On vGPUs that support CUDA, CUDA is disabled. These restrictions are removed when a license is acquired. After you license NVIDIA vGPU, the VM that is set up to use NVIDIA vGPU is capable of running the full range of DirectX and OpenGL graphics applications. If licensing is configured, the virtual machine (VM) obtains a license from the license server when a vGPU is booted on these GPUs. The VM retains the license until it is shut down. It then releases the license back to the license server. Licensing settings persist across reboots and need only be modified if the license server address changes, or the VM is switched to running GPU pass through.
robsisk1972​ This is what we use for our SSMS 2016 UEM flex config file. Hopefully it helps. [IncludeRegistryTrees] HKCU\SOFTWARE\Microsoft\SQL Server Management Studio [IncludeFolderTr... See more...
robsisk1972​ This is what we use for our SSMS 2016 UEM flex config file. Hopefully it helps. [IncludeRegistryTrees] HKCU\SOFTWARE\Microsoft\SQL Server Management Studio [IncludeFolderTrees] <AppData>\Microsoft\Microsoft SQL Server <AppData>\Microsoft\SQL Server Management Studio
We have used the Logon Monitor in previous versions up to Horizon 7.6. Once we upgraded to Horizon 7.6 it has stopped functioning properly. It will either show no information at all or very littl... See more...
We have used the Logon Monitor in previous versions up to Horizon 7.6. Once we upgraded to Horizon 7.6 it has stopped functioning properly. It will either show no information at all or very little information (several of the timings are missing in the graph or blank). It is not accurate when timing with a stopwatch/app. We have had a Support Case opened since 11/13/2018 on this issue. Originally the first level support engineer told us that the Logon Monitor was broken for Blast/PCoIP protocols. I confirmed this by switching the protocol of a desktop to RDS and the timing profile was accurate and worked. Then after it was escalated to another level we were told that the Logon Monitor has been deprecated as of Horizon 7.6. I pointed them to zero documentation stating it has been deprecated and pointed them to the documentation for Horizon 7.6 and 7.7 where its still referenced on how to set it up/view the timing. Every update since has been "We are waiting for an answer from the engineering team". Now onto a 3rd level engineer and they still won't give us an answer. Seems like they completely broke it and won't confirm it, in my opinion.
I ended up with the following as well as DirectFlex disabled. # Flex config file generated with VMware User Environment Manager Application Profiler version 9.2 [IncludeRegistryTrees] ... See more...
I ended up with the following as well as DirectFlex disabled. # Flex config file generated with VMware User Environment Manager Application Profiler version 9.2 [IncludeRegistryTrees] HKCU\SOFTWARE\Microsoft\VisualStudio HKCU\SOFTWARE\Microsoft\VsHub HKCU\SOFTWARE\Microsoft\CTF HKCU\SOFTWARE\Microsoft\VSCommon HKCU\SOFTWARE\Red Gate [IncludeFolderTrees] <LocalAppData>\Microsoft\VisualStudio <LocalAppData>\Microsoft\VSCommon <LocalAppData>\Microsoft\VisualStudio Services <LocalAppData>\Microsoft\VSApplicationInsights <LocalAppData>\Microsoft\MSBuild <AppData>\Microsoft\VisualStudio