Ensures that all changes made to WSUS Computer Groups or endpoint assignments on the Primary WSUS server are fully synchronized to all Replica WSUS servers. 

It is critical in environments with multiple WSUS servers, as it guarantees that group membership and update approvals are consistent across the entire WSUS hierarchy. JetPatch uses this task to confirm that after any group or assignment change, all Replicas reflect the new state before proceeding with patching or compliance checks. 

If synchronization fails, endpoints may appear out of sync or patching may be delayed.
More Details : Here

Manages the lifecycle of WSUS Computer Groups. It creates new groups, renames existing ones, or deletes groups in WSUS to match the structure of JetPatch Smart Groups. 

This is essential for dynamic grouping, as JetPatch relies on WSUS groups to target endpoints for patching. 

The task ensures that any change in JetPatch's group logic is reflected in WSUS, maintaining a one-to-one mapping between Smart Groups and WSUS groups.

Queries the WSUS server for the full list of available updates, including metadata such as KB numbers, categories, and approval status. 

It can run in diff mode (fetching only new/changed updates) or full mode (fetching all updates and cleaning up removed ones). 

The results populate JetPatch's patch catalog, enabling accurate compliance reporting and patch selection for remediation plans.

Collects summary statistics for each WSUS Computer Group, such as how many endpoints in the group need a specific update, how many have installed it, and how many failed.

This data is used to display group-level compliance dashboards and to prioritize patching actions for groups with the highest risk or lowest compliance.

Retrieves detailed update status for each individual endpoint from WSUS. 

It records which updates are installed, missing, failed, or pending a reboot. 

This granular data is essential for per-endpoint compliance tracking, troubleshooting patch failures, and generating audit reports.

Queries WSUS for the current list of Computer Groups and the endpoints assigned to each group. 

JetPatch uses this information to verify that endpoints are in the correct groups according to Smart Group logic, and to detect any discrepancies that might require corrective action such as reassigning endpoints.

Triggers a forced synchronization on the Windows Update Agent (WUA) of an endpoint, making it immediately contact the WSUS server to refresh its list of available updates and group memberships. 

This is especially important after group or approval changes, ensuring the endpoint is aware of its new patching context without waiting for the next scheduled sync.

Synchronizes the approval status of updates between JetPatch and WSUS. 

Ensures that JetPatch's internal records match the actual approval state in WSUS (e.g., Approved, Not Approved, Declined), which is critical for accurate patch targeting and compliance reporting.

Runs a PowerShell script on a Windows endpoint to reset the Windows Update Agent's (WUA) authorization and registration with WSUS. 

Used to fix issues where the agent is not communicating properly with WSUS, often by clearing configuration and forcing a re-registration.

Configures a Windows endpoint to use Microsoft Update directly, bypassing WSUS entirely. Used in WSUS-less environments where JetPatch manages patching without a local WSUS server.

The task updates registry settings and Windows Update configuration to point to Microsoft's public update servers.

Assigns endpoints to the correct WSUS Computer Groups or removes them from groups they no longer belong to, based on JetPatch Smart Group logic. 

Ensures accurate targeting for patching and compliance.

Performs a deep reset of the Windows Update Agent, including stopping services, clearing update caches, re-registering components, and restoring default settings. 

Used to fix persistent or complex WSUS/WUA issues that cannot be resolved by the standard reset tasks.

Displays a notification to the logged-in Windows user before patching begins. 

The notification informs the user that updates will be installed soon, giving them a chance to save work or prepare for a possible reboot. 

The notification is non-blocking (the user cannot postpone the patching), but it improves user awareness and reduces surprise disruptions.

Displays an interactive reboot dialog to the Windows user after patching. 

The user can choose to reboot immediately, snooze the reboot for a configurable period, or optionally cancel the reboot. 

The task can be configured to only trigger if a reboot is actually required, and the number of allowed snoozes can be set by policy.
More Details : Here

Performs an immediate, non-interactive (forced) reboot of a Windows endpoint. 

Used when a forced reboot is required, such as after critical updates or as part of an automated workflow where user interaction is not needed.

Issues a reboot command to a Solaris endpoint. 

Typically used after patching or as part of a remediation plan that requires a system restart to complete updates.

Reboots a Linux endpoint. 

Can be triggered automatically after patching or run manually by an administrator as part of maintenance.

Checks if the endpoint has communicated with JetPatch within the last 24 hours. 

Used for health monitoring, reporting, and to identify endpoints that may be offline or disconnected.

Runs a series of health checks on a Linux endpoint, such as verifying that required services are running, checking disk space, and confirming network connectivity. 

The results help JetPatch determine if the endpoint is healthy enough to proceed with patching or if pre-remediation steps are needed.

Checks if a Windows endpoint is ready for patching. Verifies disk space, required services, network connectivity, and ensures there are no pending reboots or other blockers. 

If the endpoint is not ready, JetPatch may delay patching or alert the administrator.

Performs a series of checks and setup steps on a Windows endpoint, ensuring the system is ready for patching or other JetPatch-managed activities. 

May collect system information, verify prerequisites, and set up the environment.

Runs multiple checks and preparatory steps on a Linux endpoint. 

May collect system information, verify prerequisites, and set up the environment for patching or other operations.

Scans a Windows endpoint for available updates, either via WSUS-less mode or direct scan. 

Results are used to populate JetPatch's patch catalog and determine compliance.

Scans an Ubuntu endpoint for available updates using the system's package manager. 

Results are parsed and reported to JetPatch for compliance and remediation planning.

Enables the Vault repository on CentOS 6 endpoints, allowing access to archived (EOL) updates after official repositories are shut down. 

Essential for maintaining legacy systems that still require patching.

More Details - Here

Disables IPv6 networking on a Windows endpoint by modifying system settings. Often done for security or compatibility reasons in environments that only use IPv4.

More Details - Here

Disables IPv6 on a Linux endpoint and immediately reboots the system to apply the change. Used for hardening or compliance with network policies.

More Details : Here

Checks the activation and licensing status of a Windows endpoint. 

Ensures the OS is properly licensed, which can affect update eligibility and compliance.

Checks the PowerShell execution policy on a Windows endpoint to ensure that scripts can be executed. 

If the policy is too restrictive, JetPatch may not be able to run required scripts for patching or remediation.

More Details - Here

Checks if a Windows endpoint requires a reboot (due to pending updates or system changes) and automatically reboots the system if necessary. 

Ensures that endpoints are in a clean state before or after patching.

Checks if a Windows endpoint requires a reboot, but does not perform the reboot. 

Used for compliance checks or to alert administrators without triggering an automatic restart.

Checks if a Windows endpoint is assigned to more than one WSUS Computer Group, which can cause targeting conflicts or compliance issues. 

Alerts administrators to correct group assignments.

Runs diagnostics on the Windows Update Agent (WUA) to detect common problems that could block patching, such as misconfiguration, missing services, or corrupted update databases. 

Provides actionable results for troubleshooting.

Checks the epoch value of a CentOS patch, which is used in versioning to determine update order. 

Ensures JetPatch correctly interprets which patches are newer or older, preventing accidental downgrades.