Scanning and Mobility

Best practices to deploy SOTI MobiControl Device Agent into an already existing install-base of Dolphin devices.
Solution number KB-000006621
1- Introduction and scenario Several Dolphins are already being used on the field. SOTI MobiControl has been purchased in order to be able to manage the Dolphins but ActiveSync cannot be used to deploy the Device Agent that connects to the Deployment Server (i.e. because the devices are spread across a wide area or because the people using the devices do not have the means or the knowledge to manually deploy de Device Agent). In such scenario, the only way to deploy the MobiControl Device Agent might be by scanning bar codes that contain the information needed to connect to the Deployment Server, and will force the client device to connect to it. For this solution to work, it is required that the Dolphin is able to run an application called EZConfig, which by default always runs silently (in the background) when i.e. the Power Tools or Demos menus are started, or when Scanwedge is running. This means that an application like Scanwedge is able to read the bar codes that will be generated and explained further in this document.

2- Equipment and diagram used for this sample To create this document and the screenshots in it, the Dolphin 9700 marked in the diagram below as number 2 has been used. It connects to the backbone through an 802.11 wireless connection. Note that other terminals and data connection types (like GPRS) might be used as well. SOTI MobiControl Deployment Server is running version 8. At the end of the document there is some extra information that needs to be taken into consideration when client devices are located in IP subnets other than the one where the server is located, i.e. the Dolphin 9700 number 1, which connects through GPRS.

This is an entry from the Honeywell Scanning and Mobility Knowledge Base. As part of our ongoing effort to improve and enhance the quality of the solutions, we ask you to inform us if you feel that we can improve on the content of this solution. For America: hsmnasupport@honeywell.com or EMEA: hsmeurosupport@honeywell.com Page 1 of 8

3- Configuration of the SOTI MobiControl Deployment Server It is expected that SOTI MobiControl is already installed, and is up and running. Creation of an Add Devices Rule: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. In the MobiControl Manager application, go to the Rules tab at the bottom. On top, click on Rule > Create Rule > Add Devices Rule. The wizard starts. Enter a descriptive name for the rule, like Add Management Dolphin Devices > Click Next. Select the group where new devices will be added > click Next. Click Finish A pop-up appears. Click on the Launch Device Agent Manager button. Click on the New Agent button. Enter a descriptive name for the Device Agent, like Dolphin 9700 Device Agent > Click Next. Select Honeywell (Hand Held Products, Metrologic) > Click Next. Select the type of Honeywell product. For this example (Dolphin 9700), Honeywell Dolphin Mobile Device > Click Next. In the Device Platform Configuration step of the wizard, you can do 2 things: i. If there is a Dolphin 9700 connected to the PC through ActiveSync, you can click on the Detect Settings button to automatically populate the values for the Platform, Processor, OS major version and OS minor version fields. ii. If there is not a Dolphin 9700 connected to the PC through ActiveSync, the following values can be selected for the fields: 1. Platform: Pocket PC 2. Processor: ARM 3. OS major version: 5 4. OS minor version: 2 Click Next. Make sure that the IP address and port of the Deployment Server is correct. i. For instance, to create the agent for our Dolphin 9700 number 2 of the diagram on the first page of this document, the Deployment Server would be 192.168.111.104:5494. However, if client devices located outside the local subnet of the deployment server need to be able to connect to the server, a different IP address might need to be used. Check with the network administrator what IP address should be used, i.e. in the sample diagram above, IP address a.b.c.d should be used as well or Dolphin 9700 number 1 will not be able to connect to the server. ii. Rest of the fields can be left as they are suggested, but they can be changed as well. Click Next For this example, the Device Name is going to be the Customize Device Name option, with a value of Dolphin 9700 %AUTONUM% As Device ID, the MAC address of the device will be used. Click Next > Finish > Close > Close.

12. 13.

14. 15.

16.

st 4- Creation of the 1 bar code picture

1. If it is not yet installed on a PC, download and install EZConfig Editor application for the PC from this link. 2. Copy the \IPSM\Deviceconfig.exm file from a Dolphin and paste it somewhere in the PC. 3. On the PC, double click on the Deviceconfig.exm file. The EZConfig Editor application starts up:

This is an entry from the Honeywell Scanning and Mobility Knowledge Base. As part of our ongoing effort to improve and enhance the quality of the solutions, we ask you to inform us if you feel that we can improve on the content of this solution. For America: hsmnasupport@honeywell.com or EMEA: hsmeurosupport@honeywell.com Page 2 of 8

This is an entry from the Honeywell Scanning and Mobility Knowledge Base. As part of our ongoing effort to improve and enhance the quality of the solutions, we ask you to inform us if you feel that we can improve on the content of this solution. For America: hsmnasupport@honeywell.com or EMEA: hsmeurosupport@honeywell.com Page 3 of 8

4. As you can see, there is a disabled (grayed out) section at the bottom called MobiControl. Right click on MobiControl and enable it. Enable the 4 subfolders underneath as well (Device, Info, Comm and Connection). These subfolders should have the following keys and values: i. Device:

The DeviceClass value must be the same as the Add Devices Rule tag when the Add Devices Rule was created:

ii. Comm:

iii. Info:

The SiteName can be retrieved on the MobiControl Manager, by going to Tools > Options. The AgentID key will need to be created manually if it does not exist. iv. Connection:

Remember that for the Dolphin 9700 number 1 of the diagram, the IP address a.b.c.d will have to be used! 5. 6. 7. 8. 9. Save the changes to the DeviceConfig.exm file. Click on File > Create EZConfig Bar Code. Go to the Advanced tab and select Replace remote file. Go to the Bar codes tab and click on the Save button. Save the file in the PC.

This is an entry from the Honeywell Scanning and Mobility Knowledge Base. As part of our ongoing effort to improve and enhance the quality of the solutions, we ask you to inform us if you feel that we can improve on the content of this solution. For America: hsmnasupport@honeywell.com or EMEA: hsmeurosupport@honeywell.com Page 4 of 8

5- 2nd bar code picture 1. Download this bar code picture to the PC.

6- Client establishes first connection to the sever NOTE: it is expected that the Dolphin already has a network connection of any type, and that connection is working fine. It is not the purpose of this document to explain how to establish an 802.11 or GPRS connection with the Dolphin. 1. Open the picture of the 1st bar code saved, saved step 4 above. 2. Using the Dolphins Scanwedge application, scan the bar code of step 1. If Scanwedge is switched off, it can be started up on the Dolphin by manually going to Start > Power Tools > Scanwedge. 3. After scanning this bar code, a file gets automatically created in \IPSM\ called MCBootstrap.ini containing the connection settings that the \IPSM\MCBootstrapAgent.ext application will use during the first connection to the server. 4. Open the picture of the 2nd bar code, downloaded in step 5 above. If this bar code is scanned prior to the other one, an error message might appear on the screen of the Dolphin: \IPSM\MCBootstrap.ini does not exist. 5. Scan the bar code. After scanning this bar code, the Dolphin will automatically make the first connection to the server.

This is an entry from the Honeywell Scanning and Mobility Knowledge Base. As part of our ongoing effort to improve and enhance the quality of the solutions, we ask you to inform us if you feel that we can improve on the content of this solution. For America: hsmnasupport@honeywell.com or EMEA: hsmeurosupport@honeywell.com Page 5 of 8

7- Device Agent is pulled and installed on the client

1. In the background, the Dolphin will pull the Device Agent created in step 3.2.vii, to upgrade from the MCBootstrap agent to the real DeviceAgent.

The Dolphin disconnects the MCBootstrapAgent and installs the DeviceAgent, which then makes a connection again to the server. The Icon of the DeviceAgent appears on the Dolphins display.

2. As seen below, the Dolphin is fully connected.

3. The bar code pictures can be emailed or printed out and then scanned by all Dolphin devices. Remember that the bar codes must be scanned in the right order, as explained in this document. NOTE: keep in mind that there might be settings configured in Deviceconfig.exm that might be unique per Dolphin device (i.e. a fixed IP address). If that is the case, it is not recommended to use this method to deploy the Device Agent to the remote devices.

This is an entry from the Honeywell Scanning and Mobility Knowledge Base. As part of our ongoing effort to improve and enhance the quality of the solutions, we ask you to inform us if you feel that we can improve on the content of this solution. For America: hsmnasupport@honeywell.com or EMEA: hsmeurosupport@honeywell.com Page 6 of 8

Information that needs to be taken into consideration when client devices are located in IP subnets other than the one where the server is located, i.e. GPRS connections. Over GPRS, the clients cannot directly access the IP address of the server (192.168.111.104) because the Dolphins are not on the same IP network as the server. Over GPRS, the devices will only be able to approach the public IP address of the internet connection where the server is (unless other networking technologies like VPN are used). Lets say that the public IP address of the site where the SOTI MobiControl server is located is 1.2.3.4 (marked as a.b.c.d in the diagram) On the SOTI server, when you create the device agent, you might want to create (although not everything is needed): Separate Device groups, as on the screenshot below, as you might want to have different update schedules, security settings, etc.

Separate Device Rules, one for client devices that connect through LAN / WLAN, and another one for one for client devices that connect through GPRS.

This is an entry from the Honeywell Scanning and Mobility Knowledge Base. As part of our ongoing effort to improve and enhance the quality of the solutions, we ask you to inform us if you feel that we can improve on the content of this solution. For America: hsmnasupport@honeywell.com or EMEA: hsmeurosupport@honeywell.com Page 7 of 8

Separate Device Agents (one per rule): one Device Agent will be used for the local LAN / WLAN clients and the other one for the GPRS clients.

The bottom line is that clients coming from a different IP network need different settings in: The bar code generated out of Deviceconfig.exm: o The IP address of the server should then be 1.2.3.4 instead of to 192.168.111.104. o Make sure that the value of the Device Class key is the same as the tag of the Add Devices Rule that is linked to the proper device Agent. The IP address of the Device Agent generated for the Add Devices Rule, as it should be 1.2.3.4 instead of 192.168.111.104. Finally, NAT translation might need to be configured on the internet gateway and/or routers to forward incoming traffic on TCP port 5494 towards the IP address of the SOTI server.

This is an entry from the Honeywell Scanning and Mobility Knowledge Base. As part of our ongoing effort to improve and enhance the quality of the solutions, we ask you to inform us if you feel that we can improve on the content of this solution. For America: hsmnasupport@honeywell.com or EMEA: hsmeurosupport@honeywell.com Page 8 of 8