Issue metadata
Sign in to add a comment
|
During enrollment, Wi-Fi connection drops and will not reconnect with deployed credentials
Reported by
thetfo...@staff.lisd.net,
Oct 10
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Firefox/60.0 Platform: 10895.78.0 (Official Build) stable-channel peppy Steps to reproduce the problem: 1. Turn on Chromebook 2. Go through OOBE until you reach the "Connect to network" screen. 3. Join the production Wi-Fi network with credentials (we'll call this "Credential A") 4. Go through the rest of the OOBE and enroll into the organization. 5. While at the "enrolling device" screen, the wi-fi will disconnect. 6. Eventually the screen will change to a successful enrollment message. 7. The chromebook would normally load back to the login screen but instead your are presented with a "Connect to network" screen. What is the expected behavior? While performing the enrollment, the chromebook should receive the device Wi-Fi configuration and change credentials to "Credentials B" What went wrong? While performing the enrollment, the chromebook disconnects. We must enter "Credentials A" information again and then the chromebook will switch to "Credentials B" Did this work before? Yes 65? Chrome version: 69.0.3497.120 Channel: stable OS Version: 69.0.3497.120 Flash Version: 31.0.0.108 I don't use my chromebook much but we just purchased 1000 devices. Our setup team brought this issue to me.
,
Oct 10
Please provide any missing steps/doamin details. Thanks.!
,
Oct 15
The Wi-FI SSID we are connecting to during enrollment is the same SSID as we are deploying if that helps. The deployed network configuration contains all of the same settings except a different username and password. Also, the chromebook is already processing the enrollment (we've authenticated at the enterprise enrollment screen) before disconnecting. I'm assuming it's grabbing most of the enrollment settings and the new network config during this time. Once it disconnects, it will say at the "enrolling device" screen for a bit. I'm guessing it then reaches a timeout since it's no longer connected. It will then try to load the normal login. Since it's not connected, we receive the "connect to network" screen. I have reproduced this on 2 devices myself and our setup crew has seen it on all of the new devices we purchased (they are currently setting up a few hundred in the warehouse). Again. The enrollment is successful. You might be disconnecting too early since you are forcing a disconnect.
,
Oct 15
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 15
I'm adding some pictures as well. I was mistaken that the last screen I saw was the "Connect to Network" screen. It is actually titled "Network not available".
,
Oct 15
If we select the 'LISD' SSID, we are prompted to enter our username/password. It does retain the PEAP/MSCHAPv2 settings. The only way to get the machine to successfully connect using the deployed credentials is to login using the same credentials used during setup. Once we do this, it seems to change to the deployed credentials.
,
Oct 17
,
Oct 17
atwilson, Who could verify / fix this Wifi enrollment problem?
,
Dec 3
,
Jan 11
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by chchakrapani@chromium.org
, Oct 10