/build/static/layout/Breadcrumb_cap_w.png

KACE Product Support Question


After configuring DHCP for UEFI boot to K2000, KBEs no longer require passwords

02/21/2017 1582 views
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?
Answer Summary:
This is known behavior, reflected in the 4.0 release notes.
0 Comments   [ + ] Show comments

Comments

  • This content is currently hidden from public view.
    Reason: Removed by member request For more information, visit our FAQ's.

Answer Chosen by the Author

1
The password prompts do not currently work on UEFI. This was listed under the release notes for version 4 of the K2000.
Answered 02/21/2017 by: RyanPersaud
Senior White Belt

  • Ha, guess I should have looked in the release notes first. Thanks!

Community Chosen Answer

1
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.
Answered 02/22/2017 by: cserrins
Red Belt

All Answers

0
Has this been resolved as yet?  We are needing this password function.

Answered 08/02/2017 by: hoodathunkut
Purple Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ