Last summer my customer bought a couple af K2 cards for a small VDI deployment running Windows 10. The POC on View 6.1.1 was successful.
After a long period with test my customer decided to move it to production, using the newly released View7.
We have now spent 6 months including VMware support trying to get a stable k120q setup. The larger profile the more stable client, but using a k160q is way overkill and too expensive.
VMware ended up suggesting latest Nvidia drivers but those give same problems of freezing desktops when running video or having large display areas change.
Now I am trying to get support from Nvidia, but cannot find anything but SUMS which my customer does not have. What to do?
This is the problem with every GPU vendor that uses a hardware only model. The support falls on the GPU vendor (i.e. the OEM who sold the card), in turn they can raise a support ticket with NVIDIA. We recognised this gap so GRID 2.0 and up are sold via a software model license with SUMS allowing the user to purchase 24/7 support and direct support with NVIDIA.
The legacy hardware only model means your custoemr needs to raise a support ticket with the server OEM who was the seller of the card.
You aren’t clear as to what "unstable client" actually means/symptoms/ error messages. Our support staff provide goodwill support on these forums if sufficient info is provided. We also make available the self-help KB articles generated by SUMS funding free to all users to search on their symptoms and debug techniques. search on GRD Support Home Page | NVIDIA
Since it’s VMware version specific it does suggest it could be the right course of action to pursue with VMware.
Because the custoemr has found changing the PCoIP setting to what should intuitively be a weightier protocol has resolved the video issue and we haven’t seen this with ICA/HDX/Blast I’m still suspicious this in part is worth pursuing on the protocol side too. Hence why I think pursuing with VMware is worthwhile. Configuring PcoIP resolved one issue.
The driver roll-back for the second issue I have highlighted to our engineering team. So they will be aware when HP pass it on.