SEP SBE, but applies to Enterprise ase well.
Suggestion/Idea:
In System Policies it is possible to influence the "Software Update Schedule". We need a similar function for required reboots, at least for critical servers.
Sometimes, SEP requires a reboot. If the user/admin does not react, a reboot is executed based on a difficult to understand time planning.
For servers, especially critical servers, it must be possible for a system admin to prevent reboots during business hours or periods where the server cannot and should not be stopped under any circumstances. Especially Hyper-V Servers should not just be rebooted at the mercy of an installed application. (If it makes sense or not to install SEP on a Hyper-V Server is another topic, please).
It makes sense to be able to define a maintenantc period, or periods, where a server may be rebooted, even by SEP.
It also makes sense to have special rules for Hyper-V hosts and such.
Background:
On one of our Hyper-V Servers, SEP requested the deletion of a file (that file was used under controlled conditions and the risks were understood). It was not possible to schedule a reboot for the next couple of days. Yet, SEP enforced the reboot at a time that was not ideal for that Hyper-V server. There are several VM's running on that server and each of them has certain requirements on uptime. System administration defined times for Hyper-V Host maintenance. But due to the enforced reboot, those times could not be used.
This brings a lot of hassles and required unplanned overtime.