Exporting Apps and Creating Configuration Files
As of Workspace ONE UEM 1811, the IT administrator can leverage the provisioning wizard in the console to create the configuration file and export the apps. If you on console version pre-1811, please refer to the Exporting Apps to Provisioning Packages and Creating Configuration Files section. The IT administrator can configure OOBE, domain join and MDM enrollment from the wizard. Additionally, with a Windows 10 Enterprise license, the IT administrator can also choose to set the provisioning configuration for removal of consumer applications bundled with Windows 10. The active directory types that are supported for provisioning configuration are: on-premises domain join, Azure Active Directory Premium, Azure Active Directory - No Premium and local user/workgroup.
The provisioning configuration is exported in Windows unattend XML file format. This file follows the standard unattend XML schema, with some additional configuration for MDM enrollment into Workspace ONE UEM. The configuration is applied when the end user logs into the device.
Now that the enterprise applications are uploaded or imported using Workspace ONE AirLift (from SCCM) into Workspace ONE, the administrator is ready to export the applications into a provisioning package to share with Dell. The container used for this provisioning package is a Windows Provisioning Package (.ppkg) recognized natively by Windows 10. A custom mechanism is used in the PPKGs generated by Workspace ONE to install the applications, so it is not recommended for a customer to treat these PPKGs as generic PPKGs.
To export the enterprise applications, the IT administrator opens the Workspace ONE UEM console, and navigates to the Native Applications under the Apps & Books section. In the export dropdown, there is a new option to export PPKG. Selecting that option brings up a new dialog box with a list of applications to pick from. Currently, Windows classic desktop applications and Universal Windows Platform (UWP) apps which install in device or user context are supported.
Once the IT administrator initiates the PPKG export process, a confirmation is shown. On completion of PPKG export, a notification is sent to the Workspace ONE UEM console with a link to download the PPKG. A console administrator can have one PPKG export in progress at a time. To start a new PPKG export, the administrator needs to wait for the existing PPKG export to complete. A new PPKG export request overwrites any previously exported PPKG for that administrator. Multiple console administrators can concurrently request PPKGs to be exported though.
Lets take a look at how to export apps to provisioning packages and create the configuration file in the Workspace ONE UEM Console.
The above diagram shows the process of uploading, exporting and leveraging factory provisioning to load the apps and deliver the device to the end user.
- Workspace ONE UEM admin uploads apps to Workspace ONE UEM manually or using Workspace ONE AirLift.
- Workspace ONE UEM admin exports selected apps as a provisioning package (.ppkg).
- Admin provides the provisioning package, along with a configuration file to Dell.
- Dell performs factory provisioning using the exported apps and configuration file.
- Devices are shipped directly to end users or IT.
- End users boot device and device onboard into Workspace ONE UEM and receive app updates and other policies over-the-air.
1. New Provisioning Package
- Click Devices.
- Click Lifecycle.
- Click Staging.
- Click Windows.
1.1. New Windows Provisioning Package
Click New.
1.2. Export PPKG for Windows
- Enter
Tech Zone Corp
for the Provisioning Package Name. - Click Next.
1.3. Windows Provisioning Package
- Select Workgroup from the Active Directory Type dropdown.
- Enter
TechZone
for the Workgroup. - Enter
VMware1!
for the Administrator Password. - Scroll down to the bottom of the page.
The following screens will be leveraging the Workgroup Active Directory Type, reference the table with all options for more information and explanations of all required fields.
1.4. Configurations Details
The following table details all of the options for the configuration file. Leverage the below table for a detail explanation of each field.
|
1.5. Workspace ONE Enrollment Details
Enter ws1.airwlab.com
for the Enrollment Server.
We will now go back to the Workspace ONE UEM Console to obtain the following required information.
1.6. All Settings
Back in the Workspace ONE UEM Console,
- Click Groups & Settings.
- Click All Settings.
1.7. Staging & Provisioning
- Expand to Devices & Users > Windows > Windows Desktop > Staging & Provisioning.
- Copy the UPN value which will be used in the next step.
- Copy the Secret (staging password) value which will be used in the next step.
- Copy the Group ID by hovering over your email address. This value will be used in the next step.
1.8. Workspace ONE Enrollment Details
- Enter your Group ID obtained from the last step for Enrollment OG.
- Enter your UPN obtained from the last step for Staging Account.
- Enter your Secret obtained from the last step for Staging Account Password.
- Click Next.
1.9. Selecting Applications
- Click the checkbox at the top to select all apps.
- Click Next.
Apps with MSTs or MSPs will fail to deploy as those additional configurations are smart group specific, as a workaround re-package or ZIP the app with the MST/MSP already included then deploy and export.
1.10. Summary
Click Save and Export.
1.11. Success Message
Notice the Success message. Depending on how many apps you have chosen to export will determine how long the export takes. The Unattend XML configuration file will be ready to download right away. In this lab, it will take about 20 seconds to process the request, then you can refresh the page.
1.12. Confirm Unattend and Provisioning Package Download
- Click Unattend XML and PPKG to download.
- Confirm that the download was successful. We will use this exported provisioning package and unattend.xml in a future step.
These are the files which need to be sent to the Dell Factory for Provisioning, however you will first want to test and validate that these apps and configuration work on a test device. The next steps will walk you through how to validate on a virtual machine (VM). You will want to log back into the Workspace ONE UEM Console from the test VM to download these files.
0 Comments
Add your comment