<?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>MaorZoh Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>MaorZoh Tracker</description>
    <pubDate>Fri, 24 Nov 2023 07:21:55 GMT</pubDate>
    <dc:date>2023-11-24T07:21:55Z</dc:date>
    <item>
      <title>Re: Agent Upgrade Not Available</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Agent-Upgrade-Not-Available/m-p/2996940#M100214</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;You must have&amp;nbsp;Horizon Enterprise Plus Subscription license and to migrate to&amp;nbsp;Next-Gen Cloud Connector" (Horizon Edge Gateway) to be able to work with this BETA feature.&lt;/P&gt;&lt;P&gt;At this point, all related documentation regarding this feature were removed from VMware website.&lt;/P&gt;&lt;P&gt;Luckily, a few weeks ago I created a step-by-step guide how to enable and configure the "Horizon Agent Auto-Upgrade" feature. &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@3CBC42A1E7848F607FD419D398107BF9/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&lt;/P&gt;&lt;P&gt;See attached PDF.&lt;/P&gt;&lt;P&gt;Tested successfully.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope it helps.&lt;/P&gt;</description>
      <pubDate>Thu, 23 Nov 2023 13:17:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Agent-Upgrade-Not-Available/m-p/2996940#M100214</guid>
      <dc:creator>MaorZoh</dc:creator>
      <dc:date>2023-11-23T13:17:08Z</dc:date>
    </item>
    <item>
      <title>Re: Duplicate lease on DHCP after rebuilding process</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Duplicate-lease-on-DHCP-after-rebuilding-process/m-p/2987529#M99925</link>
      <description>&lt;P&gt;Hi Scott,&lt;/P&gt;&lt;P&gt;It makes sense, but I partially agree with it because in another environment we have it doesn't happen to us, but only in a specific environment and both communicate with the same DHCP server.&lt;/P&gt;&lt;P&gt;Even with a new MAC address, it should not happen, otherwise especially Instant-Clones would have problems all the time.&lt;/P&gt;&lt;P&gt;I reduced the leas time from 2 days to 4 hours to check if it has a positive effect.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Sep 2023 05:47:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Duplicate-lease-on-DHCP-after-rebuilding-process/m-p/2987529#M99925</guid>
      <dc:creator>MaorZoh</dc:creator>
      <dc:date>2023-09-21T05:47:43Z</dc:date>
    </item>
    <item>
      <title>Re: Duplicate lease on DHCP after rebuilding process</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Duplicate-lease-on-DHCP-after-rebuilding-process/m-p/2987520#M99923</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN&gt;André,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thank you for your reply.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Actually,&lt;SPAN&gt;&amp;nbsp;our DHCP scope is pretty big and there are enough available IP addresses for the machines to acquire.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Lease time is configured for 2 days. I\ll consider reducing&amp;nbsp;it even more.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Sep 2023 05:23:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Duplicate-lease-on-DHCP-after-rebuilding-process/m-p/2987520#M99923</guid>
      <dc:creator>MaorZoh</dc:creator>
      <dc:date>2023-09-21T05:23:33Z</dc:date>
    </item>
    <item>
      <title>Duplicate lease on DHCP after rebuilding process</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Duplicate-lease-on-DHCP-after-rebuilding-process/m-p/2987379#M99914</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We have some Full-Clone pools, and from time to time we rebuild random machines.&lt;/P&gt;&lt;P&gt;In most cases, the machine is getting a new IP after rebuild but the old lease stays on the DHCP server and additional lease is created with the new IP.&lt;/P&gt;&lt;P&gt;This causing the user to unable to connect to their machines until I manually delete the old lease and wait until the DNS server are updated with the change.&lt;/P&gt;&lt;P&gt;I tried to follow this article but no change.&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.mustbegeek.com/configure-dns-dynamic-update-in-windows-dhcp-server" target="_blank" rel="noopener"&gt;https://www.mustbegeek.com/configure-dns-dynamic-update-in-windows-dhcp-server&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone have an idea how to solve this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Sep 2023 07:38:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Duplicate-lease-on-DHCP-after-rebuilding-process/m-p/2987379#M99914</guid>
      <dc:creator>MaorZoh</dc:creator>
      <dc:date>2023-09-20T07:38:54Z</dc:date>
    </item>
    <item>
      <title>Published Application starts with full sign in process</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Published-Application-starts-with-full-sign-in-process/m-p/2984158#M99831</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I configured a Published Application on my RDSH farm, and I can see that when it lunched, before the app shows on my local computer,&lt;/P&gt;&lt;P&gt;It starts with a full sign in process for a few seconds as if connected to a full VDI machine, then it's closed and only then I get the app on the front.&lt;/P&gt;&lt;P&gt;Is this a normal behavior or can I bypass this sign in process somehow?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Sun, 27 Aug 2023 09:55:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Published-Application-starts-with-full-sign-in-process/m-p/2984158#M99831</guid>
      <dc:creator>MaorZoh</dc:creator>
      <dc:date>2023-08-27T09:55:33Z</dc:date>
    </item>
  </channel>
</rss>

