Skip to main content

Save and Print Page

This final page allows users to save the profile (.tar file) and preview and save the generated barcodes (.pdf file). There are three main sections on this page, Name and Save, Advanced, and Deployment QR Codes

Save and Print page

Name and Save​

  • A name for your profile is required and will determine the file name of the profile when it is saved to disk.

  • The Description field allows you to enter some notes about the profile for future reference. It will be displayed on the printed barcode PDF as well.

Profile host location​

This section appears if your profile requires a Scan2Deploy profile (.tar file). Use this section to specify how the profile will be transferred to the device.

tip

Check the tables in the Action Selection page section to understand which settings require a profile host location and which do not.

When visible, you must select from the following options:

tip

Regardless of what option you choose, all profiles are saved to disk at C:\users\<user>\scan2deploy_uploads\<profile-id>.

Scan2Deploy Studio​

The profile will be hosted directly within Scan2Deploy Studio itself. Scan2Deploy Studio inserts the hosting PC's hostname as well as IP addresses for all connected interfaces to increase the likelihood of a successful profile retrieval by the Android device on the connected network.

important

Scan2Deploy Studio must be running and reachable by the mobile device. When you close Scan2Deploy, it keeps running in the background. See the task tray section for more detail.

Hosted in Studio

External hosting​

In this use case, you are responsible for knowing ahead of time where the profile will be hosted. The barcode created will point to the Custom deployment server location specified.

Hosted externally

note

SFTP Protocol - If a host key is provided, Scan2Deploy will verify that the server's public key matches the provided host key. If no key is provided, Scan2Deploy will attempt to connect to the server with host key checking disabled.

SFTP host key

The public key can be obtained from the SFTP host server with the ssh-keyscan shell command. For optimal security, the key should either be verified by or provided by the server administrator.

ssh-keyscan -t [type] [host]
  • type - The type of key to fetch from the scanned host. Possible values are rsa, dsa, and ecdsa.
  • host - The host name or ip address of the SFTP host server.

SFTP key scan

Additional hosting options ...​

These options allow you to locate the profile on the device, avoiding having to download the profile. Some likely use cases are that an EMM was used to push the tar file to the device and then apply it using the service intent, or deployment without use of Wi-Fi is required.

Additional hosting options

  • The options are:

    • Device storage - the internal flash storage of the device.
    • SD card - physical micro SD card. This option only appears in Scan2Deploy Studio if the device you selected on the Action Selection page has an SD card slot.
    • USB storage device - a USB hard drive or flash drive attached to the device with an on-the-go USB cable.

  • Each option requires a Path. For each option, Path is defined as below.

    • Device storage - the absolute path to the deployment package on the device. Example: /sdcard/Download/s2d/profile.tar
    • SD card - path to the deployment package relative to the root of the removable storage device. Example: /s2d/profile.tar
    • USB storage device - path to the deployment package relative to the root of the removable storage device. Example: /s2d/profile.tar

Advanced​

A few specialized fields are available here:

Final Action​

  • Action - Determines the last action Scan2Deploy should take before finishing profile processing. Values are none, close, enterprise-reset, factory-reset, and reset. The default value is none. If intent is selected, you will be expected to provide an intent URI that should be sent.

  • Intent - The intent URI that should be sent. Only applicable if the action field is set to intent. Two URI schemes are supported within Scan2Deploy, 1. Android App scheme and 2. Intent scheme. An example of how to configure an intent to open Chrome to the Google webpage within each URI format can be seen below:

    android-app://com.android.chrome/https/google.com/

Default Home/Launcher​

  • Launcher type - The type of launcher that should be used as the default launcher. Selecting Google Launcher App will use the standard, default launcher. Selecting SureLock will set SureLock as the default launcher. Selecting Custom App will require you to enter the name of a package in the Package name field. Selecting No Default will clear any previously selected default launcher. Selecting Select type will make no change to the device.
  • Package name - Package name of an APK that is or will be installed on the device that should serve as the device's Home/Launcher app. Not just any application can be used as a launcher app. It has to meet certain requirements specified by Google to be set as the launcher app.

Deployment Settings​

  • Hide from launcher - Caution if checked, Scan2Deploy will become hidden after the barcode read and the profile is processed fully.

  • Valid until - Set a date on which the barcode will be invalidated.

  • Backup to enterprise - If checked, Scan2Deploy will back up the current profile to persist through an enterprise reset. The profile will be automatically re-applied after an enterprise reset has occurred. Factory resetting the device will remove the backup profile. See the below table for the required minimum firmware version for supported devices.

    DeviceOS VersionMinimum Firmware Version
    Joya Touch 2211MR1 (TBA)

  • Skip field encryption - If checked, Scan2Deploy will remove any encrypted configuration fields and store all configuration data as plain text. When unchecked, potentially sensitive fields related to Datalogic application configuration (e.g. DL Launcher & DL Browser) will be encrypted within the profile.

  • Install latest OEMConfig - (Recommended) If checked, Scan2Deploy will include the latest version of OEMConfig in the profile and it will be automatically installed when the profile is applied to a device. If unchecked, the OEMConfig app will not be included in the profile.

    important

    The Datalogic OEMConfig application must be installed on the device to apply settings from the Device and Scanner Settings page. Scan2Deploy Agent may not report settings that fail to apply if OEMConfig is either not installed or if the version that is installed doesn't support the latest settings.

Scan2Deploy QR Code Settings​

Version​

Determines how the data in the QR code is encoded.

  • V2 - Default value. Supported in all versions of Scan2Deploy Studio.
  • V3 - Introduced in Scan2Deploy Studio v1.6 and uses more secure and stronger encryption key to generate the QR code data. This requires Scan2Deploy Agent v1.33 or above on the device to work. See below table for the required minimum firmware version for some of the devices.
DeviceOS VersionMinimum firmware version
Memor 18.1v3.06.08
Memor 108.1v1.05.13
Memor 109v2.03.04
Memor 209v1.04.15
Skorpio X510v2.08.050

Silent Deploy​

If checked, Scan2Deploy Agent on the device will silently deploy the profile without launching the UI. Requires a minimum Scan2Deploy QR Code Version of V3, compatible with Scan2Deploy Agent v1.33 and minimum firmware versions listed above.

Other Settings​

  • Screen Lock - Enables/Disables the device screen lock (keyguard). Choosing Disable has the same effect as choosing 'None' as the screen lock type on the device. However, this has no effect if a password, pin or pattern is currently set. Choosing Enable OR if a password, pin or pattern is set after the keyguard was disabled, the keyguard is reenabled. Default value is set to No Action.

Deployment QR Codes​

Barcode displayed when Scan2Deploy Studio hosts the profile:

Scan2Deploy hosting barcode

Barcode displayed when an external server hosts the profile:

Hosted somewhere else barcode

Download PDF​

This button allows you to download a PDF document that contains the full set of barcodes generated.

Sample generated PDF

Copy data​

This option allows you to copy the underlying data contained in the barcode(s). It is useful for making manual edits to the JSON file, as well as passing the data to the Scan2Deploy app via the start service and start activity intents. Three options are provided:

  • Copy JSON data (no whitespace) - copy unencrypted JSON for use with the start service and start activity intents, either from Java/Kotlin code or an adb shell.

  • Copy JSON data - copy unencrypted data suitable for pasting into a file. Includes newlines and proper spacing. This could be useful if you want to hand-edit the file and re-import it into Scan2Deploy Studio later.

  • Copy encrypted data - primary use case is also to pass to Scan2Deploy via the start service and start activity intents. Unless you intend on making adjustments to the JSON, this is recommended way of passing data via intent since it is encrypted.

Copy data save and print

note

The Copy data button is also available as part of the Show QR action view of a given profile on the Welcome page.

Copy data home

info

Right click on barcodes and select Copy Image to copy the barcode image itself. It can then be pasted into the application of your choice.

Next steps​

Typically, the next step is to open the Scan2Deploy app on your device and scan the barcodes provided by Scan2Deploy Studio.

Screenshot

note

Older versions of device firmware require enabling Scan2Deploy first. See the Enable Scan2Deploy section on the Scan2Deploy Android page for more information.

Alternatively, Scan2Deploy configuration data can be passed into the Scan2Deploy app directly from other Android applications. For instance an MDM agent installed on the device could directly pass barcode data to Scan2Deploy agent, eliminating the need for a barcode to be physically scanned. The following steps are necessary to achieve this.

Start Service intent​

Scan2Deploy offers a service that listens for requests to apply Scan2Deploy profiles without the Scan2Deploy UI (activity) being visible. The profile will be applied silently, without any Scan2Deploy UI being displayed in the foreground.

  • Broadcast action: datalogic.scan2deploy.intent.action.START_SERVICE
  • Broadcast receiver: com.datalogic.scan2deploy.S2dServiceReceiver

Extras​

ExtraTypeRequiredDefaultDescription
encodingenumnov2Indicates how the data field is encoded. Allowed values are:
• json - plain, unencrypted JSON file
• v1 - v1 encryption, generated by dl_config.exe
• v2 - v2 encryption generated by Scan2Deploy Studio
• v3 - v3 encryption generated by Scan2Deploy Studio
datastringyesnullThe data that Scan2Deploy should process that would normally be received in a barcode.

Examples​

These examples demonstrate passing properly escaped json data in data extra. The encoding extra must be set to json in this case.

Intent i = new Intent("datalogic.scan2deploy.intent.action.START_SERVICE")
  .putExtra("encoding", "json")
  .putExtra("data", "{\"global\":{\"action\":\"reset\"}}");
  .setClassName("com.datalogic.scan2deploy", "com.datalogic.scan2deploy.S2dServiceReceiver");

getApplicationContext().sendBroadcast(i);

Start activity intent​

Alternatively, you can start the Scan2Deploy activity if you want the Scan2Deploy UI to be visible. The same intent extras can be used in this case (encoding and data). These examples demonstrate passing in v2 barcode data exported by Scan2Deploy Studio in the data extra. Since v2 is the default, no encoding parameter is required.

  Intent launchIntent = getPackageManager().getLaunchIntentForPackage("com.datalogic.scan2deploy");
  launchIntent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
  launchIntent.putExtra("data", "Bm9uiYc//NWOnA0ZtIrgJ/qy0DCvHR+a1XwUz1sTne8s0KEM9ANwTS0XD4NbIOf/hV0+MM7cOFiZMbUDtO1L4sb4vnJluFbQOEM3phIuCRiBuMtpnh85");
  getApplicationContext().startActivity(launchIntent);
note

You can utilize an MDM console to start the Scan2Deploy activity or service with the desired data intent extra. However, that process will differ significantly from one MDM to the next and is outside the scope of what can be documented here.