<?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>pbarrett1 Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>pbarrett1 Tracker</description>
    <pubDate>Sat, 25 Nov 2023 13:42:14 GMT</pubDate>
    <dc:date>2023-11-25T13:42:14Z</dc:date>
    <item>
      <title>Re: "Source signal on other port"</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/quot-Source-signal-on-other-port-quot/m-p/2914182#M97214</link>
      <description>&lt;P&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/1244562"&gt;@GreenDean&lt;/a&gt; Think of the message - source signal on other port. This is referring to the source, the zero client is not the source however it may help to understand which port is port 1 or port 2. When at the connect screen of any PCoIP zero client if you hit Ctrl + 1 the OSD logo should be on display 1 if you hit Ctrl + 2 the OSD logo should now move to display 2 this is assuming that you have two displays connected.&lt;/P&gt;&lt;P&gt;Typically when I see messages like this I always tell customers to connect to the AWI (Web Interface) of the zero client and go to &lt;STRONG&gt;Info &amp;gt; Attached Devices&lt;/STRONG&gt; from here you can clearly see which port the display is connected to. Port 1 should be the DP (display port) and Port 2 should be your DVI port. If you are connected to the DVI port then the VM is expecting to see something connected to Port 1 so you may have to get a display that supports DP and connect it.&lt;/P&gt;&lt;P&gt;In any case it is the VMware SVGA driver that is messed up because if you look at the host VM log file (pcoip_server_yyyymmddxxxx.txt) file for the session you are in you will clearly see that the zero client has sent it's correct topology to the host.&lt;/P&gt;&lt;P&gt;I know this is an old post that I am responding to so treat it as just information.....&lt;/P&gt;&lt;P&gt;Paul@Teradici&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jun 2022 00:48:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/quot-Source-signal-on-other-port-quot/m-p/2914182#M97214</guid>
      <dc:creator>pbarrett1</dc:creator>
      <dc:date>2022-06-15T00:48:26Z</dc:date>
    </item>
    <item>
      <title>Re: PCoIP Session Unexpectedly Disconnects</title>
      <link>https://communities.vmware.com/t5/VMware-Horizon-Discussions/PCoIP-Session-Unexpectedly-Disconnects/m-p/2902849#M17464</link>
      <description>&lt;P&gt;I know this is an older post but just seeing it now. The zero client log kind of tells the issue - Unable to communicate with peer. This is basically a networking issue as communication is lost between the zero client and the host VM.&lt;/P&gt;&lt;P&gt;Only to tell exactly what is going on is to review the entire zero client log file and the pcoip_server_xxxx.txt file located in -&lt;/P&gt;&lt;P&gt;C:\ProgramData\Vmware\VDM\logs&lt;/P&gt;&lt;P&gt;Each time a new session starts there is a new pcoip_server file created. May be difficult to get this log if using instant clones but still key to understanding exactly what is going on.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Right now I suspect an issue with the phone as you probably have QoS set for VoIP and if network gets congested the PCoIP traffic will be treated as scavenger class traffic so may need to set QoS policy for PCoIP. This is very easy to eliminate the phone just use a different direct connection to the core switch and by pass the IP phone.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;</description>
      <pubDate>Wed, 06 Apr 2022 20:40:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Horizon-Discussions/PCoIP-Session-Unexpectedly-Disconnects/m-p/2902849#M17464</guid>
      <dc:creator>pbarrett1</dc:creator>
      <dc:date>2022-04-06T20:40:15Z</dc:date>
    </item>
    <item>
      <title>Re: Horizon 8 2111 Rotated Secondary Monitor Issue</title>
      <link>https://communities.vmware.com/t5/VMware-Horizon-Discussions/Horizon-8-2111-Rotated-Secondary-Monitor-Issue/m-p/2902611#M17460</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;Over the past week VMware and Teradici have worked together to come up with a work around for the artifacts showing when display is rotated 90 degrees clockwise. Please follow the steps below, we have tested this in our lab and if has resolved the issue.&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;SPAN&gt;Connect via RDP or use VSphere Web Console. Check in Device Manager if Display Adapters has VMWare SVGA. If it does, disable VMWare SVGA&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Create the registry value HKEY_LOCAL_MACHINE\SOFTWARE\Teradici\PCoIP\pcoip_admin\pcoip.disable_svga_async_capture=dword:00000001&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Connect to a session and test 90deg clockwise rotated display&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;SPAN&gt;At the present time this is the only work around we have.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 05 Apr 2022 21:21:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Horizon-Discussions/Horizon-8-2111-Rotated-Secondary-Monitor-Issue/m-p/2902611#M17460</guid>
      <dc:creator>pbarrett1</dc:creator>
      <dc:date>2022-04-05T21:21:36Z</dc:date>
    </item>
    <item>
      <title>Re: Horizon 8 2111 Rotated Secondary Monitor Issue</title>
      <link>https://communities.vmware.com/t5/VMware-Horizon-Discussions/Horizon-8-2111-Rotated-Secondary-Monitor-Issue/m-p/2901681#M17459</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;Not sure how to make this post show as the most recent however I want to let you know today both VMware and Teradici had a very successful call to discuss this issue and the issue is actively being investigated. As soon as we have more information or work around we will post here. Please be patient while we investigate.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 31 Mar 2022 20:39:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Horizon-Discussions/Horizon-8-2111-Rotated-Secondary-Monitor-Issue/m-p/2901681#M17459</guid>
      <dc:creator>pbarrett1</dc:creator>
      <dc:date>2022-03-31T20:39:06Z</dc:date>
    </item>
    <item>
      <title>Re: Horizon 8 2111 Rotated Secondary Monitor Issue</title>
      <link>https://communities.vmware.com/t5/VMware-Horizon-Discussions/Horizon-8-2111-Rotated-Secondary-Monitor-Issue/m-p/2900693#M17454</link>
      <description>&lt;P&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/1739194"&gt;@TechMassey&lt;/a&gt;this won't be the issue in mostly everyone experiencing the artifacts on a rotated display in this post as most are running PCoIP zero clients and not using the VMware software client.&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;</description>
      <pubDate>Fri, 25 Mar 2022 22:11:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Horizon-Discussions/Horizon-8-2111-Rotated-Secondary-Monitor-Issue/m-p/2900693#M17454</guid>
      <dc:creator>pbarrett1</dc:creator>
      <dc:date>2022-03-25T22:11:51Z</dc:date>
    </item>
    <item>
      <title>Re: Horizon 8 2111 Rotated Secondary Monitor Issue</title>
      <link>https://communities.vmware.com/t5/VMware-Horizon-Discussions/Horizon-8-2111-Rotated-Secondary-Monitor-Issue/m-p/2900692#M17453</link>
      <description>&lt;P&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/5168482"&gt;@KippB&lt;/a&gt;not much. I have provided screen shots, video and a complete log bundle and now they want me to share my two test VMs with them. I have one VM running Horizon Agent 2106 and the other running Horizon Agent 2111. I can only reproduce this issue on the 2111 Agent and I suspect it may be related to VMware dropping the SVGA driver from 2111. I am still trying to verify. Both VMs are running the SVGA driver 8.17.2.14.&lt;/P&gt;&lt;P&gt;My logs show the SVGA driver is only picking up one display and the Indirect Display Driver is not picking up any. Not sure what this new Indirect driver does I suspect it may be Blast related and if so probably not required for anyone running pure PCoIP - to be confirmed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;</description>
      <pubDate>Fri, 25 Mar 2022 22:09:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Horizon-Discussions/Horizon-8-2111-Rotated-Secondary-Monitor-Issue/m-p/2900692#M17453</guid>
      <dc:creator>pbarrett1</dc:creator>
      <dc:date>2022-03-25T22:09:02Z</dc:date>
    </item>
    <item>
      <title>Re: Horizon 8 2111 Rotated Secondary Monitor Issue</title>
      <link>https://communities.vmware.com/t5/VMware-Horizon-Discussions/Horizon-8-2111-Rotated-Secondary-Monitor-Issue/m-p/2898169#M17442</link>
      <description>&lt;P&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/5488622"&gt;@virtuallypsycho&lt;/a&gt;&amp;nbsp;I have picked up your Teradici case.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The part about pasting the screen capture into Paint or Word is to see what is coming from the frame buffer. If the pasted image is clean then we know we are getting clean info from the frame buffer which now points to an issue with the driver or PCoIP itself.&lt;/P&gt;&lt;P&gt;At this time I will not rule out anything further other than this is an issue that VMware will have to address as they are responsible for all the code. VMware are doing their own development work with PCoIP.&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;</description>
      <pubDate>Fri, 11 Mar 2022 23:05:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Horizon-Discussions/Horizon-8-2111-Rotated-Secondary-Monitor-Issue/m-p/2898169#M17442</guid>
      <dc:creator>pbarrett1</dc:creator>
      <dc:date>2022-03-11T23:05:55Z</dc:date>
    </item>
    <item>
      <title>Re: Horizon 8 2111 Rotated Secondary Monitor Issue</title>
      <link>https://communities.vmware.com/t5/VMware-Horizon-Discussions/Horizon-8-2111-Rotated-Secondary-Monitor-Issue/m-p/2898168#M17441</link>
      <description>&lt;P&gt;All,&lt;/P&gt;&lt;P&gt;I was able to reproduce this issue in my lab first attempt. The artifacts are quite sever. I am only noticing this issue in Horizon Agent 2111 and do not experience it with Horizon Agent 2106.&lt;/P&gt;&lt;P&gt;I have opened an SR with VMware and will keep this post updated.&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;</description>
      <pubDate>Fri, 11 Mar 2022 22:57:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Horizon-Discussions/Horizon-8-2111-Rotated-Secondary-Monitor-Issue/m-p/2898168#M17441</guid>
      <dc:creator>pbarrett1</dc:creator>
      <dc:date>2022-03-11T22:57:12Z</dc:date>
    </item>
    <item>
      <title>Re: Horizon 8 2111 Rotated Secondary Monitor Issue</title>
      <link>https://communities.vmware.com/t5/VMware-Horizon-Discussions/Horizon-8-2111-Rotated-Secondary-Monitor-Issue/m-p/2898095#M17438</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Paul here from Teradici. I will confirm that yes we are seeing a spike in cases like this. We have not made any changes to the firmware that will impact this issue. Have you heard anything back from VMware on the case you have open with them?&lt;/P&gt;&lt;P&gt;I am in the process of trying to reproduce this issue in my lab. I have confirmed with our engineering team that during our initial testing a rotated display was not in the test plan. We will test and report back.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;</description>
      <pubDate>Fri, 11 Mar 2022 17:36:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Horizon-Discussions/Horizon-8-2111-Rotated-Secondary-Monitor-Issue/m-p/2898095#M17438</guid>
      <dc:creator>pbarrett1</dc:creator>
      <dc:date>2022-03-11T17:36:41Z</dc:date>
    </item>
  </channel>
</rss>

