Created: 04/11/2012
Updated: 06/11/2012
Background:
during one of my commitments, we encountered a strange behavior in the intelligent connection card cycle. Basically, when launching an application hosted on XenApp (4.0 / 4.5 / 6.0 / 6.5) server from a Dell Latitude E6320 with built in USIM reader, you will have a driver error notification.
The message itself mainly causes functional problems on Windows 03 servers, but it is visible on all operating systems. In reality, it causes problems when connecting a laptop to a recent system of 9 years old exploitation, so why am I surprised in the first place?
As far as I know (from past experience) is that Windows picks up the chip card readers in alphabetical order (if you have a lot), but it just does not sense. As good player to use is named "Broadcom .." and USIM drive is named "Dell ..." he was just curious.
Windows 03 Server Error
Windows 08 Server Error
solution 1
There are a few workarounds to this point of time, for example, if we disable the device error messages disappear.
solution 2
found another solution is to keep the device enabled USIM but instead of a blank value in groups (as indicated below). It was also found that this change has no impact on the behavior of the USIM / 3G significantly.
HKLM SOFTWARE Microsoft Cryptography Calais readers
Notice please! that the solution registry workaround has not been confirmed to be supported and therefore it is not a recommended approach at this point in time to use.
And yes, we tried to find other workarounds, but none of them was as effective as the two above.
Appropriations
I would also like to thank a few people for their help. So a big thank you to Kjell Perman (Tieto), Samir Hamouni (Tieto), Jens A (SecMaker) and last but not least Emil Tibblin (Swedish public sector). Emil is a guy you'll probably hear more like it (one way or another) been involved in most of my smart cards Citrix deployments over the years.
0 Komentar