cancel
Showing results for 
Search instead for 
Did you mean: 
Create a Post

Bluetooth Driver Confict with Endpoint.

Jump to solution

Hello,

I am trying to pair a Phillips Heartstart MRX device to a Panasonic Toughbook cf-19, running windows 10, and endpoint 80.82. I have a third party bluetooth driver installed, due to the increased security settings in windows 10 and bluetooth sharing. The MRX is very old school, and they are no longer making them anymore. The MRX is the device that initiates the connection to the laptop, and sends a passcode to it. you get a prompt like you should, but the area when you can input the passcode, is simply stripped out. Media and Port Encryption is 100% not enabled in the application, but it still should be active at the driver level, and there in lies the possible problem. I don't think i am going to find much documentation on this. Does anyone know if this would be supported? I have not tested to confirm, but i believe this could work with windows 7 using the native bluetooth drivers, which does have the sharing built in. to block the connection is one thing, but to strip out a passcode like this, suggests to me that this is not supported, or there is a conflict/incompatibility of some kind. We have compliance, full sandblast suite, FDE, and anti-malware enable. Without the Checkpoint software installed, this does work as expected. My plan forward is as follows.

upgrade to E80.83

I already disabled the FDE blade. no change.

I am going to continue with this path, and disable each blade one by one in the policy (since in deployment if i disable sandblast, it shuts them all down at once, and see if it works.Then i guess i can also go to disable the blade in deployment as well, if the no policy idea does the trick. This would allow me to find the problem active blade, if it exists. If not, I am going to find out what driver is being used, and push this up to CP TAC and or R&D. I will probably have to engage them in either case. Anyone else have any thoughts/Ideas?

Thanks in Advance,

0 Kudos
1 Solution

Accepted Solutions
Highlighted

Re: Bluetooth Driver Confict with Endpoint.

Jump to solution

Hi Marina, you saved me the time of going though and disabling each blade one by one. it was an order of operations issue. the bluetooth drivers came along first. If you remove everything, and then install checkpoint, and then the bluetooth drivers, it works as expected.

Thanks again!

0 Kudos
2 Replies

Re: Bluetooth Driver Confict with Endpoint.

Jump to solution

Hello,

Was the Bluetooth driver installed before or after Endpoint Client has been deployed to the machine? The direction to eliminate what Endpoint Blade can be related seems absolutely correct to me. I would suggest to open a Support ticket and get help from TAC team on investigation.

0 Kudos
Highlighted

Re: Bluetooth Driver Confict with Endpoint.

Jump to solution

Hi Marina, you saved me the time of going though and disabling each blade one by one. it was an order of operations issue. the bluetooth drivers came along first. If you remove everything, and then install checkpoint, and then the bluetooth drivers, it works as expected.

Thanks again!

0 Kudos