This content has been marked as final. Show 1 reply
Normally this is because the admin is trying to issue a boot once, when the user needs an "unlock screensaver" code. The same could also be true for the opposite, where an attempt was made to issue an unlock screensaver, when the user was at the pre-boot.
If this is the case, we helped clean up this confusion for our users by putting a custom banner at the top of the pre-boot environment, reflecting this.
I wouldn't chase down technical issues too far until you verify that the admin is actually doing it right. Sometimes it isn't the admin, but the user describing the scenario inadequately (wrong information or failing to mention something).