Scan2Deploy Host Profile

Overview

A Host Profile Scan2Deploy profile supports every Scan2Deploy action, including installing apps and configuring Datalogic Launcher, Enterprise Browser, QuickBoard, and Visual Formatter. The profile is saved as a .tar file, and the barcode data only holds the location of that file. Instead of scanning the barcode, your MDM sends the same data to the Scan2Deploy Agent on the device in an intent, and the agent loads the profile from that location and applies it.

The .tar file can be hosted in one of three places, set in the File Hosting Location section of Scan2Deploy Studio:

• Scan2Deploy Studio: Studio hosts the .tar file from the PC it runs on. Studio must be running and reachable by the devices on the network, so this is best suited to testing or small, on-site deployments.
• Device storage: Your MDM pushes the .tar file to the device, then sends the intent. No server is needed. Used with SOTI MobiControl, SureMDM, and Workspace ONE.
• External hosting: The .tar file is hosted on a web, FTP, or SFTP server that the devices can reach, and the agent downloads it. Used with Microsoft Intune, which can't push files to Android Enterprise devices.

If the profile only uses the actions supported by Barcode Only profiles, use a Barcode Only profile instead, as nothing needs to be hosted.

Before you begin

• Complete the steps in Scan2Deploy: Before you begin, and read What both have in common for how MDM-deployed profiles behave.
• Make sure the devices have enough free storage for the .tar file, including any APKs and firmware it contains.

Create the profile

These steps set up a profile that your MDM can send to the devices. What the profile changes on the device is up to you: you choose it in Add your configuration.

Start the profile

1. Open Scan2Deploy Studio.
2. On the Welcome page, select Create Profile.
3. On the Action Selection page, select the device Model, SKU, and OS Version.
4. Under Configuration Actions, select Host Profile.

Add your configuration

1. Select the actions for the settings you want to change on the devices. Wi-Fi Setup is selected by default; clear it if your MDM manages Wi-Fi.
2. Select the > arrow to open the page of each selected action.
3. If you kept Wi-Fi Setup, clear Remove saved networks on the Wi-Fi Setup page to keep the networks already on the device, such as those set by your MDM. It is selected by default.
4. On each page, set the settings you want to apply. See the Scan2Deploy Studio documentation for each action.

Prepare the profile for your MDM

1. On the Save and Scan page, select the File Hosting Location tab.
2. Clear Use Studio to automatically host profile from this PC.
3. Set the hosting location for your MDM:
   • SOTI MobiControl, SureMDM, and Workspace ONE: Select Device storage and enter /sdcard/Download/profile.tar as the path.
   • Microsoft Intune: Select the server protocol and enter the location where the .tar file will be hosted, such as https://<storage-account>.blob.core.windows.net/scan2deploy/profile.tar.
4. Select the Settings tab.
5. Under Scan2Deploy QR Code Settings, check that Version is set to V3.
6. Select Silent Deploy, so the profile is applied in the background without the Scan2Deploy Agent opening on the screen of a device that may be in use.
7. Select Save and save the .tar file.
8. Rename the saved .tar file to profile.tar, or use the actual filename in the path above and in the steps below.
9. Select Copy.
10. Copy the data for your MDM:
    • SOTI MobiControl, SureMDM, and Workspace ONE: Select EMM Intent, then select your MDM (SOTI MobiControl, SureMDM, or Airwatch Intelligent Hub). The intent is copied, formatted for your MDM.
    • Microsoft Intune: Select Profile Data, then select Encrypted data.

See Save and Scan for more details on the copy options.

Deploy the profile

SOTI MobiControl

These steps are based on SOTI's Creating a Package guide. A SOTI package copies the .tar file to the device, then runs the SOTI MobiControl intent copied from Scan2Deploy Studio as a post-install script.

Profiles under 2 GB

A profile that includes APKs or a firmware update can be larger than 2 GB, so a SOTI package is the recommended method. If your .tar file is under 2 GB, you can use a File Sync policy instead.

Create the package

1. Sign in to the SOTI MobiControl web console.
2. Open the main menu and select Packages.
3. Select New Package.
4. Select Create.
5. Select Android as the platform.
6. Enter a name for the package, such as Scan2Deploy Profile, and a version.
7. Select Next.
8. On the Files tab, select Add.
9. Browse to, or drag in, profile.tar.
10. Set File Destination to /sdcard/Download/.
11. Select Save.

Add the intent script

1. On the Scripts tab, select Add.
2. Select Post-Install Script.
3. Paste the SOTI MobiControl intent copied from Scan2Deploy Studio.
4. Select Save.
5. Select Next.
6. Select Publish.

Assign the package with a profile

These steps are based on SOTI's Creating a Profile guide.

1. Navigate to Policies > Profiles.
2. Select New Profile.
3. Select Android Enterprise as the platform.
4. Enter a name for the profile, such as Scan2Deploy Profile.
5. Open the Packages tab.
6. Select Add.
7. Select the Scan2Deploy Profile package.
8. Select Add to Profile.
9. Select Save and Assign.
10. Select the target devices or device groups.
11. Select Assign.
12. Verify that the profile is applied, either on the device or in the session status file /sdcard/Download/S2DStatus.log.

Alternative: File Sync policy (profiles under 2 GB)

These steps are based on SOTI's Using File Sync Policies guide. SOTI File Sync doesn't support files larger than 2 GB.

1. Navigate to Policies > File Sync.
2. Select New File Sync Policy.
3. Select Android as the device family.
4. Enter a name for the policy, such as Scan2Deploy Profile, and select Next.
5. On the Configure tab, select Download from Server.
6. In Server File/Folder Name, select File Manager and upload profile.tar.
7. In Device File/Folder Name, enter /sdcard/Download/profile.tar.
8. Select Next.
9. On the Scripts tab, turn on Enable Post-Sync Script.
10. Set Script Type to Custom and paste the SOTI MobiControl intent copied from Scan2Deploy Studio.
11. Turn on Execute Script Only if Files Transmitted so the profile is applied only when a new .tar file is transferred.
12. Select Next.
13. On the Schedule tab, configure the synchronization schedule.
14. Select Save and Assign.
15. On the Devices tab, select the target devices or device groups.
16. Select Assign.

Microsoft Intune

Intune can't push files or send intents to Android Enterprise devices. Instead, host the .tar file on a server the devices can reach, and use the Launch Activities setting of Datalogic OEMConfig to open the Scan2Deploy Agent with the profile data, using the start activity intent. The agent then downloads the .tar file and applies it.

One OEMConfig profile per device

Intune supports only one OEMConfig profile per device on Datalogic devices. Add the launch activity to your existing OEMConfig profile from OEMConfig, rather than creating a new profile.

Host the profile

Any web, FTP, or SFTP server that the devices can reach can host the .tar file. To host it in Azure Blob Storage, follow the same steps as for the firmware package in Firmware Update on the Microsoft Intune tab:

1. Create an Azure Storage Account and a blob container with anonymous read access, such as scan2deploy.
2. Open the container.
3. Select Upload.
4. Select Browse for files and choose profile.tar.
5. Select Upload.
6. Select the uploaded blob and check that its URL matches the location entered in Scan2Deploy Studio.
7. Open the URL in a private browser window to verify that the file is downloadable without authentication.

Protect the hosted profile

Anyone with the URL can download a file in a container with anonymous read access. Don't include credentials in a profile hosted this way, or use a server that only your devices can reach.

Add the launch activity to the OEMConfig profile

1. Sign in to the Microsoft Intune admin center.
2. Select Devices.
3. Select Manage devices.
4. Select Configuration.
5. Select your Datalogic OEMConfig profile.
6. Select Properties.
7. Next to Configuration settings, select Edit.
8. Select Configuration designer.
9. Expand Launch Activities.
10. Set Package Name to com.datalogic.scan2deploy.
11. Set Component Name to com.datalogic.scan2deploy.MainActivity.
12. Under Launch Activity Extras, select Add.
13. Set Extra Type to String.
14. Set Extra Name to data.
15. Set Extra Value to the encrypted data copied from Scan2Deploy Studio.
16. Select Review + save.
17. Select Save.
18. Verify that the profile is applied, either on the device or in the session status file /sdcard/Download/S2DStatus.log.

SureMDM

These steps are based on 42Gears' File Transfer (Android) and Jobs for Android guides. A Composite Job pushes the .tar file to the device, then runs the SureMDM intent copied from Scan2Deploy Studio.

Create the File Transfer job

1. Sign in to the SureMDM web console.
2. Navigate to Jobs.
3. Select New Job.
4. Select Android.
5. Select File Transfer.
6. Select Add, then select the upload icon.
7. Upload profile.tar, set the device path to /sdcard/Download/, and select OK.
8. Enter a job name, such as Scan2Deploy Profile File.
9. Select Save.

Create the Run Script job

1. Navigate to Jobs > New Job.
2. Select Android.
3. Select Run Script.
4. Enter a job name, such as Apply Scan2Deploy Profile.
5. Paste the SureMDM intent copied from Scan2Deploy Studio.
6. Select Save.

Create and apply a Composite Job

1. Navigate to Jobs > New Job.
2. Select Android.
3. Select Composite Job and select Add.
4. Add the two jobs in this order:
   1. Scan2Deploy Profile File (File Transfer).
   2. Apply Scan2Deploy Profile (Run Script).
5. Select Save.
6. Return to the Home tab and select the target device or devices.
7. Select Apply.
8. Select the Composite Job.
9. Select Apply.
10. Verify that the profile is applied, either on the device or in the session status file /sdcard/Download/S2DStatus.log.

Workspace ONEWorkspace ONE (formerly AirWatch)

These steps are based on Omnissa's Product Provisioning documentation. A Files/Actions component pushes the .tar file to the device, then runs the Airwatch Intelligent Hub intent copied from Scan2Deploy Studio.

Create the Files/Actions component

1. Sign in to the Workspace ONE UEM console.
2. Navigate to Devices > Provisioning > Components > Files/Actions.
3. Select Add Files/Actions.
4. Select Android.
5. Enter a name, such as Scan2Deploy Profile.
6. Select the Files tab.
7. Select Add Files.
8. Select Choose Files and upload profile.tar.
9. Set the Download Path to /sdcard/Download/.
10. Select Save.
11. Select the Manifest tab.
12. Under Install Manifest, select Add Action.
13. Select Run Intent.
14. Paste the Airwatch Intelligent Hub intent copied from Scan2Deploy Studio.
15. Select Save.
16. Select Save to save the Files/Actions component.

Create and assign the product

1. Navigate to Devices > Provisioning > Product List View.
2. Select Add Product.
3. Select Android.
4. On the General tab, enter a Name, such as Scan2Deploy Profile.
5. In Assigned Groups, select the Smart Groups that should receive the profile.
6. Select the Manifest tab.
7. Select Add.
8. Select File/Action - Install from the Action(s) To Perform list.
9. In Files/Actions, select the Files/Actions component created earlier.
10. Select Save.
11. Select Activate to preview the devices that will receive the profile.
12. Select Activate again to start the deployment.
13. Monitor the product deployment status in Workspace ONE UEM.
14. Verify that the profile is applied, either on the device or in the session status file /sdcard/Download/S2DStatus.log.