Windows Patching Automation

Problem Overview

Manually managing Windows updates and third-party patches can be time-consuming and prone to errors. Native Windows Update settings offer limited control, especially when it comes to delaying patches for stability or handling third-party apps. While Winget can solve third-party patching challenges, it often requires complex implementation across multiple endpoints. This Automation streamlines patch management by blending OS updates and app patches into a single, hassle-free process.

Description

Windows Patching Automation schedules and applies updates for both the Windows operating system and popular third-party applications—like Zoom, Chrome, Firefox, Adobe Reader, and Microsoft Teams—using native Level actions. By leveraging Winget under the hood, it skips the need for scripting or YAML configurations. You can delay OS patches by a specified number of days to ensure stability, and the Automation will retry patches to reduce alert noise. If updates fail after two attempts, it creates an alert, so you’re always aware of potential issues. Simply import the Automation, adjust the schedule and patch categories, and you’re ready to go.

Preview

Use Cases

• Centralizing patch management for Windows and third-party apps
• Minimizing manual intervention by automating repeatable update tasks
• Delaying certain patches for a set number of days to ensure stability
• Standardizing the patching process across large environments
• Providing fail-safe alerts when patch installations don’t succeed

Recommendations

• Set Up Scheduling: Review your existing maintenance windows and decide on a weekly or monthly update schedule that minimizes user disruption.
• Adjust Patch Categories: After importing, specify which Windows Updates Categories you want to include or exclude for better control.
• Delay for Stability: Use the built-in delay feature to avoid immediate patch deployment, giving you time to confirm stability in test environments.
• Start Small: Implement the Automation on a test group of endpoints first, then expand to your broader environment after confirming success.
• Monitor Alerts: Keep an eye on notifications for any patch failures—so you can address issues promptly.

FAQ

• Do I need coding skills to use this Automation?
  No. This Automation uses native actions within Level and requires zero coding or script maintenance.

• Can I choose which categories of updates are installed?
  Yes. You can customize the patch categories you’d like to include or exclude.

• What happens if an update fails?
  The Automation will try again, and if it fails twice, it automatically creates an alert so you can investigate the issue.

• How do I handle reboots?
  ‍This Automation does not instruct Windows to reboot. We recommend using our “Ask User to Reboot” Automation, which allows users to manage their own reboots and automatically reminds them based on uptime.

• Is this Automation compatible with all Windows versions?
  It works on Windows Server 2012 R2 and up, as well as Windows 8.1 and up.