Forum Discussion
Only up to 5 users can login, following won't attach profile disk
We have a RDS cluster with 2 hosts, since a few days one host has a problem that it can handle 5 users only. Every next user has problems logging in, it won't attach the profile disk. Details abou...
Jason_Parker
Microsoft
MicrosoftPlease open a MS support case as we are tracking some known issues around this semaphore time out and need to collect information as we can't reproduce the issue. This issue is related to SCSI registrations not getting properly cleaned in Windows - not necessarily an FSLogix issue, but we are looking at a way to handle it until there is a fix in Windows (potentially)
https://learn.microsoft.com/en-us/fslogix/troubleshooting-fslogix-product-support#open-a-support-request
https://learn.microsoft.com/en-us/fslogix/troubleshooting-fslogix-product-support#open-a-support-request
- Did you get any result out of the MS support case? We still face the same issue and also opened a case. Can you share your case number to reference in my support case?
Thank you!- It was corrupt entries within the below registry left behind by Fslogix incorrectly unmounting the UPD. The incorrect registry keys will not contain a ClassGUID, delete them out. In my case I had 4 corrupt entries. Let me know how you get on.
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\SCSI\Disk&Ven_Msft&Prod_Virtual_DiskAfter deleting those corrupted entries. It seemed to work fine for a while. But a couple of hours later those corrupted entries where back in place and the login issues where back. Does anyone know what we could do to prevent these corrupted entries coming back? We disabled the VHD Compact Disk policy.
