Events

Currently Available Event Types

• New Version Detected (default): Prompts a deployment process to run whenever a newer software version is detected 
• Patch Tuesday: Schedules a deployment process to coincide with Microsoft's Patch Tuesday releases

Future Recast releases will add more scheduled event types.

Active vs Inactive Events

Once you've created a scheduled event, you can set it as the 'Active' event for a deployment process, meaning that the schedule will override the default New Version Detected event. 

Active events linked to a deployment process are additive. For example, when a deployment process has the New Version Detected event and a Patch Tuesday event, it will run whenever either of those events occur. If you want the Patch Tuesday event to trigger the deployment process, you must deactivate the New Version Detected event or unlink it from the deployment process. Otherwise, the New Version Detected event will run by default as soon as a new version becomes available.

On the Deployment Processes page, the Events column displays the number of active events followed by the total number of events.

In this example, the Recast Agent deployment process is linked to 1 active event. But there are two events in total, meaning that one event is inactive.

By default, a deployment process will run as soon as Right Click Tools Patching detects a new application version in the Application Catalog. By adding a scheduled deployment process event, you can choose when deployment processes occur.

To view all deployment events, navigate to the Patching Events page.

Event details:

• Event Type 
  • New Version Detected (default) - Triggers a deployment process when a new software version is available in the Patching catalog 
  • Patch Tuesday - Currently, 'Patch Tuesday' is the only available scheduling option. Microsoft's security update release occurs on the second Tuesday of each month. Future Recast releases will add more scheduling types.

• Event trigger - 'New Version Available' or 'Patch Tuesday' (+ a delay)
• Description
• Count of Deployment Processes initiated by this event - displays the number of active and inactive deployment processes
• Actions
  • Edit Event - Choose to activate or deactivate an event, or edit event details
  • Click the ellipsis(...) and select Delete Event, then confirm the deletion.
    NOTES:
  • You can also edit an event by clicking the Events link on the Deployment Process Details page.
  • You cannot edit the default New Version Detected event.

By default, deployment processes run whenever Right Click Tools Patching detects a new application version in the Application Catalog. By adding a scheduled event, you can control when a deployment process begins.

NOTE: When you create a new deployment process, it will immediately run once before it begins to follow the schedule.

To create a scheduled deployment process event:

1. On the Events page, click Add Event.

2. In the side panel that opens, add a Name and Description for the new event.

3. Select an Event Type from the drop-down menu. 

NOTE: Currently, 'Patch Tuesday' is the only scheduling option. Microsoft's security update release occurs on the second Tuesday of each month. Future Recast releases will add more scheduling types.

4. Add a Delay of 1 to 14 days, if desired.

5. Choose the Time of day to apply the update (in UTC time).

NOTE: The precise time of a scheduled deployment is tied to the update check interval. Patching checks for new application versions every 30 minutes by default, meaning that the scheduled deployment will run 0 to 30 minutes after the check.

6. Click Save.

To have a deployment process run according to a scheduled event you've created:

1. On the Deployment Processes page, click the Events link for a deployment process.

TIP: You can also click the Events link on the Deployment Process Details page.

2. Toggle the scheduled event to 'Active' and deactivate the default New Version Available event.