/build/static/layout/Breadcrumb_cap_w.png

Best Practices Question


K2000 PXE Security Issues

01/30/2015 2408 views
We are new to the K2000 and still in the setup and testing phases. One question I have which I haven't seen referenced elsewhere regards security practices around PXE booting machines. We will have the K2000 setup so that we can reimage labs in place but I'm concerned with what happens if a student tries PXE booting a machine on their own. With the default configuration when a machine boots to the KBE it offers you the option to re-image the machine without prompting for any sort of password. Is there any way around that? It seems like there should be a way to stop users from imaging systems on their own but I haven't seen that in the documentation.

Thanks.

Answer Summary:
The interface was showing that a password was set but until I changed it I was not being prompted for a password. Once I made sure a password was set I was prompted at the PXE menu.
0 Comments   [ + ] Show comments

Comments


All Answers

3
set the password for the pxemenu on the general settings page.


Answered 01/30/2015 by: SMal.tmcc
Red Belt

  • I have a password set there but I am not prompted for it when the machine boots.
    • you will prompted, if you choose a KBE to be booted, not in the PXE menu
  • I reset the password and I'm being prompted now. I'm pretty sure a password was set previously and it showed black dots like there was a password there, but until I changed it I was not prompted.

    Thanks.
    • The UI will show black dots even for a blank password.

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