Unified System Update Orchestrator
Purpose
This solution provides a simple, centralized way to install updates for Dell, HP, Lenovo, and Windows systems. It lets users, choose what updates to run using parameters, making the process flexible and consistent. By handling everything in one place, it simplifies maintenance and helps to keep devices up to date.
Associated Content
| Content | Type | Function |
|---|---|---|
| Enable Unified Update Manager | Custom Field | Controls solution deployment across different clients. |
| Disable All Updates | Custom Field | Controls solution exclusion across Sites/Endpoints. |
| Deploy All Updates | Group | Includes Windows workstations that have been opted for the solution. |
| Unified Update Manager | Script | Installs updates for Dell, HP, Lenovo, and Windows based on the parameters selected. |
Implementation
- Create the below Custom Fields using the implementation instruction provided in the documents.
- Create Deploy All Updates using the implementation instruction provided in the documents.
- Create Unified Update Manager using the implementation instruction provided in the documents.
FAQ
Does Script works for multiple OEM simultaneously?
Yes, the script supports multiple OEMs at the same time. You can choose different update types for each OEM, such as all updates for Dell machines, BIOS and firmware updates for HP machines, and driver updates for Lenovo machines. You can also select the type of Windows updates separately.
Does windows updates will work if any OEM update is selected for a machine?
No, if an OEM update is selected, the script will not run Windows updates. It will only perform the selected OEM updates.
what is default behaviour for an OEM update if update type is not selected?
If no update type is specified for an OEM, the script will perform driver updates by default.
Does it automatically reboots the machines?
No, the script does not automatically reboot the machine. However, a reboot can be enabled by using the Reboot parameter when running the script.
Changelog
2026-04-29
- Initial version of the document