Date: April 4, 2017
JetPatch 3.5 Includes the following features:
- Policy Enhanacements
- Connector Distribution by Policy Engine
- Additional Server Details - Installed Tools
- 'Package' State improvements
- Better Role Based Access control for Policy rules
As part of refreshing the look & feel and improving functionality, the policy rules have been moved to the new console and are now grouped by tool.
To create/edit a rule, go to the specific tool in the new "Tools" page that you would like to create a policy rule for, and click on the "Policy" tab.
Define the rule that you would like to create:
- A 'required' rule in order to apply the management server on the servers you have defined in your smart group.
- A 'ban' rule if you wish to prevent deployments on that management service on the servers you have defined in your smart group.
Once you select the rule type, simply fill out the relevant fields:
Use the drag & drop helper on the right to prioritize between rules.
Connector distribution by Policy engine
In order to simplify the upgrades and automate the process of updating the latest connector version, we have added the ability to automatically distribute JetPatch services using policy rules. To create a new rule, go to the new 'Tools' page and select the JetPatch service icon. Best practice for upgrading the latest version would be to scope the rule to a smart group created based on the managed servers only (Check Yes in 'Managed' column under servers tab).
Please note that if an JetPatch management service is not installed on an endpoint, and there is no rule for automatic distribution, JetPatch service will be installed only upon deploying the first agent management service.
For such cases you can define implicitly what service will be deployed from the old Policy tab under JetPatch Services.
Additional server details - Installed tools
From servers map of each tool page, you can now easily see which tools are installed on a server and what is the status of each one:
'Package' State Improvements
In uncommon cases an JetPatch service installation might fail and leave the service in package state, or service might lose its connection to the running agent. In JetPatch 184.108.40.206 we significantly reduced the probability this might occur, but also added indication for such cases. In servers tab, a service in 'package' state will have a package overlay icon, and if a policy rule exists, an exception will indicate that there is a package state on the server.
Please note that most of the 'Package' state occurrences are due to installation that has failed for various reasons (not necessarily JetPatch - related), and are probably very old. In order to fix the package state, you will need to install the service again (or new services of the same tool version).
Better role based access control for Policy Rules
In JetPatch 220.127.116.11, user can fully edit a policy rule if user has a permission to manage policy rules.
- Different tools with the same management service can now be applied by policy engine
- Fixed improper high disk consumption for a specific management services configuration
- Improved policy rules auditing
Transitions between the following Auto-fix modes will only take place when disabling and enabling the policy rule. Once / Moderate / Aggressive.