Exciting things are coming - our community is moving to a new home!
Whilst we make this move, please note any posts/replies made between 21st February - 5th March 2026 will not be carried across. Learn more here.

Forum Discussion

Daucc's avatar
Daucc
Level 1.5: Cupcake
16 days ago

Wi-Fi connection and credentials

I work at a school where we need to enterprise enroll the devices. We have an issue that correlates to how we initiate the enterprise enrollment. 

 

If we use the shortcut keys "ctrl alt E" to initiate the enrollment, wi-fi connection is lost as soon as the user hits <enter> after the password for the account information. Yet if we choose the enrollment button at the bottom of the screen, there are no issues.

 

 In general, knowing what causes our issue would be good to have in our mental toolbox, but the issue also prevents us from using a script which acts similar to Go-Box or Centipede.

1 Reply

  • Lynda's avatar
    Lynda
    Google Community Manager
    2 days ago

    Hi Daucc​ thanks for getting in touch. You are most welcome here but just as you mentioned working at a school I also wanted to point you in the direction of our Google for Education Community in case there were particular nuances in the education space that you wanted to keep updated on.

     

    However as your question surrounds general enterprise enrollment we'd be happy to advise.

     

    Possible SolutionDescription
    The "Tab" MethodInstead of Ctrl + Alt + E, program your script to use Tab to navigate to the "Enterprise Enrollment" button at the bottom of the screen and press Space/Enter. This mimics the "button" behavior which you've already confirmed works.
    Update ChromeOS FirstSometimes the OOBE version on the box is several milestones behind. Try updating one device to the latest stable channel manually to see if the shortcut bug persists.
    Zero-Touch Enrollment (ZTE)If your hardware supports it and you bought from a qualified reseller, ZTE bypasses the need for scripts entirely by pre-registering the serial numbers in your Google Admin Console.

     

    Review the above and give them a try.

     

    Outside of that, if the issue persists, please can you raise a support case so that our dedicated team can investigate the specific instance and better advise?