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?!
Yeah, I really like the hardware of ProBook/EliteBook but the software is atrocious when used with the default Image.
For Small Companies, I kinda like Wolf Security, as it has some nice sandbox features, but for medium-size companies where you already have an security endpoint, I think it’s more of an issue.
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?!
Yeah, I really like the hardware of ProBook/EliteBook but the software is atrocious when used with the default Image.
For Small Companies, I kinda like Wolf Security, as it has some nice sandbox features, but for medium-size companies where you already have an security endpoint, I think it’s more of an issue.