Over-the-air Migration from SOTI to Workspace ONE UEM

For Windows Mobile legacy device (Windows Rugged)

1      Over-the-air Migration from SOTI to Workspace One UEM

1.1      Migrating your Windows Mobile legacy devices.

1.1.1       Introduction

ACME PTY require to migrate their X scanners from their SOTI legacy tenant running Mobicontrol to their VMware Workspace One UEM Platform in order to decommission the Legacy SOTI tenant and let the X scanners in UEM with minimal management capability until retirement.

1.1.2       Purpose

In this document we will describe the steps in order to migrate the device from SOTI tenant to Workspace One tenant. Everything will be zero touch and with no user interruption so this can be performed at any time of the day with no production impact.

1.1.3       Audience

This tutorial is for prospective IT administrators of Workspace ONE, SOTI Mobicontrol and anyone who uses the products.

1.1.4       Packaging and Licensing

All Workspace ONE editions are licensed on a per-named-user basis and available as an annual cloud subscription or a perpetual on-premises license. For more information, see VMware Workspace ONE in the VMware Workspace ONE and VMware Horizon Packaging and Licensing guide.

1.1.5       Architecture

For a more detailed architectural diagram of Workspace ONE UEM, please see the VMware Workspace ONE and VMware Horizon Reference Architecture on Techzone.

2      Migration configuration

2.1      Logical migration flow

2.2      Prerequisites

Before you can perform this procedures, you must have the following components administrator rights access to:

Workspace ONE UEM abd SOTI Mobicontrol Tenants using a compatible Web Browser like Firefox or Chrome.

You must use a Windows computer to perform this steps due to SOTI Package studio only compatible with Windows desktop based OS.

2.3      Migrate your Device from SOTI to Workspace One

2.3.1       Preparation and Download of the binaries

Preparing your Workspace One tenant for Windows rugged (These are VMware recommended settings):

In Workspace Once Console, select the Organisation group that will have the Windows Rugged devices enrolled and then go to Group and settings  All Settings  Devices & Users  Windows  Windows Rugged. Select override as per below:

Save and Close this windows

Creating a generic device based user to enroll your devices:

In the Workspace One Console go to Accounts  List View  Add User:

Add the user details as per below and click Save:

Donwload of the Windows Mobile agent and the Credential.bin file:

The Windows mobile agent are stored in the Workspace one UEM Console so in order to get the binaries go to Devices  List View  Add Staging:

Select the Windows Rugged Platform:

In this section Name your Staging rule, select the OG, Enter your generic user previously created and select the right agent for your device. In this case we are selecting AirwatchCoreAgentWM-6.5.6.0. Click Save to complete.

In the same console section, select now the enrollement legacy rule and then click on “More Actions” and then “SideLoad”.

Click then on Download to initiate the download. A zip file will be generated and downloaded on your computer.

Extract the files and go to next step below.

2.3.2       Create a package in SOTI Mobicontrol

In order to create a SOTI Package you will need to download Mobicontrol Package Studio from the SOTI Console directly

In Mobicontrol Console select the device of choice (Windows Mobile) and click at the bottom on the Package Tab. You will be able to find the option to download package studio.

Execute the application and create a new project. Provide a name and make sure to select the platform “Windows Mobile”

Click next and leave it as default:

In this step we will select our files. First select the credential.bin file and leave everything as default as we will confire the file option later. Then add the WindowsMobile Agent.cab and same leave settings as it is. Click next until Package Studio takes you to the main window.

Now it’s time to configure our files. Select the Credentials.bin file and make sure the destination on the device is: “\Program Files\AirWatch\Staging\enrollment\”

PS: Do Not Select Execute this upgrade file – Auto Execute should be greyed out

Now select our second file the Agent.cab and right click property or double click the file: the file destination can be anything you wish in the case we selected \temp\

Ensure you then tick the box “Execute CAB File” and enter the command: “wceload.exe /noui /silent %file%” this will install the agent silently on the device.

Now you are ready to compil your package to be deployed to your device. Go to Project and Click Build Package. You will be able to see where the .pcg file is stored on your desktop after the compilation is finished.

2.3.3       Deploy the package to your devices with SOTI Mobicontrol

On the SOTI Mobicontrol Tenant select Windows Mobile on the top Tab and then select Rule Tab at the bottom. Right click on package deployement and select “Create Package Deployement Rule”

Provide a name to your Rule:

You will now have to add the package previously created. Select Add package and browse to find your file.pcg and then upload it into the console.

Select now your package from the list and click Next. The next step is now to select the devices you want to migrate.

You can decide when the migration will happen as per below and click next and finish to start the migration.

After 2-3 min your device will show up into your Workspace One UEM OG you defined and you can fully manage the device while the device is still enrolled into SOTI.

For testing purpose if you would like to clean the device to have it back to before being enrolled you can as per above select More Actions and click Enterprise Wipe. This will unenroll the device and delete Workspace One agent from the device.

2.3.4       Unenroll your device from SOTI Mobicontrol

In Mobicontrol console you can select the devices in lot right click and unenroll the devices.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Blog at WordPress.com.

Up ↑

%d bloggers like this: