Reply to Message

View discussion in a popup

Replying to:
tbro
Enthusiast
Enthusiast

Our use case is a little bit different, but I was just able to get the OneDrive client working in my pilot environment and the only catch seems to be that users need to enter their email address to sign in each time.

We are using LTSB, so no Files on Demand for us, but I think this approach would still work.

First off for UEM I am using the settings provided here by JohnTwilley​. I have placed the exe for the OneDrive client on my parent image and am using a logon script in UEM to install the client for our users.

Now, since Files on Demand is not an option, we needed to deal with the OneDrive cache, so that we didn't have to download all our files each time we log in. On my parent image I created a "OneDriveSync" folder on the root of C and then modified the security of this folder so that the Users group would have full control of this folder. Using the OneDrive GPO settings I set the default folder location for the OneDrive folder to map to the "OneDriveSync" folder and disabled the ability for our users to change the location of the OneDrive folder.

Since our users get a writable volume, I then modified the config file and added the below line at the top.

################################################################

# OneDrive Cache

################################################################

virtualize=\OneDriveSync

In this scenario the cache follows our users as they log in and out and they are not getting the scary looking error message that "the onedrive folder is not your original onedrive folder"