this post was submitted on 23 Nov 2024
300 points (99.7% liked)
Technology
60090 readers
1798 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't understand how businesses that use windows for employee laptops are not throwing a fucking tantrum. I would be.
They already said it will be off by default for all Enterprise editions of windows. They're protecting their corporate buddies but normal users get fucked, as always.
Off by default. For now...
One step. The corps know it. It's been happening for years. One step, then soon after you just accept that's how it is. Then another step. And another. And another...
I actually really doubt it'd ever go on by default for enterprise installations. One tiny slipup in GPO and IT departments could end up with the most massive explicit data leak in history, many many companies and governments working with very sensitive data would drop all Microsoft products in a heartbeat. Microsoft knows that is an impossible sell and really not worth the squeeze vs just shoving a larger dildo up the private consumer's ass.
Microsoft Azure already leaks secrets and nobody cares. As long as it has all required certifications it'll be fine.
I get what you're saying, but:
Apply this same logic to 'Considerable and substantial direct access to the kernel for who knows how many third party software engineers, without meaningful or comprehensive review of how they're using that access.'
Why, one serious, overlooked error on a widely used enterprise software with this kernel access could basically brick millions of business computers and cost god knows how many millions or billions of dollars, they'd never do that!
... cough CrowdStrike cough.
I think you misunderstand the relationship Microsoft has with corporations. If they turn on something like this after the fact while promising to do the opposite previously they will get thoroughly railed in court and then no one will ever buy their products ever again.
The reason that companies use Windows rather than running everything on Linux is the absolutely enormous support base that Windows has. The moment it becomes more problematic to use Windows than to just deal with the support issues of a Linux OS is the moment that everyone will switch to Linux.
Work in the space, I don't misunderstand. Corps are one thing, what about the rest of civilization? Also some corps might even embrace as a means to spy on their employees work habits or something dystopian like that.
Not every business uses enterprise. I suspect quite a few use pro.
Then that will be Microsoft's captive audience upsell. "Ohhh don't want us collecting your secrets? Damn better pay up for enterprise licenses..."
Just because you're running pro doesn't mean you don't have domain policies.
Yes and no.
Enterprise has just lesser headaches and no need to customize the installation as much as the adware bloated default iso.
I'm just saying that you can turn recall off in GPO. As long as Windows pro machines are bound to the domain.
I checked my work laptop running W11. Recall was installed and enabled. No copilot+. IT had no idea. Disabled it right away.
They just turn it off with group policy or intune.
can't wait for the first "whoops, it accidentally got turned on beccause of a bug" news headline
This.
We did get pissed off, then turned on a GPO to block it
Even easier. It’s off by default in enterprise and education SKUs.
Ours is. Last I heard, our Client Management team is already looking for different ways to disable it and make triple sure it stays off.
(inb4 "Switch to Linux": several thousand users, specialised software and a technologically conservative company would already make that a non-starter)
I don't disagree that it would be tough, but they had to start from nothing when choosing Windows originally. It all had to be learned and built up at some point. It can again, and hopefully on an open platform that won't fuck them over in the future. (I know, there's no chance, but there should be.)
Everyone always complains that whatever they want isn't on Linux. Well, it wasn't on Windows at some point either. Make a user-base for it on Linux or make it yourself. Someone did it in the past. It can be done again.
Inertia is a hell of a thing to try and overcome. It's a big deal for most companies to change out an important piece of software, let alone an entire OS and everything that comes with it. It could happen one day, I just don't expect to see it.
I use Linux privately, and haven't had a Windows OS on my PC in years except for a VM I needed for a university project. I'm all for hoping that specialised apps get developed for Linux too. I like mine and would probably enjoy using it for private purposes too, but it won't work with wine and learning different tools is obviously an additional time investment in my free time compared to the one I get paid for learning.
But I'm both quick and happy to learn. Many people are not (and I see that daily with my users). The cost of switching and disruption in productivity would probably be disastrous enough to ruin the company even before considering the fact that "industry giant unable to fulfill contractual obligations because they have to rebuild half their infrastructure from nothing" would be a crippling blow to its professional reputation in an industry where IT is still considered second-class at best, the ideological gain of no longer depending on Microsoft would net them nothing and in an economic system where short-term profitability is more important than long-term independence.
And that's not considering the difficulty of convincing company leadership that Windows really is that bad and Linux really is much better and that we only need to provide the financial incentive and invest the time and money to have someone port already expensive software to a different platform. FFS, we're still struggling to get people to see IT as a service rather than an expense.
Finally, even if they were to switch out their entire IT infrastructure, they'd start asking whether it would be cheaper to outsource our internal IT to a company that already knows the new stuff than to retrain all of us. I'd very much like to keep my permanent position, even if it means using Windows.
I totally agree. I hinted towards what you've said in my comment. It still doesn't change the fact that at some point Windows was chosen and everything was built. The implies another choice could still be made. It's just not going to happen with an established company most likely. It would be nice to see newer companies that don't have the same inertia switch to Linux at least and start the transition. So much is stuck in a "business culture" that treats Windows as the only option though, but again this wasn't always true and can be changed again if enough companies started to transition.
Eh, between the financial expense, the human reluctance to change and the still very real barrier of "We can't migrate where there's nowhere to go" with respect to the software landscape, I think we need to compare our definitions of could. It's not just a business culture issue either. All change brings friction, but trying to replace the entire infrastructure of a company (and it has to be pretty much everything - one selling point of MS is how thoroughly integrated its products are) is basically ripping out most of the internal organs and replacing them with transplants, but also trying to keep the patient alive somehow... and you need to sell the people with the money on the idea.
Throwing away and starting over is costly, no matter the context. So no, I don't think larger companies can even make that choice at this point.
Smaller companies without the same inertia, in industries where there are Linux-compatible tools? Yeah, they can, provided the software they need is there too.
MS know who butters their bread. Businesses get given the tools to control windows properly. Even without needing to resort to LTSC versions, domain joined with group policy, you can manage all the shitty parts of windows to make it behave as you wish - even down to control over when you receive the updates
Businesses will embrace this. The data will be tied to the m365 data governance agreement.
It's because they want this. Microsoft Recall I am sure on a domain will be expanded upon to allow for auto capturing screenshots that can be parsed with AI to generate statistics of who is "working". Without the legal issue of saying "we don't install monitoring software".
Microsoft will slap a license on that bad boy and businesses will eat it up to use against employees they want to terminate for cause anyway because they slipped up viewing a video from manager who sent them a cat video to watch that is less than 30 seconds long.
The other is how businesses will be crying when the feds just use it against them for finding fraud in business because they never bought the "enterprise" license that limits sharing and that doesn't funnel everything to Microsoft anyway.