Some users can’t log in correctly on the RDSH Host.
If they login, first there is a cmd window seen after this the screen goes grey after this, the session is automatically closed.
As an result of this, the user is "half logged in" user is shown in task manager but you can’t logoff them neither a task is open.
Server 2016 Driver: 386.09_grid_win10_server2016_64bit_international
Eventlog is showing following two errors:
1.Der Desktopfenster-Manager-Prozess wurde beendet. (Prozessexitcode: 0x000000ff, Neustartzähler: 7, ID des primären Anzeigegeräts: NVIDIA GRID M10-0B)
| Source: Dwminit
| Event ID: 0
Ausnahmecode: 0xc00001ad
Fehleroffset: 0x00000000000f5956
ID des fehlerhaften Prozesses: 0x404c
Startzeit der fehlerhaften Anwendung: 0x01d3935419b6c0d1
Pfad der fehlerhaften Anwendung: C:\Windows\system32\dwm.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\dwmcore.dll
| Source: Application Error
| Event ID: 1000
Has anyone the same issue?
PS: No vmware horizon is used, there are about 20 user on the rdsh host.
Thanks for your answer.
No I didn’t created a ticket yet, but if I can’t resolve it by myself or by community power in the next few days I will create one.
I just recognized you’re trying to use a M10-0B profile for RDSH? This is not supported nor working. You should use at least 4GB FB for this amount of users. And you need to use the A profile for RDSH. Just tested with M10-8A profile and I was able to start 35concurrent user sessions without issues.
you need to read the documentation properly. The 1 display/1280er resolution doesn’t apply for RDS sessions. snip
A-series virtual GPU types are targeted at virtual applications users.
A-series NVIDIA vGPUs support a single display at low resolution because they are intended to support remote application environments such as RDSH and Xenapp. In these environments, virtualized applications are typically rendered in an off-screen buffer. Therefore, the maximum resolution for the A-series NVIDIA vGPUs is independent of the maximum resolution of the display head.
For sure you can use 2xFullHD with RDSH. As you use RDSH you will need to use vApps licensing means you need a vApps license for every CCU on the host and yes you need to use the A profile. In this case not the wrong profile but the FB requirement is causing the issue.
0B profile is intended for Win7 VDI or Win10 with a single screen so you can imagine that this is not sufficient for 20 users running RDSH…
good to hear that it’s working as expected. Framebuffer requirements for RDSH is pretty hard to answer as it really depends on the workload but I would expect 100-200MB per user. My tests with 8A profile runs fine for >35 users. But if you run for example AutoCAD in RDS sessions the numbers might be totally different.
Best way would be to test with a number of users and your specific workload and check the FB usage with nvidia-smi or GPUProfiler as example and then you could calculate your max numbers.,
BTW: I’m always happy to get some real use numbers from the field…so if you test it in your environment and could share it that might help others…
do you have a valid license? Otherwise you won’t see the latest releases. You need vApps licenses for your use case, no matter if you run Passthrough only.