Automate deployments in Hexnode: Patches and Updates

This document provides a detailed overview of Patches and Updates automation in Hexnode UEM. Learn how IT admins can efficiently manage software/app updates across Windows (including co-managed Windows), macOS and Linux devices.

Maintaining control over device updates is essential for ensuring security and performance. Hexnode UEM simplifies patch management for Windows, macOS and Linux devices with manual and automated options.

Manual patching gives IT admins full control over update selection and installation, allowing for tailored patching based on organizational needs. Automated patching enforces updates through predefined rules, ensuring timely installations with minimal intervention.

Windows Patches and Updates

1. Manual patching for Windows devices: With manual patching, IT admins can selectively apply updates based on relevance, ensuring that only selected, critical patches are installed on Windows devices. This method is particularly beneficial in environments where software compatibility is a priority, such as organizations relying on legacy applications or custom-built software.

   In Hexnode UEM, manual patching allows admins to filter available updates by category, choosing between security patches, or feature updates and identifying the ones that need to be applied. Admins can also define installation parameters, such as whether a device restart should be enforced after the update, in what order the patches should be applied, and how to track installation success. Manual patching provides organizations with the flexibility to manage patches according to their specific operational requirements.

2. Automated patching for Windows devices: For organizations that need to ensure their Windows devices are always up to date with the latest security patches and software updates, automatic patching provides an efficient way to roll out updates. This is particularly useful in industries where security and compliance mandates require devices to stay protected against vulnerabilities. With Hexnode UEM, IT admins can set up rules to automate the patching process. These rules define when updates should be installed, whether admin approval is required before patch deployment, and if certain updates should be excluded based on compatibility considerations. Additionally, organizations can schedule updates to take place during designated maintenance windows, ensuring that critical operations remain unaffected. Admins can also enable notifications to receive real-time updates on automation progress, making it easier to monitor patch status. By automating the patching process, organizations can ensure timely updates and reduce vulnerabilities.

macOS Patches and Updates

1. Manual patching for macOS devices: With manual patching, IT teams can assess and apply updates based on operational requirements. This approach is particularly useful when managing software compatibility across various teams or when updates need to be rolled out to specific device groups. In Hexnode UEM, IT admins can select the updates to install and determine how they should be applied. Options include notifying users about available OS updates, downloading them for later installation, or performing an immediate installation.
2. Automated patching for macOS devices: For organizations managing a large fleet of macOS devices, automating update deployment helps ensure consistency and security by enforcing updates through predefined rules. This approach allows patches to be installed on time while aligning with organizational policies. Hexnode UEM allows IT admins to configure automated patch deployment for macOS devices by setting predefined rules. These settings allow organizations to manage how updates are applied, whether admin approval is needed before patch deployment and whether specific updates should be excluded.

Linux Patches and Updates

1. Manual patching for Linux devices: With manual patching, IT admins can select specific updates and deploy them to targeted Linux devices. This approach is useful when an update needs to be applied to specific devices, tested before wider deployment, or installed during a planned maintenance window.

   In Hexnode UEM, admins can select the updates to deploy and assign the deployment to the required Linux devices or device groups. This allows administrators to control which updates are deployed and which Linux devices receive them.

2. Automated patching for Linux devices: For organizations managing Linux devices at scale, automated patching helps deploy updates based on administrator-defined update criteria and deployment rules. This approach is useful for recurring patch cycles where updates need to be deployed consistently without manually approving updates each time.

   In Hexnode UEM, IT admins can configure automated patch deployment for Linux devices by creating a Linux automation and defining when it runs. Admins can configure update criteria based on attributes such as product, release date, severity, update classification, or update name. Multiple update conditions can also be combined using AND/OR operators.

   Admins can specify updates to ignore and configure deployment rules such as requiring update approval, installing updates and rebooting during a maintenance window, technician notifications, and deployment retries. The automation can then be assigned to the required Linux devices using included groups, excluded groups, and target filters.

Monitoring Patches and Updates automation

The Automations section under the Patches tab provides a centralized view of all patch automation activities. Every configured automation is listed here, allowing administrators to track and manage them effectively.

Selecting an automation allows admins to access its configuration page, where they can review its details and make necessary modifications. The Automations section consists of the following details:

• Name – The assigned name of the update automation.
• Version – The version of the patch or update installed.
• Platform – The target device platform (Windows, macOS or Linux).
• Created Time – The timestamp when the automation was created.
• Status – The current state of the automation (e.g., scheduled, running, complete).
• Last Status Update – The most recent timestamp indicating an update on the automation’s progress.