this post was submitted on 24 Nov 2024
581 points (95.7% liked)
PC Master Race
14998 readers
64 users here now
A community for PC Master Race.
Rules:
- No bigotry: Including racism, sexism, homophobia, transphobia, or xenophobia. Code of Conduct.
- Be respectful. Everyone should feel welcome here.
- No NSFW content.
- No Ads / Spamming.
- Be thoughtful and helpful: even with ‘stupid’ questions. The world won’t be made better or worse by snarky comments schooling naive newcomers on Lemmy.
Notes:
- PCMR Community Name - Our Response and the Survey
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
My employer is in the process of decommissioning all their on-premises storage and shifting all data into the many-headed hydra that is OneDrive/SharePoint/Teams/Azure. It's going... not great. Automatic file locking for non-Office applications doesn't exist in the context of SharePoint and people are losing hours of work when two people had the same file open all day without knowing. Projects that had large, complicated folder structures have whole swathes of files that cannot be edited because of path length restrictions rearing their ugly head ("C:\Users\Username\OneDrive\VerboseHumanReadableProjectNameAndNumber ends up being quite a bit longer than P:\ProjectNumber, whodathunkit?!). Nobody's sure of they should be syncing or linking their project directories locally. Some options for file management appear in SharePoint views of shared folders, but not Teams.
As a tool for portable user profiles or casual filesharing or syncing, it's fine, though I'd prefer if MS didn't force it into Windows and Office apps by default. As the core of a complex international business operation? Fuck this I hate it desperately, and I cannot imagine any way in which it's going to save the business money over keeping storage in house.
They saw $$ savings projected. They didn't realize they'd need cloud engineers to manage it. Savings gone.