After configuring DHCP for UEFI boot to K2000, KBEs no longer require passwords
I followed Quest's instructions for adding the policies and making the scope changes to our DHCP server to enable UEFI booting to the K2000. This worked as expected, and I am able to image this way. But when I select a KBE to boot into, the KBE no longer requires a password before booting. All our KBEs have passwords, but they have just mysteriously stopped requesting them. Anyone know how to deal with this? Am I just going to have to make new KBEs?
0 Comments
[ + ] Show comments
Answers (3)
Answer Summary:
This is known behavior, reflected in the 4.0 release notes.
This is known behavior, reflected in the 4.0 release notes.
Please log in to answer
Posted by:
RyanPersaud
7 years ago
Top Answer
The password prompts do not currently work on UEFI. This was listed under the release notes for version 4 of the K2000.
Comments:
-
Ha, guess I should have looked in the release notes first. Thanks! - rstauffer 7 years ago
Posted by:
cserrins
7 years ago
The password does not currently work with iPXE, UEFI or BIOS. If the password is a requirement, you would need to stay with PXELinux (k2000.0) for now. The ability to use a password with iPXE is in the works for a future version.
Posted by:
hoodathunkut
7 years ago
Has this been resolved as yet? We are needing this password function.
