I have a question about how the Installation behavior works in regard to maintenance windows.
Scenario:
I have an application that requires Outlook.exe to be closed in order to install.
We have a nightly maintenance window of 11:00 PM until 6:00 AM. We have a required deployment deadline is set to ASAP.
On the deployment settings we have the "Automatically close any running executables...." checked.
On the user experience we are not selecting the software installation nor the system restart outside the maintenance window.
Now, after the deadline hits but outside the maintenance window outlook.exe is getting closed by SCCM. If this is supposed to work that way, it seems like a terrible design flaw. It still waits to install until the maintenance window.
Scenario:
I have an application that requires Outlook.exe to be closed in order to install.
We have a nightly maintenance window of 11:00 PM until 6:00 AM. We have a required deployment deadline is set to ASAP.
On the deployment settings we have the "Automatically close any running executables...." checked.
On the user experience we are not selecting the software installation nor the system restart outside the maintenance window.
Now, after the deadline hits but outside the maintenance window outlook.exe is getting closed by SCCM. If this is supposed to work that way, it seems like a terrible design flaw. It still waits to install until the maintenance window.
