Add the ability to schedule VM lock and unlock actions at the host pool level, including the ability to specify the number of VMs to lock, so that automated patching workflows can be fully automated end-to-end.
**Desired Workflow:**
1. Scripted Action scheduled to lock X number of VMs in a host pool on Day X (prior to Windows Update deployment from golden image)
2. Automatic Windows Updates on the golden image scheduled to run on Day Y (existing functionality)
3. Scripted Action scheduled to clean up and unlock the locked VMs on Day Z
**Why this matters:**
Today, scripted actions can be scheduled against golden images, but VM lock/unlock cannot be scheduled. This forces a manual step into what would otherwise be a fully automated patching cycle. Scheduling lock/unlock at the host pool level, with the ability to define how many hosts to lock, would close the gap and allow the entire patch lifecycle to run hands-off.
**Benefit:**
- Fully automated patching workflows with no manual intervention
- Predictable, repeatable maintenance windows
- Reduced operational overhead for admin teams managing multiple host pools
Comments (0 comments)