I was working on a VDI project for a customer this week. The solution was for a public library, the software used by the library added a custom GINA to Windows, that is to say it replaced the default logon screen, like so:
A VDI solution was proposed using the pooled desktop scenario, whereby a connection broker was used to distribute the connections amongst several RD virtualisation hosts, all using a template ‘gold’ image.
Now, because of the custom GINA, the RD connection broker would correctly redirect the connection to the Windows 7 VMs, but… would disconnect the session after around 6 minutes as there had been no login activity. This was a problem in this scenario as the library terminals spent most of their time at the login screen, wanting for a member of the public to come up and use them. The problem source was identified as the RD connection broker, not the VM itself by two methods: First, RD connections directly to the Win 7 VM stayed active for ever, secondly, the following log entries were spotted on the RD connection broker:
What could be the solution to this problem? I like to think I know MS products pretty well and thought that there must be a parameter for this.