Forum Discussion
Can you skip network connection in Android Enterprise Edition?
I think you'll need to speak to Samsung on this.
If the devices are showing correctly registered in ZT either via IMEI1 or SN & hardware details, and the config is assigned, it sounds to me like a bug in the build missing a step.
Are you buying enterprise edition models or anything outside of standard off-shelf devices from a normal retailer?
Are you able to flash/update with e-FOTA or OTA these devices to their latest builds and verify the behaviour still happens?
Okay but after we wipe the device completely and remove it from ZTP it reupload it. It works. I mean the image doesn't change, it's still the same image even after the wipe.
Also I can't explain why I can skip the network connection on these devices specifically and I couldn't do it with my other test devices. They have the same android version.
Logically if it's enterprise version you shouldn't be able to skip the network connection, during the first time setup.
Interesting, i can enroll all our AER devices on first time and after that without any network connection as far as i know but they then bahve as you described: Enrolling like a consumer device (or more likely unconfingured devices without any Google account etc.).
Yes, so on enterprise modell of the device, it should not be possible to skip network connection for the initial device setup. I confirmed this by taking in 4 different models of Android enterprise phones from Samsung and none of them gave me the option to skip network connection at the initial setup.
I had to connect it to Wi-Fi or use cellular data.But then we have these that are sent to customer exact same model that I test AND they can skip network connection at the initial setup.
As Sean mentioned maybe misconfigured OEM image from Samsung? I don't know I don't have any answer and I have been working with the issue for over a week now. Done like a 100 tests!Tested and you are right (again learned something, thanks!).
But I'm not sure what Google is checking being able to connect to in that step because reachability of the ZTP won't be part of it as companies may not use it and so don't want to grant access to it.
If the Wifi-Network you connect to provides internet access but blocks the relevant Google Services it could be possible to enroll without ZTP detection.
Also sometimes because of a somehow strange issue it could happen that devices are not detected by the ZTP correctly (enrolling as consumer device even if listed in ZTP correctly).
We have seen this on very few devices where it helped to reassign the correct configuration and after a wipe they were detected correctly. Is this maybe the case here as well?
Isn't this policy / feature (that you MUST connect to a network) by default set to TRUE for all Android Enterprise? Or is it different based on Android version?
No, this would be configured at the OEM for their build of Android. Most devices don't even know they're for enterprise until after they first connect to the internet where ZT is concerned. Samsung gains the benefit of OEM solutions storing locally a config after first setup to force devices to connect to the internet, though this wouldn't normally apply for ZT, rather KME.
Are you ZT exclusively or have you used other Samsung solutions to date? KME or Configure?
