We have a requirement regarding the reboot process after critical Windows updates.

Our requirement is as follows:

When critical Windows updates are installed, the endpoint should notify the user that a restart is required.

If the user postpones the restart on the first day, the endpoint should generate another restart notification on the following day.

The second notification should not provide the user with an option to postpone the restart.

The device should be forcefully restarted after a defined grace period.

This is required because some critical Windows updates require a restart to complete firmware/BIOS-related updates and other pending components.

Could you please confirm whether this workflow can be configured in Xcitium?

If possible, please advise us on the recommended configuration/procedure to achieve the following:

Day 1: Notification → User can postpone once

Day 2: Mandatory notification → No postpone option → Force reboot

Our requirement can be structured like this:

Day 1 – Windows update

Install all the Windows updates once its completed.

Notify the user that a restart is required.

Give a short grace period, e.g. 30 minutes.

After the grace period, force the reboot.

If you specifically need a “user can postpone once” workflow

First notification: allow postponement.

Record/check whether the endpoint is still in Reboot Pending status.

On the following day, run a forced reboot procedure against devices still pending restart.

The second notification should use Xcitium's Force the reboot option, rather than the postpone option.

Please also let us know if this can be configured through a Patch Management Procedure, Restart Control, or any other Xcitium policy/procedure.