Graceful network disconnection handling
We use Forticlient VPN for our remote systems, which has a sign in option that allows for connecting to the VPN as part of the logon process. When doing that, after you enter your username and password at the Windows logon screen, it connects to the VPN to authenticate against the domain controller directly. It also cuts off any pre-existing connections so everything will go through the VPN.
When we set a managed install to "after login", it starts and brings up the MI screen, but do to the agent connection loss from the VPN, it can't complete and just hangs. It doesn't appear to timeout or anything, we have to hit ctrl-alt-del and run explorer manually to get to the desktop.
It can be worked around with an offline script, but it would be ideal if MIs could handle this scenario more gracefully. It would even be an improvement to just abort the MI if the connection is lost, but here is my ideal behavior if the connection is broken:
1) Wait some amount of time for agent to try reconnection
2) On reconnection:
2a) Success then proceed with MI or maybe restart it
2b) Failure then abort MI and continue to desktop