<?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 Re: Changes in registry on master do not reflect on VMs after composing in Horizon Desktops and Apps</title>
    <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Changes-in-registry-on-master-do-not-reflect-on-VMs-after/m-p/2839456#M93585</link>
    <description>&lt;P&gt;Hello jshaole808.&amp;nbsp; Enforcing the changes through Domain Group Policy did the trick.&amp;nbsp; VMs will be recomposed and get the correct registry value.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Thu, 01 Apr 2021 21:10:17 GMT</pubDate>
    <dc:creator>Mario_Rivas</dc:creator>
    <dc:date>2021-04-01T21:10:17Z</dc:date>
    <item>
      <title>Changes in registry on master do not reflect on VMs after composing</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Changes-in-registry-on-master-do-not-reflect-on-VMs-after/m-p/2817899#M92602</link>
      <description>&lt;P&gt;Hello.&amp;nbsp; We run a Horizon 7.12 VDI for Windows 10 v2004 VMs, using the VMware OSOT to prepare the Master VM to be used for recomposing.&lt;/P&gt;&lt;P&gt;Before, due to getting a "No Network" issue, we had implemented the following registry settings on the master VM. Under, &lt;STRONG&gt;Computer\HKLM\Software\Policies\Microsoft\Windows\NetworkConnectivityStatusIndicator\&lt;/STRONG&gt; we made the following changes:&amp;nbsp; &lt;STRONG&gt;NoActiveProbe&lt;/STRONG&gt;, from &lt;STRONG&gt;1&lt;/STRONG&gt; it was changed to &lt;STRONG&gt;0&lt;/STRONG&gt; and &lt;STRONG&gt;DisableActiveProbing&lt;/STRONG&gt;. from &lt;STRONG&gt;1&lt;/STRONG&gt; it was changed to &lt;STRONG&gt;0&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;This is set along with of a local policy, under &lt;STRONG&gt;Computer Configuration\Administrative Templates\Network\Network Connectivity Status Indicator&lt;/STRONG&gt;, the item &lt;STRONG&gt;Specify passive polling&lt;/STRONG&gt; is &lt;STRONG&gt;Enabled&lt;/STRONG&gt; with &lt;STRONG&gt;Disable passive polling&lt;/STRONG&gt;&amp;nbsp;checked.&lt;/P&gt;&lt;P&gt;This setting has been working just fine until we recently ran MS Updates on the master VM and did recompose VMs with this new update.&amp;nbsp; The registry settings, on the VMs, changed back to &lt;STRONG&gt;1&lt;/STRONG&gt;, making them to get the "No Network issue" (with Outlook 365) not working.&amp;nbsp; Interesting fact is that the master template still has the registry changes we did before.&lt;/P&gt;&lt;P&gt;Has anyone ran into this issue?&amp;nbsp; Any help is greatly appreciated.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Mario&lt;/P&gt;</description>
      <pubDate>Thu, 17 Dec 2020 17:24:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Changes-in-registry-on-master-do-not-reflect-on-VMs-after/m-p/2817899#M92602</guid>
      <dc:creator>Mario_Rivas</dc:creator>
      <dc:date>2020-12-17T17:24:05Z</dc:date>
    </item>
    <item>
      <title>Re: Changes in registry on master do not reflect on VMs after composing</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Changes-in-registry-on-master-do-not-reflect-on-VMs-after/m-p/2824034#M92874</link>
      <description>&lt;P&gt;I'm sure this is resolved now, but for those that find this thread, the optimization tool sets a local computer policy that forces the 0 to 1. Below is the policy:&lt;/P&gt;&lt;P&gt;&lt;A href="https://admx.help/?Category=Windows_10_2016&amp;amp;Policy=Microsoft.Policies.InternetCommunicationManagement::NoActiveProbe" target="_blank"&gt;https://admx.help/?Category=Windows_10_2016&amp;amp;Policy=Microsoft.Policies.InternetCommunicationManagement::NoActiveProbe&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Jan 2021 20:29:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Changes-in-registry-on-master-do-not-reflect-on-VMs-after/m-p/2824034#M92874</guid>
      <dc:creator>jshaole808</dc:creator>
      <dc:date>2021-01-19T20:29:26Z</dc:date>
    </item>
    <item>
      <title>Re: Changes in registry on master do not reflect on VMs after composing</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Changes-in-registry-on-master-do-not-reflect-on-VMs-after/m-p/2824304#M92888</link>
      <description>&lt;P&gt;Hello jshaole808. Thanks for your reply.&amp;nbsp; We are testing forcing, through Domain Group Policy, to have those registry settings with the required setting value.&lt;/P&gt;&lt;P&gt;Will update this discussion on the results.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jan 2021 17:39:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Changes-in-registry-on-master-do-not-reflect-on-VMs-after/m-p/2824304#M92888</guid>
      <dc:creator>Mario_Rivas</dc:creator>
      <dc:date>2021-01-20T17:39:25Z</dc:date>
    </item>
    <item>
      <title>Re: Changes in registry on master do not reflect on VMs after composing</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Changes-in-registry-on-master-do-not-reflect-on-VMs-after/m-p/2839456#M93585</link>
      <description>&lt;P&gt;Hello jshaole808.&amp;nbsp; Enforcing the changes through Domain Group Policy did the trick.&amp;nbsp; VMs will be recomposed and get the correct registry value.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 01 Apr 2021 21:10:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Changes-in-registry-on-master-do-not-reflect-on-VMs-after/m-p/2839456#M93585</guid>
      <dc:creator>Mario_Rivas</dc:creator>
      <dc:date>2021-04-01T21:10:17Z</dc:date>
    </item>
  </channel>
</rss>

