- CheckMates
- :
- Products
- :
- General Topics
- :
- Re: Central Deployment of Hotfixes using Smart Con...
- 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?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Central Deployment of Hotfixes using Smart Console
Central Deployment of Hotfixes
Deploying a package on several Gateways in parallel is now easy, intuitive GUI based.
Central Deployment allows performing batch deployment of Jumbo Hotfix Accumulators and Hotfixes using Smart Console.
You can deploy either the Recommended Jumbo Hotfix Accumulator or specific Jumbo Hotfix Accumulator take.
The name of the specific Jumbo Hotfix Accumulator can be found in the relevant SK article for the desired version.
The Management Server should be 80.40 and the Security Gateways can be any version starting 80.10 and up.
Notice that both Management and Security Gateway should be connected to Check Point Download Center.
R81 shall allow version update as well as local management of package repository, enabling central deployment without the need to be connected to Check Point Download Center
For detailed information, review the R80.40 admin guide: Central Deployment of Hotfixes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Very good - this is valuable, but - it is not CDT yet ! It has no logs for itself and only uses parts of CDT that call CPUSE on the target.
I have successfully installed Jumbo HFs on single Gateways, but:
- with 2200 Cluster, only one node was sucessfully updated, failover worked, but the installation on second node stopped and had to be finished manually ☹️
- on SMS, it proved to be the snake biting its tail ! After downloading the package, install started:
Then, Dashboard did disconnect from SMS. But in WebGUI, i saw:
Installation proceeded and unit rebooted. It took a long time until Dashboard connect was successfull, and the task window showed:
Seems it could not verify that the task had been successfull...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks very much for the inputs.
CDT has wide capabilities since it uses xml file to define a flow which can consist of installations, clish commands, scripts, file transfers and actually whatever you wish.....
This is the great power and this is what makes CDT a bit less intuitive and limited - you must edit xml files and use command line.
Regarding the two issues you encountered, I will appreciate more info in order to investigate
Will appreciate if you ping me on boazo@checkpoint.com as I have some questions I would like to ask.
The new development is aimed to be much more simple, intuitive and user friendly even if it means it has less options and configurations.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In this SmartConsole CDT, i assume that Dashboard calls CDT tools that trigger CPUSE on the Target. Drawback is that we have no central logs for the task.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The link given above to the R80.40 admin guide is incorrect.
Use this:
