Programmatically configure the 802.11 radio in Omnii and Core “Psion” terminals using WLANEx
Article ID: 96507078
Topic or Information
What is the WLANEx tool and what is it used for?
Can I use the WLANEx tool to programmatically configure the 802.11 radio in Omnii and Core “Psion” terminals?
Workabout Pro 3, 8530 Omnii XT15 8525 EP10 7530 G2 8515 VH10
WLANEx is a tool that can be used to programmatically configure the 802.11 radio in Omnii and Core “Psion” terminals.
SOTI’s MobiControl MDM does not have the ability to configure the 802.11 radio on Omnii and Core “Psion” terminals. This document describes a workaround via the WLANEx tool.
WlanEx_Connect.exe leverages a .dll and an XML file (WLANEx_Connect.xml) to configure the radio.
When unzipped the archive contains the following files/folders
The Readme.txt file contains the instructions on how to use this tool. The .exe, .dll and the .xml must reside in the same folder on the terminal
The “Sample XML configurations” folder contains sample XML files for the various supplicants that it supports.
DSA aka “DeviceScape Agent (found in Omnii Family terminals, XT10/XT15/VH10)
SCU aka Summit Configuration Utility (found in Core “Psion” terminals, 7535G2, 8525G2 etc)
WZC aka Windows Zero Config (the default wireless supplicant for WEH O/S variant terminals)
The end user can create their own XML file or modify an existing one to suit their use case but you must use the appropriate WLANEx_Connect.xml format for the target supplicant.
Below is a sample WLANEx_Connect.xml
“dsa” indicates this XML is for the DeviceScape Agent
This XML will add a new Wifi configuration with an ESSID of “Name”, using WPA2 Personal authentication and AES (ccmp) encryption with a PSK passkey of 0123456789
Below is a another sample WLANEx_Connect.xml
<root>Thawte Server CA</root>
“scu” indicates this XML is targeting the Summit Configuration Utility
This XML will add a new Wifi configuration with an ESSID of “APname”, using Open authentication and WEP encryption and a key of 1234567890 . The 802.1x mode is PEAP-MSCHAP using a root certificate
MDM Deployment Process
The typical deployment scenario involves pushing out the exe, dll and XML file and then using a post install script to run the exe file. The terminal does not need to be rebooted for the configuration change to take effect.
The accepted value for the Authentication field is one of:
“open” "wep" "shared" "802.1x" “wpa_psk” “wpa_eap” “wpa2_psk” “wpa2_eap” “cckm”
The accepted value for the Encryption field is one of:
"tkip" , "ccmp", "tkip_ccmp"
When using 802.1x, the accepted value for the EAP type field is one of:
"fast_mschapv2", "fast_gtc”, "fast_tls", "leap", "peapv0_mschapv2"
"peapv1_mschapv2", "peapv1_gtc”, "peapv1_tls", "tls”
"ttls_md5", "ttls_mschapv2", "ttls_gtc"
+ Applicable Products
- 7530 G2 Mobile Computer
- 8525 G2 Vehicle-mounted Computer
- 8530 G2 Vehicle-mounted Computer
- EP10 Mobile Computer
- Omnii RT15 Mobile Computer
- Omnii XT10
- Omnii XT15
- Omnii XT15 Mobile Computer Series
- Omnii XT15f
- Omnii XT15ni
- Workabout Pro 3
- Workabout Pro 4 Mobile Computer