Release information five(9)s Console 4.7

With a dual patch process, you can differentiate between high priority patches and regular patches. By defining rules that identify which patches are critical, you can prioritize the most important updates and ensure they are applied quickly. While also having the possibility to manually move currently running patches to a FastTrack Rollout. This means that any vulnerabilities or exploits that could be used by attackers to compromise your systems are addressed as soon as possible, reducing the risk of a security breach.

This also allows you to streamline the patching process for high priority updates. By configuring the process to be shorter and more focused, you can finalize the browser updates before a new one arrives.

• Rules to define patches as FastTrack
• Duration of the patch steps
• Number of pilot steps
• Approval of the steps
• Assignment of pilot test devices
• Scheduler for starting the patch operation

1. Flexibility: A scheduler allows you to schedule events at specific times, with specific intervals, or based on rules for the day or week.
2. Prioritization: Different schedulers allow you to prioritize patches and ensure that high-priority patches are scheduled first. This can be particularly useful in situations where you need to ensure that critical patches are completed in a timely manner.
3. Improved accuracy: A scheduler can provide more accurate timing compared to an interval-based event caller, that may not align with your specific requirements of each event. Additionally each Patch Group can use the global scheduler or a group specific one.
4. Resource management: A scheduler can help manage system resources by avoiding scheduling events at the same time or conflicting with each other. This ensures that each event runs smoothly and doesn't interfere with other important processes.
5. Patch Tuesday: Our scheduler allows to start patch processes after patch tuesday with a specific delay. This ensures that all patches have been downloaded and are deployed in a timely manner.
6. You can control and gather the patches to have one rollout over the course of one week. No more 6 rollouts per day and user complaining.
7. You can still use an workflow which needs to be approved with quality insurance so that you do not run into situations which can block your entire IT.

1. Patch Rollout notification for assigned users (configurable)
2. Pilot Notification for each pilot for admin (configurable)
3. Individual notifications of pilot users (can be configured for each user)

Frameworks
    • .net Framework 4.8

Upgrades
• We always strongly recommend to create
    ◦ a Database backup of the EPM DB