The constructor for the maint_util call in 'pu.exe' looks like this: maint_until (until%d,for%d,comment,from%d1)

So, you could script pu.exe calls for the maint_until callbacks to the relevant robot using the epoch time stamp. Please be aware that this will only put this specific robot (and the probes on that robot) into maintenance. It will not affect any remote probes (such as net_connect) that have profiles running against this target, these would still send alarm / qos as normal.

To be able to put everything targeting a specific host into maitenance, you need to either use the Rest API call backs (webservices_rest) or use the USM ad-hoc maintenance functionality (i understand the latter is not an option here).

The constructor for the maint_util call in 'pu.exe' looks like this: maint_until (until%d,for%d,comment,from%d1)

So, you could script pu.exe calls for the maint_until callbacks to the relevant robot using the epoch time stamp. Please be aware that this will only put this specific robot (and the probes on that robot) into maintenance. It will not affect any remote probes (such as net_connect) that have profiles running against this target, these would still send alarm / qos as normal.

To be able to put everything targeting a specific host into maitenance, you need to either use the Rest API call backs (webservices_rest) or use the USM ad-hoc maintenance functionality (i understand the latter is not an option here).