HKLM\SYSTEM\CurrentControlSet\GraphicsDrivers\Configuration The next step was to modify some Graphics Drivers Registry settings. Path: HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\WindowsĪs you can see in the following screenshots the value always contained the full before path. Path: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows We changed the following registry entries to make sure there is no problem with the MFAPHOOK: So it was time for a more intensive debugging. So we decided to test it with a Windows Client and Receiver 4.2. So we changed the Receiver Version (a Thin Client with Linux was used) from 12 to 13 – but it was still the same. Then we disabled the Desktop Composition Redirection. We started to search for solutions and tried the following ones:įirst we activated the Legacy graphics mode and assigned it to the affected VMs. But also this only happened at the first login in the morning. When we tried to reproduce it this was nearly impossible – only sometimes the same problem was happening with our test user. Though after successfully logging in it was possible to logout and login again (to another VM) without any problems. Interestingly this only happened when he arrived in the morning. But after a few days the user always saw a black screen after logging in – nothing more. During the first few days everything was working fine. One user was chosen to test if everything is working. An image was created and deployed with MCS. A rollout for a new division was planned. During the last weeks I was facing a strange black screen problem in a XenDesktop 7.6 environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |