Hello all. I have an issue that I have been trying to solve over the last few days and now hope someone can assist with. Quick overview on the setup, to hopefully give you a better picture...
See more...
Hello all. I have an issue that I have been trying to solve over the last few days and now hope someone can assist with. Quick overview on the setup, to hopefully give you a better picture. We are using thin clients (Igel and HP) running Igel OS 11 as endpoints using smartcards for a larger healthcare organization. Idea is that users walks up to the endpoint, insert their smartcard in the reader, type in their pin and they would get access to a horizon VDI. This means the Horizon client login screen is autostarted on boot, and is restarted after the user pulled the card, or ended the session. This is currently running perfectly with 2206, as the Horizon client login screen is waiting at the smartcard login screen, with the secondary option to manually login. Issue: After updating our test environment from 2206 to 2303 we noticed that the smartcard login "option" is bypassed when the Horizon client is started, unless the user has already put in their smartcard. If no smartcard is present when the client/login screen is started, it goes straight to the manual login option, and needs a restart to notice the smartcard. I also tested this with Horizon client 2209 and 2212 - same result. We've talked with Igel as if this was something on their end, which they said no to, I've attempted to look through all kinds of settings to see if I missed anything (I am not super experienced with Horizon yet) and nothing. Have I missed something, is there some setting we can tweak or is there some kind of workaround we can use? Any good ideas floating around? Just for good measures, since this is also what Igel suggested, we are not interested in logging in with the AD/Smartcard in the IGEL OS itself, as it's only used as a gateway/portal.