NotarySojac
New member
- Local time
- 2:30 AM
- Messages
- 2
You know the "a bluetooth device is trying to connect click to allow this" balloon that pops up from what used to be called the System Tray? A year or so ago that stopped popping up for all our users that have locked down systems.
Policy Admins say the group policy has not changed and nothing in effect should block those alerts. But they are being blocked, and we'd like to figure out what's blocking them.
A little background - these Dell Optiplex 3010 & 3020 PCs are in a domain environment. There are separate network accounts used on each PC and that account is in the matching machine's local Administrators group - all due to required ancient software. So PC01 is logged into using account user01, and so on. We don't want the users to mess with the environments so group policies & regedit keys prevent them from seeing or accessing the Control Panels, Task Manager, etc. All machines also have a local administrator account so we can do setup, maintenance, etc and it is not subject to the group policy and regedit lockdowns.
So back to Bluetooth. Most of these PCs have a Bluetooth dongle and a Bluetooth barcode scanner. For unknown reasons the scanners lose their connection to the dongles every once in a while - some lose it every few days, some stay connected for a year at a time. In the past, a few minutes after the scanner loses it it tries to reconnect and the "a bluetooth device is trying to connect click to allow this" Taskbar Notification Balloon pops up and these locked down users could click it and get to the Allow button to get their scanner back instead of calling the Help Desk to reconnect them.
As I said, about a year ago that Balloon stopped showing up for them. If we come out and switch to our local admin account the Balloon soon pops up and we can click Allow, let it connect, log ourselves out and the users can go back to their barcode scanning.
Because it worked, then it didn't, and we did no software changes other than Windows updates, we suspect some M$ update is interacting with group policy or regedit keys in an unanticipated manner.
Has anyone here encountered something like this, or has a deep enough gp/regedit understanding to point us in a promising direction?
Policy Admins say the group policy has not changed and nothing in effect should block those alerts. But they are being blocked, and we'd like to figure out what's blocking them.
A little background - these Dell Optiplex 3010 & 3020 PCs are in a domain environment. There are separate network accounts used on each PC and that account is in the matching machine's local Administrators group - all due to required ancient software. So PC01 is logged into using account user01, and so on. We don't want the users to mess with the environments so group policies & regedit keys prevent them from seeing or accessing the Control Panels, Task Manager, etc. All machines also have a local administrator account so we can do setup, maintenance, etc and it is not subject to the group policy and regedit lockdowns.
So back to Bluetooth. Most of these PCs have a Bluetooth dongle and a Bluetooth barcode scanner. For unknown reasons the scanners lose their connection to the dongles every once in a while - some lose it every few days, some stay connected for a year at a time. In the past, a few minutes after the scanner loses it it tries to reconnect and the "a bluetooth device is trying to connect click to allow this" Taskbar Notification Balloon pops up and these locked down users could click it and get to the Allow button to get their scanner back instead of calling the Help Desk to reconnect them.
As I said, about a year ago that Balloon stopped showing up for them. If we come out and switch to our local admin account the Balloon soon pops up and we can click Allow, let it connect, log ourselves out and the users can go back to their barcode scanning.
Because it worked, then it didn't, and we did no software changes other than Windows updates, we suspect some M$ update is interacting with group policy or regedit keys in an unanticipated manner.
Has anyone here encountered something like this, or has a deep enough gp/regedit understanding to point us in a promising direction?
My Computer
At a glance
Win7Pro-32, Win7Pro-64
- Computer type
- PC/Desktop
- Computer Manufacturer/Model Number
- Dell
- OS
- Win7Pro-32, Win7Pro-64
