Has anyone used a local variable %userprofile% for user homedirectory when adopting MS ONEDRIVE?

Hi

I am investigating how we could move away from configuring user accounts with homedirectory that are classic \\server\share\%username format to also allow the use of a local OS variable and string with a couple of spaces "%userprofile%\ONEDRIVE Company name"  (we don't specify the double quotes) and wondering if anyone else has tried this or similar sucessfully. We are using a new Property Generation and Validation policy for this attribute, and not the Global one that doesn't quite fit our multiple domain environment.

The ActiveDirectory Powershell module does allow setting this string and it works ok when we then have this used.

The native dsa.msc returns an error "The specified path is not valid. Enter a valid path using the form: drive-letter:\directory. " when we use the same string in its GUI. Active Roles also returns the same error from AD as the DSA tool does.

We want to keep the flexibility of users wanting to be able to have their profile from a non OS disk. The option of specifying a string such as c:\users\%username%\ONEDRIVE Company name has worked but wouldn't be our preferred combination is we can use %userprofile%.

Has anyone else moved away from homedrives on network shares and wanted to specify user settings in ways similar to this?

I am not aware if there could be configurations from ONEDRIVE that could affect a local user profile so that the homedrive attribute in AD for a user doesn't need any configuration. This might be an option if that could also work.

Thanks

Glenn