<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Horizon 2103 Single Monitor Issue in Horizon Desktops and Apps</title>
    <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-2103-Single-Monitor-Issue/m-p/2861865#M94634</link>
    <description>&lt;P&gt;This is related to my post at&amp;nbsp;&lt;A href="https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-Desktop-Locks-up-at-Black-Screen/m-p/2859067#M94530" target="_blank"&gt;https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-Desktop-Locks-up-at-Black-Screen/m-p/2859067#M94530&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is my current problem.&amp;nbsp; I have Dell Wyse 5070 clients running ThinOS 9.1.3112.&amp;nbsp; I have two systems setup to do some testing.&amp;nbsp; One has a single monitor while the other one has dual monitors.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can connect to a desktop using the Blast protocol however, the zero-client with a single monitor locks up at the desktop with the&amp;nbsp;&lt;STRONG&gt;Project to a Connected Screen&lt;/STRONG&gt; dialog box.&amp;nbsp; It will stay frozen until the resolution is changed on the zero-client.&amp;nbsp; That seems to unfreeze the desktop.&amp;nbsp; I attached an image of what the desktop looks like when it freezes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The zero-client with dual monitors does not have this issue and works as intended and all is right with the world.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I thought this was strictly a Wyse issue until I tried accessing the desktop through the web browser.&amp;nbsp; Once again, the desktop loads but freezes up at the same spot but if I resize the browser window it resolves the problem.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have tried changing the master image hardware config from 2 monitors to 1 monitor to automatically detect settings in the video card settings.&amp;nbsp; I have adjusted the video memory.&amp;nbsp; I tried setting the screen resolution to different settings, nothing seems to help and I really need to get this resolved.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I attempted to force PCoiP instead of Blast but that is causing other issues that I don't have the time to troubleshoot.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any suggestion will be greatly appreciated.&amp;nbsp; Thanks.&lt;/P&gt;</description>
    <pubDate>Thu, 12 Aug 2021 16:58:24 GMT</pubDate>
    <dc:creator>robinsonjl3</dc:creator>
    <dc:date>2021-08-12T16:58:24Z</dc:date>
    <item>
      <title>Horizon 2103 Single Monitor Issue</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-2103-Single-Monitor-Issue/m-p/2861865#M94634</link>
      <description>&lt;P&gt;This is related to my post at&amp;nbsp;&lt;A href="https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-Desktop-Locks-up-at-Black-Screen/m-p/2859067#M94530" target="_blank"&gt;https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-Desktop-Locks-up-at-Black-Screen/m-p/2859067#M94530&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is my current problem.&amp;nbsp; I have Dell Wyse 5070 clients running ThinOS 9.1.3112.&amp;nbsp; I have two systems setup to do some testing.&amp;nbsp; One has a single monitor while the other one has dual monitors.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can connect to a desktop using the Blast protocol however, the zero-client with a single monitor locks up at the desktop with the&amp;nbsp;&lt;STRONG&gt;Project to a Connected Screen&lt;/STRONG&gt; dialog box.&amp;nbsp; It will stay frozen until the resolution is changed on the zero-client.&amp;nbsp; That seems to unfreeze the desktop.&amp;nbsp; I attached an image of what the desktop looks like when it freezes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The zero-client with dual monitors does not have this issue and works as intended and all is right with the world.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I thought this was strictly a Wyse issue until I tried accessing the desktop through the web browser.&amp;nbsp; Once again, the desktop loads but freezes up at the same spot but if I resize the browser window it resolves the problem.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have tried changing the master image hardware config from 2 monitors to 1 monitor to automatically detect settings in the video card settings.&amp;nbsp; I have adjusted the video memory.&amp;nbsp; I tried setting the screen resolution to different settings, nothing seems to help and I really need to get this resolved.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I attempted to force PCoiP instead of Blast but that is causing other issues that I don't have the time to troubleshoot.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any suggestion will be greatly appreciated.&amp;nbsp; Thanks.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Aug 2021 16:58:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-2103-Single-Monitor-Issue/m-p/2861865#M94634</guid>
      <dc:creator>robinsonjl3</dc:creator>
      <dc:date>2021-08-12T16:58:24Z</dc:date>
    </item>
    <item>
      <title>Re: Horizon 2103 Single Monitor Issue</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-2103-Single-Monitor-Issue/m-p/2863507#M94683</link>
      <description>&lt;P&gt;Very discouraging that no one has any suggestions or hasn't seen this issue.&amp;nbsp; I am still battling it and have nothing good to report.&amp;nbsp; I did get a PM saying to disable Print Redirection but that did not help in my situation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have been digging through logs and I found the following:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The driver \Driver\WudfRd failed to load for the device ROOT\VMWUSM\0000&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;and&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The driver \Driver\WudfRd failed to load for the device ROOT\VMWVIDD\0000&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Not sure if this has anything to do with anything but they stuck out.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Aug 2021 14:02:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-2103-Single-Monitor-Issue/m-p/2863507#M94683</guid>
      <dc:creator>robinsonjl3</dc:creator>
      <dc:date>2021-08-24T14:02:45Z</dc:date>
    </item>
    <item>
      <title>Re: Horizon 2103 Single Monitor Issue</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-2103-Single-Monitor-Issue/m-p/2863553#M94684</link>
      <description>&lt;P&gt;&lt;SPAN&gt;You can go ahead and mark this resolved.&amp;nbsp; I finally figured out what was causing it.&amp;nbsp; I overlooked a particular GPO that was being inherited by the VDI OU that fixed an issue with our dual monitor fat-clients.&amp;nbsp; Once I disabled inheritance the image began working as intended.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Aug 2021 17:25:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-2103-Single-Monitor-Issue/m-p/2863553#M94684</guid>
      <dc:creator>robinsonjl3</dc:creator>
      <dc:date>2021-08-24T17:25:51Z</dc:date>
    </item>
    <item>
      <title>Re: Horizon 2103 Single Monitor Issue</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-2103-Single-Monitor-Issue/m-p/2864086#M94706</link>
      <description>&lt;P&gt;What was the GPO that you you were using?&lt;/P&gt;</description>
      <pubDate>Fri, 27 Aug 2021 13:56:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-2103-Single-Monitor-Issue/m-p/2864086#M94706</guid>
      <dc:creator>Genose</dc:creator>
      <dc:date>2021-08-27T13:56:28Z</dc:date>
    </item>
    <item>
      <title>Re: Horizon 2103 Single Monitor Issue</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-2103-Single-Monitor-Issue/m-p/2864095#M94707</link>
      <description>&lt;P&gt;This particular GPO has been in place since before I started managing this environment and apparently it was due to some bizarre behavior with an nVidia driver and dual monitor fat-clients.&amp;nbsp; So the GPO was a simple logon script that called&amp;nbsp;&lt;STRONG&gt;DisplaySwitch.exe /extend.&amp;nbsp;&amp;nbsp;&lt;/STRONG&gt;The GPO was labelled nVidia Dual Monitor Fix and since I am not using nVidia cards in my servers I completely ignored the GPO since I assumed it was specific driver related stuff.&amp;nbsp; Apparently, this was forcing the desktop image to try and extend the display to a second monitor which is fine if the zero-client had a second monitor attached but when only one monitor was connected it locked up the display until you changed the resolution.&amp;nbsp; Mouse clicks were still being registered just the display wasn't refreshing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How I figured this out was disabling inheritance on the VDI OU and logging in with nothing but the default domain policy being applied.&amp;nbsp; I then attached specific GPO's necessary for our domain leaving out the nVidia GPO.&amp;nbsp; I then investigated the GPO to see what it did.&amp;nbsp; It definitely made me feel stupid but I'm just glad I got it figured out before these need to be deployed.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Aug 2021 14:19:03 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-2103-Single-Monitor-Issue/m-p/2864095#M94707</guid>
      <dc:creator>robinsonjl3</dc:creator>
      <dc:date>2021-08-27T14:19:03Z</dc:date>
    </item>
  </channel>
</rss>

