this post was submitted on 30 Nov 2023
494 points (97.9% liked)

Technology

59349 readers
5352 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] d3Xt3r@lemmy.nz 7 points 11 months ago* (last edited 11 months ago) (1 children)

In one of my previous roles as a sysadmin, our company signed a deal with HP to directly supply enterprise laptops to one of our clients as part of Microsoft's Autopilot deployment model, so users could get a new/replacement laptops directly and get it customized on the fly at first logon, instead of us having to manually build it the traditional way and ship it out. It worked fine in our pilot testing, so we decided to roll out to the wider audience.

However, one problem which arose after the wider rollout, was that SCCM wasn't able to connect to any of these machines (we had it in co-management mode), and even the laptops which were able to communicate previously, stopped communicating. It was working fine in our pilot phase, but something was now blocking the traffic to SCCM and we couldn't figure it out - it was all okay on the network/firewall side, so we thought it could be a configuration issue on the SCCM server side so we raised a priority ticket with MS. After some investigation, we found the root cause - turned out out to be this nasty app called HP Wolf Security - which was new at the time - which HP started tacking on to all devices, unbeknownst to us. Wolf was supposed to be an "endpoint protection" solution - which no one asked for, especially since we already had Defender. Searched online and found tons of similar issues reported by other users, all caused by Wolf. Lost some of my respect for HP since then - who tf pulls stunts like this on an enterprise level?!