Forum Discussion
Syntax for Onedrive.admx edits - DefaultRootDir
I was just having this exact discussion with my client earlier this week. We have not been able to get it work either.
On a related note, how many GPOs do you create? I am thinking that 3 - one for User Configuration, one for Computer config and one for Folder redirection, will provide long term maintainability, but we are having some deployment problems, and I'm wondering if it would be better to just have one. Any thoughts on this would be appreciated.
I'll have an article out next week about my approach, but in summary, let's say there's one folder redirection policy already in place. I'll create one Onedrive GPO, that contains settings to create a custom environment variable, create the Onedrive sync folder, set the Onedrive settings, and change the folder redirection to the new location (including moving the data). The GPOs are filtered/denied etc so that when users are added to the appropriate group the old one stops applying and the new one applies instead.
Separating them makes sense if it's a more complex environment or requirement, but for most cases the "migration" to Onedrive just becomes a matter of dropping users in the group, advising them to launch Onedrive and complete initial setup, and monitoring network impact.
No OneDrive product team folks here I guess.
The problem is that the .admx template wrongly adds to the registry a REG_SZ instead of a REG_EXPAND_SZ, so the former does not expand the environment variable.
You can verify it by yourself, changing manually the type in the registry: you will find that REG_EXPAND_SZ works perfectly.
So the template must be edited manually to work, at least until someone at Microsoft will correct it.
Hope it helps...
