Forum Discussion
Paul Cunningham
Mar 09, 2017Steel Contributor
Syntax for Onedrive.admx edits - DefaultRootDir
In the Onedrive deployment guidance we're instructed to edit the Onedrive GPO template (Onedrive.admx) to insert specific values. For example, replacing {INSERT YOUR TENANT'S GUID HERE} with our ...
Ronak Shah
Microsoft
Sep 22, 2017The ADM files will be located in your %localappdata%/Microsoft/OneDrive/<build version>/adm directory. You can navigate to %localappdata%/Microsoft/OneDrive which will have the build version folders that contain corresponding ADM packages.
Thanks,
Ronak
Thanks,
Ronak
Adam Fowler
Sep 23, 2017Iron Contributor
Awesome, thanks Ronak - although I'll wait till Monday ;)
- John MarshallSep 25, 2017Brass Contributor
This sounds very promising. I'll have a look for the technical documentation so I can understand how to make best use of the templates.
Thanks!
- Jonathan ConwayOct 04, 2017Brass Contributor
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?
- Jonathan ConwayOct 10, 2017Brass Contributor
Jonathan Conway wrote: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?
This was user error on my part - although the client version for my admin account had updated to the latest version, the standard user account was unable to access the update servers and was therefore stuck on an earlier client version which did not support the new GPO settings. Once updated, the GPO applied as per design.