- Products
- Learn
- Local User Groups
- Partners
- More
Policy Insights and Policy Auditor in Action
19 November @ 5pm CET / 11am ET
Access Control and Threat Prevention Best Practices
Watch HereOverlap in Security Validation
Help us to understand your needs better
CheckMates Go:
Maestro Madness
Why is a license taken up for the Endpoint client when the computer is moved to the Deleted Users/Computers directory in the SmartEndpoint console? Is there a way to purge this on a scheduled basis or have it remove the active license when placed in this directory?
It will automatically do so after 30 days.
More specifically, it will do it for any host that does not communicate with the management server in 30 days.
If you need to do it sooner than that, you will need to contact the TAC: Contact Support | Check Point Software
Dameon, can you direct me to an sk that contains the commands/process to preemptively release the licensing? I've had Endpoint techs do it for me in the past and I would like to know what commands to run on my own, if needed.
Unfortunately, the commands are in an internal SK, which means I cannot share them.
If we have remote laptops that don't get used often, what happens if the CheckPoint Management Server automatically deletes that laptop after 30 days, what will happen if the laptop gets used again? Will the management server give the license back to that endpoint or break the endpoint on that laptop?
We did used to have this issue with a previous version. Before we disabled a particular feature, users were getting locked out of their laptops due to inactivity, essentially. (Some had workstations AND laptops and neglected their laptops.)
In theory, they should get the license back when they "phone home" (assuming one is available).
Is there a way to mass delete users/computers from the Deleted User/Computers folder within the management console, rather than having to do them one by one? Or a job that can purge them after so many days?
Thanks
It's similar to what I said in the first response in this thread:
OK thanks, I'll log a call with TAC because that isn't happening. If we don't manually delete them then we end up with hundreds of old machines and users, many of which are 6 months old.
Thanks
The Endpoint server will (by default) clear monitoring information about users/machines from the database every 30 days. This is information like the last contacted IP, blade status, encryption status, etc. The license being used by a device will not be cleared from the database unless the object is reset from the console or cleared from the database by other methods.
what this means - If machines have not contacted the server in 30+ days you will get blank information about the blades on the device when you click on it in Users and Computers. Any license being used by this device will still be used until you reset/delete the object.
To the question about clearing this information faster than one by one - For servers older than R80.20 we have support tools and processes for clearing this information but I would recommend opening a support ticket so we can make sure it will work for your situation. For R80.20 these tools come with the server but I would still recommend getting with support so we can assist.
Hi Michael, I'm having this exact issue, could you let me know where i can find the tool in R80.20?
Thanks
Jamie
Deletion is an operation which should be performed with extra care, based on this - such procedures are not public and can be provided only by TAC.
Please open to us relevant service request and we will provide with a procedure to perform the desired maintenance.
There is one possible issue which could prevent automatic purge of inactive devices - if the database contains duplicate devices - and in this situation once again - SR should be raised.
If a device got deleted manually or automatically - if it will communicate with the server again - the system will not allow them to connect with error " Not found in PAT" error in server_messages.log.
Such device can be reinstalled or reconnected.
TAC can provide a reconnection procedure.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
Wed 19 Nov 2025 @ 11:00 AM (EST)
TechTalk: Improve Your Security Posture with Threat Prevention and Policy InsightsThu 20 Nov 2025 @ 05:00 PM (CET)
Hacking LLM Applications: latest research and insights from our LLM pen testing projects - AMERThu 20 Nov 2025 @ 10:00 AM (CST)
Hacking LLM Applications: latest research and insights from our LLM pen testing projects - EMEAWed 26 Nov 2025 @ 12:00 PM (COT)
Panama City: Risk Management a la Parrilla: ERM, TEM & Meat LunchWed 19 Nov 2025 @ 11:00 AM (EST)
TechTalk: Improve Your Security Posture with Threat Prevention and Policy InsightsThu 20 Nov 2025 @ 05:00 PM (CET)
Hacking LLM Applications: latest research and insights from our LLM pen testing projects - AMERThu 20 Nov 2025 @ 10:00 AM (CST)
Hacking LLM Applications: latest research and insights from our LLM pen testing projects - EMEAThu 04 Dec 2025 @ 12:30 PM (SGT)
End-of-Year Event: Securing AI Transformation in a Hyperconnected World - APACThu 04 Dec 2025 @ 03:00 PM (CET)
End-of-Year Event: Securing AI Transformation in a Hyperconnected World - EMEAWed 26 Nov 2025 @ 12:00 PM (COT)
Panama City: Risk Management a la Parrilla: ERM, TEM & Meat LunchAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY