More granularity in Pre-Boot?

**randyvcbc** · 2015-10-01

Is there a way to add more/better granularity to the Pre-Boot cycle?

Basically, the system requires me to add in the user that it will authenticate via AD, but how about the standard "Support" local account that desktop always uses on devices? What about making sure that the desktop group is allowed to log in as required in the field where they may not have a laptop that is/has been connected to the network for a while?

I find it troubling that in order to make sure that this stuff works, I have to completely disable Pre-boot authentication.

**Cory Webb** · 2015-10-02

can u put up a screenshot of this

**randyvcbc** · 2015-10-13

Sorry for the delay, I didn't get notification there was a response (I've ensured I get an immediate response now)...

Here's the area. We'd really rather have the system allow company users to be able to log in. Basically, desktop builds the machine, and they need to use a local admin account to log in afterwards as well which is NOT on the network. As well, there are some areas where more than one user will log into a machine, and these are not always the same everyday. Needing to add in the users will take a lot more administration than should be required of the support group.