Syntax for Onedrive.admx edits - DefaultRootDir

I have trialled the new ADMX files that are included with the latest production client and have found an issue with the "Prevent users from changing the location of their OneDrive folder" setting not working.

I have added the Tenant ID in the "Value Name" field as instructed and added the value "1" in the "Value" field. Sadly users can still click on the link to change the location of the OneDrive folder during the intial OneDrive setup.

Any ideas Ronak or anyone else?

Well, after doing some additional testing, i was able to finally get the gpo to behave the way i wanted:

I was able to create the directory C:\OneDrive via GPO, and set this as the default when OneDrive first launches.

The reason we are doing this is a little long-winded, and since I have your attention, I would love some feedback on our use case:

For 90% of circumstances, it wouldn't matter if the OneDrive folder was buried in the user's directory, however, we have a few applications in our environment, AutoCAD and Adobe InDesign as two examples, that rely on literal pathing to fetch resources. This was fine when the resources were stored on a file server and made available either via UNC or a mapped network drive, the file was always stored in the same path, and any user that needed to open them would have no issues.

Well, OneDrive introduces a challenge here because the default storage location is unique to each user, which breaks that literal pathing. From a performance perspective, these applications are not very latency forgiving, and fetching the content directly from cloud storage just isnt a viable option, and some of these applications don't support HTTP addresses or even understand web protocols.

Secondly, we have been eagerly awaiting the release of Windows 1709 and the promise of Files On Demand, our initial testing honestly has us incredibly excited, its an amazing bit of engineering, we are actually now planning on migrating close to 90% of our file server content to SharePoint Online.

However, the catch we've noticed is that Files On Demand, since it writes directly to NTFS now to track sync status in attribute form, it takes quite some time for that content to be fully represented, its fast certainly, somewhere in the order of 3500 objects per minute, but when you're connecting to a document library or several that altogether contain over a million objects, it would take several hours before FoD finally wrote all theat data to disk, even if it was just "Online Only"

our hope, and i'm almost certain im going to be breaking something by doing this, is that if we wrote that data in a common directory, we could still be able to present the content on workstations that are shared or ad-hoc, like conference rooms where you never really know who is going to log in, and already have a representation of the online document library written to a spot that the next user's onedrive client could consume it.

ideally, it would be great if there was a way to speed up this initial sync of libraries in FoD, but i'll take what i can get at this point.

if i'm just crazy just let me know, but i'd love to hear back thoughts on our approach.