We use Dell/Wyse P25s in a DoD environment as well. Our servers are 7.1, but we are running agent 6.2.4 in the VDIs.
If you don't have all of your certificate issuers available to the connection servers, you won't be able to use the CACs. I don't recall what the specific KB article that addresses this is, but I'm sure you can do a quick Google search for 'CAC vmware view' to find it. the article has a specific section related to DoD CACs.
My agent settings include both USB & SC redirection, without using bridging on the ZC
We have used zero clients from several vendors (ClearCube, Wyse, LG) with smartcard login for many years, going back to View 4.x days. We haven't seen any hardware issues. Zero clients just pass the credentials through.
-Horizon/View servers are configured with applicable root/intermediate CAs for user certs on smartcard
-Parent VM has correct/updated middle-ware
-View agent has PCoIP smartcard and USB redirection features installed
-Zero clients have root CAs for View server cert
-Zero clients have the latest available firmware
-Some versions of zero client firmware (Tera1) don't support newer ciphers so we have to allow older ones within Horizon/View agent on parent VM.
-Single sign-on is normally enabled by default on both Horizon/View server and agent. If you get stuck at Windows login screen then maybe single sign-on is not enabled.
I can provide specifics, if needed.
do we have to install middleware on parent VM? we are running Windows 10. My understanding is middleware is built into Windows 7.x and above. is it correct understanding.
we would like to use Biometric (FingerPrint) on Windows 10 in post-session. I see you below as troubleshooting step is to check if SSO is enabled. I would like to disable SSO, instead allow Finger print to be used for Windows authentication. Is it possible?With Great Regards,
vExpert 2012-2017 | VCP3-5 | VCAP5-DCD | VCP-NV | vSAN Specialist | VDI | Germany
In our environment with our smartcards, we must install middleware on the parent VM.