How are you blocking Wi-Fi/Bluetooth across HP fleets in enterprise without constant hardware ID maintenance?

Posted by charanreddy234@reddit | sysadmin | View on Reddit | 33 comments

Hi everyone,

I’m working on a requirement in our environment where we need to block Wi-Fi and Bluetooth on HP machines only, while making sure normal wired Ethernet/network adapters continue working without issues.

We manage the machines through Active Directory / Group Policy, and I’m trying to figure out the best long-term/enterprise-friendly way to do this.

We want to:

From what I’ve learned so far, blocking by hardware ID seems very accurate, but it only works if you know every Wi-Fi/Bluetooth hardware ID in the environment.

That becomes difficult because HP devices can have different wireless chipsets/vendors depending on model (Intel, Realtek, Qualcomm, MediaTek, etc.), and new/future HP models may introduce new IDs.

1. Blocking by hardware ID via GPO
Using:

Examples:

Concern:
Seems effective, but maintenance-heavy if we have to keep updating IDs for every model/new hardware.

2. Using class/compatible ID like PCI\CC_0280
My understanding is this may catch many wireless/“other network controller” devices.

Concern:
Not sure if this is reliable enough or if it may miss devices / affect unintended ones.

3. Blocking Bluetooth via class GUID
Using:

This seems easier/more straightforward for Bluetooth.

4. Disabling WLAN/Bluetooth services
Like:

Concern:
Feels more like a workaround since the device still exists and could potentially be re-enabled.

5. BIOS/UEFI disabling
said no to this approch.

My Question

For those who manage HP fleets in enterprise:

What’s the best real-world approach you use to block Wi-Fi/Bluetooth with the strongest coverage and least maintenance?

Specifically:

Looking for practical advice from people who’ve implemented this in production.

Thanks in advance.