This guide will show you how to quickly enroll your Windows Mobile/CE device and what to expect in TestDrive.
Demonstrating a typical rugged use case, the device will be provisioned with apps and locked down with the Launcher, restricting the user's access to the rest of the device. Advanced Remote Management is also covered.
Before You Begin
You must have:
- TestDrive Account. Sign up here.
- Device: A supported Windows Mobile or CE device
- Administrator role: Device Administrator at Retail Holding Company
- Reference relative online documentation, such as the VMware Workspace ONE UEM Product Provisioning guide.
- Launcher admin passcode = 1111
Workspace ONE UEM not only provides industry-leading management of popular consumer devices, but also supports a robust and core feature set for managing rugged device fleets. Workspace ONE UEM's Product Provisioning is the feature set.
The Provisioning area in Workspace ONE UEM is the home of product provisioning. Within, administrators set up components, such as profiles, applications, and files/actions, which configure rugged devices. The components are bundled together in products, which are pushed to devices, unpacked, and installed. These products follow a set of rules, schedules, and dependencies as guidelines for ensuring your devices remain up to date with the content they need.
In order to get devices into UEM, they must first be staged and enrolled. Staging stakes place in Workspace ONE UEM's Lifecycle area.
Windows Mobile can be staged in two ways: barcode and sideload (Devices may also be web enrolled via the browser, but web is more of a legacy method). Barcode staging is covered herein.
- Using your TestDrive account, log in to TestDrive's RTU Workspace ONE UEM console.
- Use your Device Administrator at Retail Holding Company role.
- Go to Devices > Lifecycle > Staging > List View.
- Select the pre-configured staging profile that corresponds to your Windows device type.
- Generate a barcode with the shown values, enabling your device's barcode format:
As mentioned, provisioning occurs via packages of components. The packages are pushed to devices and locally executed via configurable parameters on each device.
Key components are described herein.
Several production components are copied and renamed with an "X" prefix. Please use these components to see the configured production functionality. Please be cautious to not modify or save the "X" components.
- The main profiles view contains a dashboard view device profiles to be used in product provisioning.
- Create and edit both staging and production profiles.
- Familiar workflow found in smartphone profile configuration.
- The AirWatch Launcher secures and locks down the rugged device.
- The Launcher has three configuration modes.
- Single app (kiosk)
- Multi-app (grid)(shown)
- Template mode - Fully customized, HTML5 WYSIWYG Launcher configuration
The production launcher profile is Warehouse - Launcher. It's copied as X Warehouse - Launcher for viewing and discussion aid.
- A file/action is the combination of the files you want on a device and the actions you want performed on the device with the file.
- From the manage your repository of managed files, scripts, Windows Mobile CABs, OS updates….
- The file/action needs a manifest action to provide the product either installation or uninstallation instructions.
Use the Windows Rugged platform configurations marked with an "X" to show how a the ARM agent is set up the device. Be certain to not save the profile.
- The Product List is a view of the "products" or packages that ares set up containing the prior-configured components. Products manage all of the profiles, apps, files/actions, and applied conditions for the deployment.
- Automation is a core aspect of VMware AirWatch. IT policies are mirrored in the product, where a products' manifest, schedule, and conditions create a hands-free device management environment. With Workspace ONE UEM, IT resources don't spend their valuable time micro managing individual devices.
- Product assignment supports both organizational groups and smart groups. While organization groups are typically defined by geographical location, business unit, and department, smart groups provide admins the flexibility to deploy products by device platform, model, operating system, device tag, or user group.
- Products are deployed via manifest actions and use device conditions for their deployment.
- The Product List View is the rugged admin's dashboard into all product installation statuses.
Use any of the viewable "X" products, i.e., "X Warehouse - ARM", to discuss and illustrate the setup of each component within the product. Review manifest actions, conditions, as well as deployment options.
Deployment options are key. They set the timeframe a product is in effect as well as wether the product is deployed either automatically deployed or electively (on demand).
- Device provisions fully locked down as set by the admin in the launcher profile.
- Users only have access to what admins have allowed in the launcher profile, both apps and device settings.
- Administrative access is granted after the passcode (set in the launcher profile) is entered. The device can be remotely administered via ARM with no user intervention required.
- Template mode is the 100% customizable, WYSIWYG device layout configuration. Text boxes, images, apps, and branding are configured in the launcher template profile via admin's HTML 5 UI.
Workspace ONE Assist
Please refer to Workspace ONE Assist documentation in docs.vmware.com.
- From the Workspace ONE UEM device list, select your Windows Rugged device, and drill into device details.
- On the top menu bar, select Remote Assist.
- After the session is successfully established, click the Launch Session button.
- Select Display Capture.
- After the display capture stages have completed, you should see the UI control view of the device, with its OEM model skin, locked down with the Launcher.