MicrosoftOne comment on this - using the variable path '%systemdrive%\users\%username%\Work Folders' to reference the users profile is a REALLY BAD way to do it. In most cases, it'll work, but if for any reason the username changes or for whatever other reason the username doesn't match the folder in the 'users' folder, it'll cause problems. For example, when I first started experimenting with Work Folders, I had set it up like that. But when I first logged in, the 'special folders' weren't redirected into the Work Folders where they belonged. The reason was I had set up the PC with a local user 'Dave', and when I joined it to the domain, I logged in with my domain user 'Dave', so the domain profile folder was 'Dave.DOMAIN'. The folders redirected to the 'Dave' folder. Another example of where this could go sideways (even worse, really, if the user is established and has a bit of data), is say a user gets married and their AD logon is changed to reflect this...
The proper way to reference a users profile is using the %userprofile% variable, however, in GPOs, while using "%userprofile%\Work Folders\Desktop" (with the quotes) seems to work at least initially, when the group policy refreshes, the Target Folder Location gets changed from that variable to 'Redirect to the local userprofile location'. Without the quotes, it gets changed immediately. I haven't found a solution yet, but hopefully there's a way to properly reference a users profile in the GPO without it getting changed to point to the profile root.
