I've marked your post as an answer. This is a better solution than my original answer which I believe just does the same thing under the hood. I've had this page linked as a favorite for over a year now because although it solves my problem, the advanced settings keep getting reset after a time. I don't know why. It's probably happened five times. This is a personal computer not joined to a domain.
I do VPN in for work regularly but no policies are being pushed down or it would happen multiple times per week. It's a source of frustration because the settings, when returned to default, prevent secure applications which only permit TLS 1. To name one, Webex Meetings Office Office Exchange Server. Not an IT pro? Resources for IT Professionals. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums.
By default in Windows 10, version and later, users can choose to set a lower level. You can control this behavior using the group policy setting, Configure telemetry opt-in setting user interface. Starting in version , Configuration Manager sets the following Windows policies for the Windows diagnostic data processor configuration :. Starting in version , Configuration Manager can configure the Optional limited level on the devices running Windows build version or later.
For more information, see Changes to Windows diagnostic data collection. For this diagnostic data level, Configuration Manager sets the following settings:. Don't also apply these settings in domain group policy objects. For more information, see Conflict resolution. If you ran the Upgrade Readiness onboarding script on a device, these policy settings may still exist. Don't use the legacy script.
Before you enroll the device to Desktop Analytics, remove these previous policy settings. In general, use Configuration Manager collections to target Desktop Analytics settings and enrollment. Use direct membership or queries to include or exclude devices from the collection. For more information, see How to create collections. Configuration Manager configures commercial ID and diagnostic data settings on your target collection. If you need to configure different diagnostic data settings for different group of devices, use group policy settings to override Configuration Manager settings.
For example, you need to set Optional limited level for some devices and Required for others. Some devices may have different proxy server authentication settings. When you use group policy settings to enable complex scenarios, pay special attention to policy settings that can cause configuration conflicts. Configuration Manager only configures Windows settings if the value doesn't already exist. Mobile device management MDM policies and group policy settings take precedence over Configuration Manager settings, so certain policy configurations could cause issues with Desktop Analytics.
Sorry this didn't help. Thanks for your feedback. Try removing the policies on the machine - this would remove every policy implied in the installation. In the search, type cmd, right-click on it and choose Run as administrator.
Paste the following commands:. I have the same question 0. Skip to content When your environment migrates from legacy or lower version of Windows Server to a newer version. Like this: Like Loading Author: sabrinaksy Just an ordinary lady who love what she does best.
Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in:. Email required Address never made public. Name required.
0コメント