Changes in registry on master do not reflect on VMs after composing

[Mario_Rivas]

Hello.  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.

Before, due to getting a "No Network" issue, we had implemented the following registry settings on the master VM. Under, Computer\HKLM\Software\Policies\Microsoft\Windows\NetworkConnectivityStatusIndicator\ we made the following changes:  NoActiveProbe, from 1 it was changed to 0 and DisableActiveProbing. from 1 it was changed to 0.

This is set along with of a local policy, under Computer Configuration\Administrative Templates\Network\Network Connectivity Status Indicator, the item Specify passive polling is Enabled with Disable passive polling checked.

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.  The registry settings, on the VMs, changed back to 1, making them to get the "No Network issue" (with Outlook 365) not working.  Interesting fact is that the master template still has the registry changes we did before.

Has anyone ran into this issue?  Any help is greatly appreciated.

Thanks

Mario

[jshaole808]

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:

https://admx.help/?Category=Windows_10_2016&Policy=Microsoft.Policies.InternetCommunicationManagemen...

[Mario_Rivas]

Hello jshaole808. Thanks for your reply.  We are testing forcing, through Domain Group Policy, to have those registry settings with the required setting value.

Will update this discussion on the results.

[Mario_Rivas]

Hello jshaole808.  Enforcing the changes through Domain Group Policy did the trick.  VMs will be recomposed and get the correct registry value.

Thanks