Could you please clarify the answer about assignment of user:
After exceeding the maximum defined failed attempts with Reactive AutoBoot, can a user authenticate using Windows credentials or use Self-Recovery to pass preboot and access Windows? [EEPC 7.0 Patch 1 and later]
No, if the system has always been working in AutoBoot mode, which means it is likely that no EEPC users have been assigned to allow any successful preboot authentication.
Yes, if the EEPC user account has been assigned and the user knows the EEPC login credentials.
If I enable Reactive AutoBoot and user have never logged to PC using PBA. How can I pass to PBA user's Windows credentials?
Will EEPC get user's Windows credentials for PBA if enable SSO and options below?
Message was edited by: Konstantin_M on 10/15/13 3:30:25 AM CDTMessage was edited by: Konstantin_M on 10/15/13 3:40:30 AM CDT
If the users are assigned elsewhere, epo will pick up their password then.
If you are not using preboot and you chose to run insecurely in autoboot mode (with the keys stored on the drive) then you will have to do a machine recovery.
Thank you for information.
But I see that PC starts slower if I enable SSO even for autoboot mode.
I thought EEPC pickuped password when SSO was enabled.
I had to switch on AutoBoot option because start of PC took a lot of time with PBA+SSO combination for EEPC 6.x.x.
I have not tested if it works better and quicker for EEPC 7.x.x.Message was edited by: Konstantin_M on 10/15/13 8:47:03 AM CDT
Slow startup is usually related to excess irrelevant drivers in your image, but still, using autoboot mode defeats the point of encrypting. You don't get any data protection regulation compliance if you store the keys with the data.
Could you please clarify what do you mean under "irrelevant drivers"?
I have latest BIOS firmware and hardware drivers but startup is very slow when SSO is enabled for Windows 7 and for Windows XP too.
When Autoboot is enabled I have encrypted HDD, am I right? Reactive Autoboot limits password attempts as additional protection.
I made the test of different startups on the same laptop with the same user.
The results are:
As you can see that SSO makes startup slower even for AutoBoot.
No no SSO details are captured - SSO details are only ever captured for the currently logged on pre-boot user, not any other users. Since there's no pre-boot user, no SSO details can be captured for anyone.