- CheckMates
- :
- Products
- :
- Harmony
- :
- Endpoint
- :
- Endpoint Policy Changes that Require Reboot
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×
Sign in with your Check Point UserCenter/PartnerMap account to access more great content and get a chance to win some Apple AirPods! If you don't have an account, create one now for free!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Endpoint Policy Changes that Require Reboot
Is there a list of endpoint policy changes that require an immediate reboot?
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I don't believe any policy change to existing active blades on a device requires a reboot.
Deploying a new version and/or activating/deactivating blades may require a reboot in some instances.
Deploying a new version and/or activating/deactivating blades may require a reboot in some instances.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I know changes to any FDE policy rule will force an immediate reboot. Got nailed by this in the past.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
FDE is a special case insofar as it's working on data encrypted on the boot volume.
To change whether data is encrypted or not or how it's encrypted, that must be done before the OS boots.
That necessitates a reboot.
To change whether data is encrypted or not or how it's encrypted, that must be done before the OS boots.
That necessitates a reboot.