1823

Following 3 failed Linux-based Pre-Boot Authentication (PBLU) start attempts, SecureDoc will automatically opt for Pre-Boot for Native UEFI (PBU) Pre-Boot (which is normally more tolerant of unusual hardware).  

A new option can be manually added to the profile's .SPF file that will change the number of failed Pre-Boot start attempts to allow IT Technicians more time to determine why PBLU is not starting cleanly before it fails over to PBU.

Issue: Certain customers may encounter issues booting into PBLU where they either did not have an attached monitor connected to an enabled port, or their devices have had certain ports disabled to work around a known issue with Intel GFX combined with Sleep mode, which can cause Blue Screen halts when using PBLU using all display ports.

Solution: This option permits the SES Admin to manually define (in the Profile's.spf file) a more lenient number of Pre-Boot attempts under PBLU, to permit technicians to resolve any issues with monitor connections before the device would switch permanently to PBU mode (after which it would require the additional steps of having a user with Admin rights logging in to SDCC to switch it back and then updates boot logon to reinstate PBLU-based Pre-Boot).

How to Apply: To enable this (optional) override, manually add the following to the SecureDoc Profile for the device(s):

Section name: "SDSpace"
Key name: "PbluFailureCounterMaxValue"
Valid key values: 0...255
Key value meanings:
* 0 - PBLU Failure counter is disabled (never switch to PBU)
* 1...255 This new PBLU Failure counter may take a value between 1 and 255.

NOTE: If the above override is not applied to the Profile's .spf file, the client continues to be hard-coded to default to 3 failed PBLU load attempts before auto-switching to PBU, as before.