Forum Discussion

Copper Contributor

May 13, 2020

Solved

WVD OneDrive Cannot Connect to Windows

Hi Folks We have a windows 10 Multi session WVD deployment. FSLogix with Office containers. OneDrive sporadically for a few users is coming up with this. "In Cloud" files. It seems that if you...

Doug_Coombs
May 14, 2020
rpextech , we have not seen this as a common issue with OneDrive and FSLogix. With a quick internet search I did find several references with trouble shooting/potential solutions, I am pasting a couple of links below. If these do not help solve the issue, I would suggest following up with the OneDrive community or submitting a OneDrive support ticket.

https://answers.microsoft.com/en-us/msoffice/forum/msoffice_drive-mso_win10-mso_2016/onedrive-cannot-connect-to-windows/a81e3866-d8d6-4186-90e0-2ddad547b4d2

https://pupuweb.com/solved-onedrive-cannot-connect-windows-error-files-on-demand/

Scott Windmiller

Copper Contributor

May 18, 2020

We have been having this same problem and have a similar setup. We are using a profile container as opposed to an office container for FSLogix. Ours is extremely random and does nothing with clicking try again.
I usually reinstall OneDrive with the /allusers switch to fix the problem. That fix may last a day if I am lucky.
We are trying to use Files on Demand to reduce costs in the profiles. We have limited the profiles to 5gb so that’s the max they can download from OneDrive to the profile.
Have not found a way to reproduce the problem.

rpextech

Copper Contributor

May 20, 2020

Scott Windmiller It seems to have gone away now or at least not been reported after latest Windows Update. Latest Version of FSLOgix and latest onedrive build.

I cant be sure really since users clicking "Download Files" makes the problem go away. It did seem to persist for specific users and not for others. If the user was suffering the problem. If i logged onto another host, the problem followed them, but if i rebooted the hosts the problem went away but then came back later. It was very odd. I think just updating everything seems to be key. Maybe its some combination of versions of products maybe. I logged a ticket with Microsoft but it wasnt very useful.