787
Windows users keep losing files to OneDrive, and many don't know why (www.techspot.com)
submitted 9 months ago by to c/technology@lemmy.world
239 comments fedilink hide all child comments
 

When Windows users suddenly discover that their files have vanished from their desktops after interacting with OneDrive, the issue often stems from how Microsoft's cloud service integrates with the operating system. The automatic, near-invisible shift to cloud-based storage has triggered strong reactions from users who find the feature unintuitive and, in some cases, destructive to their local files.

you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 9 months ago (3 children)

I work for a huge organization and my local IT guys have their hands bound. I couldn't even make a ripple in that ocean even if I tried.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 9 months ago (2 children)

    I'm sorry, that sucks. It really only takes about ten minutes to search up the settings to turn off the saving redirection in Office programs and toss it in the default Group Policy settings, but I'm sure that at a huge org that would end up stuck in absurd change review hell that IT folk seem to try and avoid.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 9 months ago (1 child)

    the thing is.... you shouldn't have to "search up the settings to turn off the saving redirection in Office programs and toss it in the default Group Policy settings". cloud shit in windows and ms office needs to be optional, and explicitly opt in

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 9 months ago*

    I don't disagree, but corps are going to push the settings in their software and products that makes them the most money. It sucks but should be expected.

    It'd be better if there were competitve open source options with the same ease of use, of implementation at scale, and ease of management at scale, but unless you're willing to do custom forking and dev work, most of the time it's easier to go with whatever is the overwhelming standard is and work around the rough spots, as at least then you'll almost never be in completely uncharted waters.

    I spent a few years building a custom solution for integrating a semi-popular but still relatively new HRIS system with a hybrid AD/Entra environment with a somewhat unique hybrid Exchange (email) setup. Doing it live, no real documentation to speak of because the few other places that had done it turn out to be consulting groups that sell their solutions for ridiculous amounts of money. My workplace has now hired an entire team and spent at least half a mil on a new software suite that will replace my solution eventually, after more dev work by this new team.

    That was after I burned a year trying to figure out how in the hell I could programatically try to clean up a horribly misconfigured and mismanaged old SolarWinds Orion setup that had accumlated tech debt for years, only to be stymied because they don't allow public discussion of their fucking database structure, and what I found out myself was batshit. Don't trust software that use their own custom bastardization of SQL.

    After those experiences I'm pretty damn content to stay in the land of "well documented and popular" and just work around the rough edges. Keeping up with patch and update news and delaying updates a little usually gives plenty of time to effectively opt-out by changing the settings before it hits our environment at large.

    Fuck Microsoft's bullshit, but at some point it's the enemy you know, especially in a corporate environment. I'm no stranger to masochism through tech work, but I've gotten used to MS's brand of fuckery, as a lot of us have.

  • permalink
  • fedilink
  • source
  • parent