Scan2Deploy

Overview

Scan2Deploy profiles are usually applied by scanning a barcode on the device. On devices enrolled in an MDM, the MDM can apply the same profile without a barcode being scanned: it sends the barcode data to the Scan2Deploy Agent on the device in an intent, and the agent applies the profile as if the barcode had been scanned.

Scan2Deploy profiles come in two types, chosen on the Action Selection page of Scan2Deploy Studio:

• Barcode Only: All of the profile data is in the barcode data. Your MDM only sends the intent.
• Host Profile: The profile is saved as a .tar file, and the barcode data only holds its location. The .tar file is hosted by Scan2Deploy Studio, pushed to the device by your MDM, or hosted on a server.

To compare Scan2Deploy with MDM settings and OEMConfig, see Configuration.

Barcode Only vs. Host Profile

	Barcode Only	Host Profile
Actions	Wi-Fi, enrollment, app enable/disable, device and scanner settings, scripts, and Scan2Deploy and Android settings	Every Scan2Deploy action, including app installs, Datalogic Launcher, Enterprise Browser, QuickBoard, Advanced Keyboard, Visual Formatter, Key Remapping, Snap OCR, file uploads, and Mobility Suite updates
What the MDM sends	The intent	The .tar file, then the intent
Hosting	None	From Scan2Deploy Studio, on the device, or on a web, FTP, or SFTP server

Use Barcode Only whenever the profile only needs the actions it supports, as there is nothing to host. Use Host Profile for any other action.

What both have in common

• Created in Scan2Deploy Studio: Both are created in Scan2Deploy Studio, as for barcode staging. An existing profile can be reused by editing it from the Welcome page.
• Applied with an intent: Your MDM sends the profile data to the Scan2Deploy Agent. Scan2Deploy Studio copies the intent pre-formatted for SOTI MobiControl, SureMDM, and Workspace ONE (Copy > EMM Intent), or the encrypted profile data for Microsoft Intune (Copy > Profile Data > Encrypted data). See Copy data.
• Silent deployment: With Silent Deploy selected in the Save and Scan settings, the profile is applied in the background, without opening the Scan2Deploy Agent. As the MDM can send the profile at any time, this keeps the agent from taking over the screen while someone is using the device. Silent Deploy requires Version to be set to V3.
• Applied once: The MDM doesn't track or reapply the profile. To change a setting, update the profile in Scan2Deploy Studio, copy the new data, and send it again.
• Same result logs: The outcome of each profile is written to the session status file /sdcard/Download/S2DStatus.log and the log history file /sdcard/Download/S2DLog.txt on the device.

Wi-Fi in Scan2Deploy profiles

The Wi-Fi Setup action is selected by default. On enrolled devices, Wi-Fi networks are better managed as MDM settings, so they stay in sync. Profiles with Enterprise Enrollment, such as for an MDM migration, should keep Wi-Fi Setup, so the device can connect and enroll in the Setup Wizard.

Remove saved networks

On the Wi-Fi Setup page, Remove saved networks is selected by default, for compatibility with older firmware. It removes every Wi-Fi network on the device that isn't in the profile, including networks set by your MDM. Clear Remove saved networks to keep them.

Before you begin

• Enroll the devices in your MDM. See Enrollment.
• Install Scan2Deploy Studio on a Windows PC.
• Make sure the devices run a Scan2Deploy Agent version that supports the profile. The required version is shown in the Next Steps section of Scan2Deploy Studio.

How each MDM sends the profile

SOTI MobiControl

Barcode Only

1. In Scan2Deploy Studio, select Copy > EMM Intent > SOTI MobiControl.
2. In SOTI MobiControl, send the intent to the devices with Send Script.

Host Profile

1. In Scan2Deploy Studio, select Copy > EMM Intent > SOTI MobiControl.
2. In SOTI MobiControl, create a package that copies the .tar file to the devices.
3. Add the intent to the package as a post-install script.
4. Assign the package to the devices with a profile.

See Barcode Only and Host Profile for the full steps.

Microsoft Intune

Intune can't run scripts, send intents, or push files on Android Enterprise devices. Instead, the Launch Activities setting of Datalogic OEMConfig opens the Scan2Deploy Agent with the profile data. Because Intune supports only one OEMConfig profile per device, the launch activity is added to your existing OEMConfig profile.

Barcode Only

1. In Scan2Deploy Studio, select Copy > Profile Data > Encrypted data.
2. In Intune, add the encrypted data to Launch Activities in the OEMConfig profile.

Host Profile

1. In Scan2Deploy Studio, select Copy > Profile Data > Encrypted data.
2. Host the .tar file on a web server that the devices can reach, such as Azure Blob Storage.
3. In Intune, add the encrypted data to Launch Activities in the OEMConfig profile.

See Barcode Only and Host Profile for the full steps.

SureMDM

Barcode Only

1. In Scan2Deploy Studio, select Copy > EMM Intent > SureMDM.
2. In SureMDM, create a Run Script job with the intent and apply it to the devices.

Host Profile

1. In Scan2Deploy Studio, select Copy > EMM Intent > SureMDM.
2. In SureMDM, create a File Transfer job that pushes the .tar file to the devices.
3. Create a Run Script job with the intent.
4. Combine the two jobs in a Composite Job and apply it to the devices.

See Barcode Only and Host Profile for the full steps.

Workspace ONEWorkspace ONE (formerly AirWatch)

Barcode Only

1. In Scan2Deploy Studio, select Copy > EMM Intent > Airwatch Intelligent Hub.
2. In Workspace ONE UEM, create a product with a Run Intent action containing the intent.
3. Activate the product for the devices.

Host Profile

1. In Scan2Deploy Studio, select Copy > EMM Intent > Airwatch Intelligent Hub.
2. In Workspace ONE UEM, create a Files/Actions component that pushes the .tar file to the devices.
3. Add a Run Intent action containing the intent to the component.
4. Add the component to a product and activate it for the devices.

See Barcode Only and Host Profile for the full steps.