Product Documentation

Device Provisioning File Formats

Feb 12, 2015

Many mobile operators or device manufacturers provide lists of authorized mobile devices, and you can use these lists to avoid having to enter a long list of mobile devices manually. XenMobile supports an import file format that is common to all three supported device types: Android, iOS, and Windows.

A provisioning file that you create manually and use to import devices to XenMobile must be in the following format:

  • SerialNumber;IMEI;OperatingSystemFamily;propertyName1;propertyValue1;propertyName2;propertyValue2; ... propertyNameN;propertyValueN
Note:
  • The file charset must be UTF-8.
  • The fields within the provisioning file are separated by a semi-colon (;). If part of a field contains a semi-colon, it must be escaped with a backslash character (\). For example, the property propertyV;test;1;2 would be typed as propertyV\;test\;1\;2 in the provisioning file.
  • SerialNumber is required if IMEI is not given.
  • SerialNumber is required for iOS devices because the serial number is the iOS device identifier.
  • IMEI is required if SerialNumber is not given.
  • Valid values for OperatingSystemFamily are: WINDOWS, ANDROID, or iOS.

Example of device provisioning file

The following lines each describe a device in a device provisioning file.

1050BF3F517301081610065510590391;15244201625379901;WINDOWS;propertyN;propertyV\;test\;1\;2;prop 2

2050BF3F517301081610065510590392;25244201625379902;ANDROID;propertyN;propertyV$*&&ééétest

3050BF3F517301081610065510590393;35244201625379903;iOS;test;

4050BF3F517301081610065510590393;;iOS;test;

;55244201625379903;ANDROID;test.testé;value;

The first entry means the following:

  • SerialNumber: 1050BF3F517301081610065510590391
  • IMEI: 15244201625379901
  • OperatingSystemFamily: WINDOWS
  • ProertyName: propertyN
  • PropertyValue: propertyV\;test\;1\;2;prop 2