You’re thinking of Intel vPro. I imagine some of the Crowdstrike victims customers have this and a bunch of poor level 1 techs are slowly griding their way through every workstation on their networks. But yeah, OP is deluded and/or very inexperienced if they think this could have been mitigated on workstations through some magical “hygiene”.

If this were the case then “I fucked your dad” would be just as common an insult, with all the same connotations.

Australia uses kilopascals rather than PSI. Our standard is 500kPa which works out at around 72 PSI.

Dumb article title. I thought the trailer also showed some pretty tight writing that nails the Indiana Jones vibe pretty damn well.

45% of business leaders should not be business leaders.

Go look at all the Windows PCs announced in the last few months and you will see they have NPUs. So again, why would we wait until it is too late to try to stop this nonsense?

Also the “AI” may run locally but it saves the info into an easily accessible and readable SQLite database in the users AppData. It will be trivial for malicious actors to access.

Do you think it would be a better idea to wait until it’s installed and active on every Windows computer before we start a discussion on how bad Copilot is?

I follow Kevin on Mastodon. He’s the real deal and is absolutely not interested in the clicks or outrage. He’s trying to make it accessible.

“Megacorp siphons more money from customers to fuel never ending hunger for profit!”

“Every woman I meet is crazy” says person who works at a women’s mental hospital.

The OP is re-tooting a toot of a screenshot of a tweet. My (mild) criticism isn’t aimed at OP, nor the OP of the OP, just the original Twitter OP. No one was “blasted” but even if they were, the Twitter OP is not likely to see my comments and have a bad case of the sads from it.

It wouldn’t have been installed at all if the OP did their job properly and had set the one config option. Microsoft doing shady things is hardly news. That’s why a good Windows sysadmin keeps and eye out for this sort of stuff.

Like I said, Microsoft shouldn’t do that crap. BUT the co-pilot setting has been around for 6 months. Long enough for any halfway decent sysadmin.

There is one GPO to disable co-pilot. One. It’s not even hard to find and has been available for more than 6 months.

And yes I would absolutely expect someone whose job it is to manage Windows servers to know about it. And certainly, I would expect them to look it up before declaring to the world how bad at their job they are.

Remember cable TV? How it used to be good but then went to shit due to greed and you were disappointed?

And do you remember streaming TV? How it used to be good but then went to shit due to greed and you were disappointed?

OK. So now, like, we go back to cable TV, but this time you won’t be disappointed because it will be shit right from the start. Genius!

This stuff always makes me laugh. Firstly, yes absolutely, Microsoft shouldn’t do this sort of crap. But more importantly, the person complaining about it here is shouting out for the world to hear “I don’t know how to manage Windows servers properly!”. There is one single group policy setting that stops this from happening. A single, set-and-forget GPO. Anyone managing Windows environments that isn’t aware of this, shouldn’t be managing Windows environments.

I’m in the southern hemisphere. The entire planet earth was in my way. :-)

I had an entire planet in my way, didn’t see a damn thing.

“Gorgeous“?!

A 12m stainless steel pedestrian bridge that took 6 years to make and was subsequently “strengthened” to meet safety requirements. Not quite the same thing.