Reconnecting too fast throws a Machine Failure - Refused in Director after upgrading to 2402. Client has these imprivata autologon machines. They are type 2, login to a published app, then locks the session with the imprivata login screen. What happens is these sessions get cycled after 2 hours idle time. Imprivata is too fast on the reconnect and the controllers throw the session onto the same machine that is still logging off. This throws an error as the session is on it's way out and it can't reconnect them. Then on the next login attempt they are fine. Is there any way we can either speed up the logoff process, get it not to reconnect to this session outgoing, or slow down the Imprivata type 2 reconnect process? Users aren't being prevented from logging in, but this noise in Director hides potential actual issues. Leaving sessions 24x7 isn't an option, as they cycle these machines throughout the week and always want sessions to go to a new Delivery Group for the rolling reboots.

@Edwin de Bruin iknow you have experience with imprivata, maybe you have some tips?

hi @Rutger Vosmeijer I think it is not Imprivata. Imprivata just receives the information from the brokers so I guess you would run in the same problem when using Storefront directly for instance (Storefront is what Imprivata is talking to) Normally the session should logoff rather fast. It is better to investigate why the logoffs take this long. Usually apps waiting for confirmation to close. Search for HungAppTimOut and AutoEndTasks regkeys.