Forum Discussion
Windows 10 Update Ring configuration
Hi there
I configured the policy, assigned it to a AAD group (members are Windows 10 devices) but still after a few days the deployment status is unassigned (Windows 10 Pro 1803):
What did I wrong?
This device is also mentioned as "conflict" with a profile with device restrictions. Didn't work out yet how to solve this.
Other devices are pending, but they are not running right now, so that's fine.
On one device (Windows 10 Enterprise 1803), I was able to activate the Insider Program in the control panel, choose an account, did a restart and the insider build is downloading now. That machine is also in the AAD group.
Thanks and best
Udo
Hi Udo,
first of all a device configuration conflict will have the result, that the policy will not be applied at all. That's different in regards to compliance policies, there it evaluates to the most restrictive value and that's applied in the end.
Normally device restrictions do not have configurations which are in conflict to software update ring policies. Are you sure you are not conflicting with e.g. a custom OMA-URI policy?
best,
Oliver
I have one OMA-URI configured:
It's assigned, but pending for all machines, but I synced them (company portal)- hm I think I missed some understanding with policies here…
The above setting is for "MDM wins over GP", but as I'm not using any on-prem config I un-assigned the policy. Perhaps that helps already.
The policy with the conflict looks like this:
So all other devices are assigned, just not the last one.
What exactly do you mean by conflict. The UI tells us "not assigned". It looks like the device does not see the policy at the moment... the MDM html report on the device with not assigned is listing a conflict? Where do you see the "conflict" exactly?
