This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 73%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYM%3C/text%3E%3C/svg%3E)
Hello,
I am working on removing TargetReleaseVersion and TargetReleaseVersionInfo through Intune. For some context, a previous admin enabled this for a fleet of WORKGROUP joined devices that operated off of our corporate network. We did not have Intune or any other MDM at this time. Now, we have Intune and have had great success with the product so far.
I successfully created a detection/remediation script to find and delete the registry entries related to TargetRelease, but I am not sure how to over-write what is currently there in the local group policy settings through Intune, because if the local group policy setting is still set like it is in the attachment, the registry entries are re-created on the next GP update.
I tried CSP in Intune. I created a new policy assigned to my dev machine where I left the parameter blank to try and force Intune to clear out any existing values.
But the device sees an error in the event viewer, seems like it's unhappy that there is no value set in the CSP. So maybe that is where I'm going wrong. Is there a specific syntax for "null" or "nothing" for this CSP that I am not aware of? Or is there a better way to accomplish my goal.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 28.000000000000004%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECK%3C/text%3E%3C/svg%3E)
From my understanding, now that you have intune as the main MDM, you want to use intune and overrid. existing local GPO. Based on your described issue, and during my research i have come across a similar situation here. Additionally, The provided solution successfully resolved these issues for multiple customers.
Refer to : MDMWinsOverGP, This policy is used to ensure that MDM policy wins over GP when policy is configured on MDM channel.
Note:
If you find the answer above helpful, please Accept the answer to help anyone in the community who might have a similar question to quickly find the solution.
Hi
Thanks for the reply - this issue is a little strange because the issue is not that local GP is taking precedence, but that the local GP setting for TargetReleaseVersion was set manually before we had an MDM and it was not pushed down from a domain controller. The previous admin just configured the local group policy settings manually and then imported them to each device during the manual imaging process.
We are just trying to find a way to remove this policy administratively, so we don't have to go through hundreds of devices manually to correct the problem. We don't want TargetReleaseVersion set at all - it's causing problems with devices being out of date and unpatched.