The only simplest and dirty option left is probably to push over-the-air another Wifi payload for "WiFi Int", but with the wrong password.  This way, the device will not be able to use "Wifi Int", and will only be able to connect to "WiFi Corp", assuming no loophole is left for device end-user to input/modify any Wifi settings.

Why not enrolling using Wifi Corp in the first place?

Thanks for your response Raymond, we have the next limitations:

- Sometimes we have to enroll devices where WiFi Corp is not available.

- There are more than one team that enroll devices, but not all of them are supposed to know the WiFi Corp password.

-  WiFi Corp password is a bit complex, it demands some extra time configuring it when you have to enroll 5-100 devices at once.

Very interesting reasons.

As far as I know, there is no script command or other mechanism in MobiControl to achieve what you need.

From your situation description, it seems that you want the device to use only the internal corporate network with no internet access for security reason.    I believe only authorized administrator with the right to know the Wifi password of your internal network be allowed to do the device enrollment.  As enrollment should normally be done only once and not needed for years,  having a long complex password shouldn't be a big deal.   You might also consider using MobiControl Stage to speed up the enrollment process.

This would be possible using the MX layer on Zebra Android devices but given that you're using Huawei you might be limited to what SOTI supports natively. There is a wifireconnect scripting command that would at least trigger the devices to disconnect from their current wifi connection, but I don't think that would guarantee that they would switch to the other network. In fact, I would suspect that they would likely re-associate with the same wireless network.

This should work for now, I will give it a try.

Thank you all.