Validating the Deployment on a Virtual Machine
Now that you have both enterprise applications and provisioning configuration packaged, the two files (.ppkg and unattend.xml) are ready to be uploaded to Dell. You would normally upload these files using a Dell File Transfer tool. Once the files are uploaded, the provisioning process starts in Dell facilities, where the two files are applied to the devices on top of a generic Windows 10 image with OEM drivers. The devices don’t have any connectivity to the internet during this process.
Once the devices are provisioned, they are shipped to the customers. The customers using on-premises domain join will need to get their devices shipped to IT first (or users with access to the corporate domain), where the devices will need to be turned on in the corporate network for automated on-premises domain join. After that, the IT administrator will shut down the devices, and send them to the end users. For other enterprise environments, the devices can be shipped directly to the end users.
Now let's validate and simulate this process on a virtual machine (VM) by using the Factory Provisioning Tool.
1. Build and Validate on your Windows 10 Virtual Machine
- You will first have to obtain a Windows 10 Pro (x64) .ISO from Microsoft Volume site or MSDN. Please use the latest two builds of Windows 10 as those will be the versions offered by Factory Provisioning.
- Install Windows 10 on a fresh virtual machine (ideally 2 CPUs, 4+ GB RAM, 60 GB Hard Drive).
- Once it enters OOBE, get the system into Audit Mode by pressing Ctrl+Shift+F3. (or Ctrl+Shift+Fn+F3 on some systems) You can also enter Audit Mode by running Sysprep and set the System Cleanup Action to Enter System Audit Mode.
1.1. Windows 10 Audit Mode
You know you have successfully entered Audit Mode when you see System Preparation Tool (Sysprep) running on the desktop.
1.2. Download and Launch the Factory Provisioning Tool
- Click on the Microsoft Edge icon on the taskbar.
- Enter https://code.vmware.com/samples/4702 into the address bar, then press Enter.
- Click Download.
1.3. Workspace ONE Factory Provisioning Tool
You can now select your provisioning package (.ppkg) and your configuration file (unattend.xml) that was created previously using the New Provisioning Package wizard in the Workspace ONE UEM Console. You will want to make sure to transfer these files directly to the virtual machine you are validating by copying onto the desktop for example.
Click one of the three buttons depending on what you are wanting to test:
- Click Apply PPKG Only to only install apps from the PPKG.
- Click Apply XML and Sysprep Only to only apply the configuration file, then Sysprep to test the end user experience without pre-loading apps.
- Click Apply PPKG, XML, and Sysprep to initiate the end to end process, mimicking what Dell is doing in the factory.
The bottom of the Workspace ONE Factory Provisioning Tool will notify you of the progress but you can also view detailed logs at C:\Dell.
Note: The Workspace ONE Factory Provisioning Tool requires internet access on the system to download the Workspace ONE Intelligent Hub and the Workspace ONE app.
1.5. Confirm Installation of Apps
You can view the log in C:\Dell. You can also verify the app installation on the machine by looking into Registry at HKEY_LOCAL_MACHINE\SOFTWARE\AIRWATCHMDM\AppDeploymentAgent\S-1-5-18. The number of folders should match the number of apps exported and included in the provisioning package.
1.6. Successfully Provisioned Device
Once the system comes back you will notice the device is enrolled and has all of the apps installed and will receive any new apps from Workspace ONE UEM, as well as other policies and configuration over-the-air.
The system will go through the workflow as defined in the configuration file, here are the expected workflows:
|OOBE will prompt for username creation as well as password. Once logged in, the Workspace ONE Intelligent Hub will prompt for credentials. (refer to image below) Be sure to enter end-user's Active Directory credentials or the credentials that are synced into the Workspace ONE console.
On-Premises Domain Join
||Ensure that the system is plugged into LAN that has access to a domain controller before booting. Once booted, system will join the domain and automatically log in as local administrator so that you can stage enrollment. Once enrollment has completed to the staging user, log out and then login using the end user's domain account. Workspace ONE enrollment will automatically flip to the domain user.
Azure Active Directory Premium
Go through OOBE and authenticate with Azure Active Directory credentials. These credentials should also be synced into Workspace ONE UEM console, otherwise enrollment will fail.
Azure Active Directory Basic
||Go through OOBE and authenticate with Azure Active Directory credentials. Once logged in, Workspace ONE will prompt for credentials (just like it does on workgroup). Be sure to enter end-user's Active Directory credentials or the credentials that are synced into the Workspace ONE console.
2. Verification, Tips, and Next Steps
- Ensure all of the Workspace ONE Intelligent Hub (AirWatch) services are running on the device.
- Ensure that the Workspace ONE app is launched and taking the user to their Digital Workspace, if configured.
- If using the Domain Join workflow, don't forget to log out and log in as the AD end user.
- Ensure that users can install apps on-demand and profiles assigned to the user are installing.
For more information about troubleshooting please refer to the Windows 10 Troubleshooting Operational Tutorial.
2.1. Next Steps
Now that you have validated your Workspace ONE environment and onboarding workflow you will need to contact Dell Configuration Services to initiate the project on the Dell side. A Dell resource will contact you and setup a new project for this factory service.