- Products
- Learn
- Local User Groups
- Partners
- More
Check Point Jump-Start Online Training
Now Available on CheckMates for Beginners!
Why do Hackers Love IoT Devices so Much?
Join our TechTalk on Aug 17, at 5PM CET | 11AM EST
Welcome to Maestro Masters!
Talk to Masters, Engage with Masters, Be a Maestro Master!
ZTNA Buyer’s Guide
Zero Trust essentials for your most valuable assets
The SMB Cyber Master
Boost your knowledge on Quantum Spark SMB gateways!
As YOU DESERVE THE BEST SECURITY
Upgrade to our latest GA Jumbo
CheckFlix!
All Videos In One Space
I'm having a problem with EndPoint. What happens is that I added a device to a white list and in this case this release only worked for machines with windows 7, but with windows 10 it doesn't work. The current version is 86.20.
Might be worth a TAC case to make sure what's showing in the logs is what we are enforcing in the client.
Meanwhile, I'd try what's showing in Windows 10 and see if that works.
Perhaps the device has a different identifier in Windows 10?
In which case, you would need to add a different device to cover whitelisting it in Windows 10.
Hi Phoneboy. I'm categorizing the devices following the category that is showing in the client logs, in the 'view logs' option. In that case, should I then base myself on the category the operating system recognizes (win10) then and not the EndPoint's?
Might be worth a TAC case to make sure what's showing in the logs is what we are enforcing in the client.
Meanwhile, I'd try what's showing in Windows 10 and see if that works.
what was initially not informed to me is that a hub was used between the device and the computer. In this case, updating the device drivers to recognize the hub on win 10 and releasing the hub on the endpoint made the release work successfully. Thanks for your help.
Thanks for the answer.
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY