OneDrive Enterprise Ring Issue

Copper Contributor

Hi all,

Is anyone else trying to use the Enterprise Ring for OneDrive?

For the life of me I cannot get our machines to respect the group policy "GPOSetUpdateRing" (we have it set to 0 for Enterprise as per documentation.

The OneDriveSetup.exe that we have deployed in SysWOW64 is 18.222.1104.0007 (current enterprise release) however when a user logs in this is what happens:

18.222.1104.0007 is installed from SysWOW64 as per usual (great! now just stop please!)
but no! OneDrive Launches, detects an update and updates to the latest production 19.012.0121.0011

All of our other policies for OneDrive are working like auto config no personal accounts etc..

I also tried the legacy GP they said not use any more (in the documentation) "EnableEnterpriseUpdate" set to 1
That didn't work either.

Any thoughts?

10 Replies


I also have this issue. Have you got it work now?

@CurtisI'm seeing similar behaviour. GPO is applying fine, other setting work and the reg value you've referred to is applying but the client is still auto updating to the "Production" version instead of "Enterprise".


I'm early on in testing this but already the details documented by Microsoft don't match what I see in the ADMX and this particular setting doesn't appear to be working.

@CurtisThe same issue also.

Not sure if it is related, but I can't even configure OneDrive policies anymore with the latest admx files from 19.086.0502.0006

GPO Error when loading the administrative templates:

Resource '$(string.GPOSetUpdateRing)' referenced in attribute displayName could not be found. File \\<name of dc>\SysVol\\Policies\PolicyDefinitions\OneDrive.admx, line 23, column 235
I also get this error now after applying the new ADMX template, i am assuming this has been superseded by another setting.
Any idea on how to fix this?

@Ivan Unger 


I had the same issue until I realized I placed both files (admx and adml) in the PolicyDefinitions folder. When I moved the adml file to the En-Us folder everything was fixed.

Same for me.. 

Thanks, no idea how I missed this, afters years of working with admx files :p

@Dimos_Panousis Thank you! :stareyes:


Just followed the documentation blindly and didn't even think about that.