What’s interesting is the fact that telemetry is a feature at this point (how old is Windows 10?) and you can’t win a fight against a core OS feature. Why are people still trying to fight this?
the group policy description explicitly says it does not respect it unless you're using enterprise or education.
> [...]
>If you enable this setting, you can decide what level of diagnostic data to send to Microsoft, including:
>- 0 (Security). Sends only a minimal amount of data to Microsoft, required to help keep Windows secure. Windows security components, such as the Malicious Software Removal Tool (MSRT) and Windows Defender may send data to Microsoft at this level, if enabled. Setting a value of 0 applies to devices running Enterprise, Education, IoT, or Windows Server editions only. Setting a value of 0 for other editions is equivalent to setting a value of 1.
>- 1 (Basic). Sends the same data as a value of 0, plus a very limited amount of diagnostic data, such as basic device info, quality-related data, and app compatibility info. Note that setting values of 0 or 1 will degrade certain experiences on the device.
> [...]
Disabling the relevant service might stop it regardless, but it's definitely not the group policy.
It would be prudent not to use company equipment for anything personal anyway.
As for remoting, rdp-ing from linux is a solved issue, as long as VPN is not too esoteric… at which point driver compatibility is not an issue anymore. That’s Looking Glass scenario for me :)
it having un-disablable telemetry and mandatory updates finally made me switch to Linux everywhere
otherwise it's no longer My Computer... it's Satya's