we are using EEPC ver 5.21 with certificate on a Aladdin eToken 32k.
pre-boot authentication works fine.
Now we are testing with the Aladdin eToken Java 72k, but at the pre-boot authentication we get the error message 0xe0010044 - Token file not found.
Normally EEPC support this Type of the Aladdin eToken:
Are there additional/other Driver needed/available for this eToken that has to be imported to the File Group?
Or what am I doing wrong?
did you rename your smartcard token name with E-Token PKI Client Middleware before?
Please be careful, McAfee is sensible with Token Names (best experience with token name "eToken") and 72k Java cards.
Don't know why.
Got the same error when creating tokens in windows.
thanks for your answer !
You are right we rename our eToken to the username !
I tested it with a new eToken 72k Java and "eToken" as name and it works fine !!
I'm wondering why it is working with the eToken 32k and the "username" as token name !
But you answer is very helpful, so we have now a workaround !