One Drive cr@p

Explain? You mean like multiple people working on a library as opposed to a SMB share?

Yeah that never goes well, for OneDrive or even SharePoint libraries.

Best to just block/hide syncing entirely and force users to work via browser. Otherwise with the client as soon as someone works offline or disconnects, it causes conflicts and versioning issues that users typically don't know how to manage or don't even observe.

Offline files with SMB shares had the same problem. Can't bypass laws of physics, can't have multiple streams of data trying to occupy the same space/file :)
 
Last edited:
Is it just me or does everyone have OneDrive come with arb errors that never occur with a normal SMB file share!!!!

Drives me nuts...

yip its crap.But i guess its the "modern" way of doing things.When it comes to IT i always belive Simpler is better.
 
if you not using sharepoint libraries etc then rather use azure file services (ie the cloud version of the traditional on-prem smb file server)
 
Explain? You mean like multiple people working on a library as opposed to a SMB share?

Yeah that never goes well, for OneDrive or even SharePoint libraries.

Best to just block/hide syncing entirely and force users to work via browser. Otherwise with the client as soon as someone works offline or disconnects, it causes conflicts and versioning issues that users typically don't know how to manage or don't even observe.

Offline files with SMB shares had the same problem. Can't bypass laws of physics, can't have multiple streams of data trying to occupy the same space/file :)
Yes, but never had any of this with dropbox...
 
if you not using sharepoint libraries etc then rather use azure file services (ie the cloud version of the traditional on-prem smb file server)
I've spent way more time figuring Azure Files out than I care to admit. :(
 
I've spent way more time figuring Azure Files out than I care to admit. :(

strange cause it works very well.Even got it to intergrate with my on prem AD , so its basically a cloud version of my local shared drive , with the same permissions , user, groups etc.
 
strange cause it works very well.Even got it to intergrate with my on prem AD , so its basically a cloud version of my local shared drive , with the same permissions , user, groups etc.

I got it AD integrated and working, that part was easy. But then figured out it only works with domain joined workstations. It won't auth from a non-joined PC by simply passing AD user creds like a normal file server would? So there goes working from home and all the benefits of the cloud :/

It also seemed to have strange auth issues depending on how I set the private endpoint and DNS handling, where it would just keep prompting for username, but I think I was just stuck in a troubleshooting rut at the time and needed some fresh air, I can't remember now exactly why I struggled so much, but holy hell did I get angry.

At one point I remember running some powershell testing over it and running through each error one by one as well. I was just totally demoralized by the whole first time experience with Azure Files, which is supposed to be so easy. Maybe just bad luck, or I lacked something fundamental in understanding.

EDIT: Now I vaguely recall I also had to re-create everything as I potentially seemed to have run into a rare issue at the time, which some forum post spoke about elsewhere.
 
Last edited:
Top
Sign up to the MyBroadband newsletter
X