Meaning the client won't be downloading all files (even files-on-demand) every time they log in to a new VM.
Everything gets redirected into a VHDX and therefore provides the "data persistence" on a non-persistent VDI. And as mentioned in the blog, there are some benefits with the method, the profile bloat, and performance impact during logon are gone.Īs FSlogix was recently bought by Microsoft, I highly suggest checking this out as it will benefit the manageability and the overall UX of OneDrive. Certainly with the latest Machine based installer the setup is a lot cleaner as it used to be with the user based installer. I have a couple of customers that have been running this setup for a couple of months without any issues. If we don't include the file "C:\Users\%username%\OneDrive - vmware\.*" Onedrive will ask the user at every login that the folder has been replaced, so you can choose to retry or setup onedrive again.Īs mentioned by Anobi圆7 and JohnTwilley, I have made 2 blog posts on installing OneDrive into both non-persistent VDI (W10) and RDSH deployments. HKEY_CURRENT_USER\Software\Microsoft\OneDrive\ C:\Users\%username%\OneDrive - vmware\.* the following folders and registry settings to provide SSO will be saved. # to avoid warnings that the onedrive folder has been removed or replaced. We have managed the following configuration with Ivanti/Appsense With the new client installed on the local machine instead of installing it under "appdata/local" and doing some additional configuration it works.Īfter testing some days, we have noticed that after a user uploads content to Onedrive from the local physical machine and logged in directly with a new session in VDI, all the old content will be deleted in the cloud and only the recent uploaded files shows up for on-demand!!! within the virtual desktop Working on a Windproject and one of the requirement was to make Onedrive available in a non-persistent VDI environment
0 kommentar(er)
