Version: 3.3
New FeaturesJetPatch version 3.3 includes the following new features:
Support for OS Versions in Management ServicesNow tools can be limited not only for Windows/Linux OS families but also for a more granular resolution, such as Windows 2012, Ubuntu, or Ubuntu 6.0. When a tool supports a set of operating systems JetPatch will allow a deployment of that tool only on servers of the defined OSs. The supported operating systems of a Management Service can be found in the Library tab per agent under the General Settings of a Management Service. Notice that AWS servers report the OS family only (Linux/Windows), and only after a server is being managed, JetPatch will find the exact OS and manage the server accordingly.
Support for Tools Replacement (Upgrade)Now you can easily upgrade a tool to a different version in two ways:
Major Scale ImprovementsNow JetPatch can officially support 30k servers per JetPatch Server We increased the number of supported servers in the Tools Overview page to be scalable by adding scroll functionality in the servers map and significantly improving performance. Tools Report WidgetThe new Console Dashboard now summarizes a chart with the status of all tools. You can filter to focus on the relevant tools and download the data as a CSV report.
Support for AWS RDSNow you can run JetPatch with an AWS-managed PostgreSQL using the RDS service and enjoy the high availability mode it offers.
Improve Support for Pre-installed ConnectorsNow if the connector is pre installed on the server you won't be required to enter the server account anymore.
VM Templates Are Now Excluded from the Servers ViewIf you use VM templates, they will now no longer appear in the Servers tab.
Added More VM VariablesDatacenter and Cluster names are now available as new columns in the Servers tab.
Alert to Prevent Accidental Change in JetPatch URLIf a user chooses to change the JetPatch connector on a server, a warning will now appear before the change in order to make sure that the new URL given is the correct URL that the connector should report to. |
Comments
0 comments
Please sign in to leave a comment.