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 VMware Workspace ONE Provisioning Tool.

1. Validate App Deployments on your Windows 10 Virtual Machine

The VMware Workspace ONE Provisioning Tool can be used to validate the application deployments in your PPKG file or simulate the full provisioning process by utilizing Sysprep and System Audit Mode.  

You will use the provided Windows 10 Virtual Machine to validate the application deployments, but you will not be able to connect to the Windows 10 Virtual Machine after Sysprep so you will not complete these steps in the Hands on Lab.  Instructions to review will be provided later to see the full process if you wish to test on a Windows 10 Virtual Machine outside of the Hands on Labs.

1.1. Launch the VMware Workspace ONE Provisioning Tool

  1. Click the File Explorer icon.
  2. Click This PC.
  3. Click Documents.
  4. Click HOL.
  5. Click Factory Provisioning.
  6. Double-click the VMwareWS1ProvisioningTool to launch the application.

Normally, you would need to VMware Workspace ONE Provisioning Tool, which is available through my.workspace.com (https://my.workspaceone.com/products/VMware-Workspace-ONE-Provisioning-Tool).  We have already downloaded the application and made it available for you to skip this process.

1.2. Provide the PPKG File

Click Select for the PPKG field.

1.2.1. Select the PPKG File

  1. Click Downloads.
  2. Click the corp local package.ppkg file.
  3. Click Open.

1.3. Provide the Configuration XML File

Click Select for the Configuration File (XML) field.

1.3.1. Select the Configuration XML File

  1. Click Downloads.
  2. Click the unattend.xml file.
  3. Click Open.

1.4. Apply the Applications from the PPKG File

Click Apply Apps Only to start installing the applications defined in your provided PPKG file.  

Once started, the results of the test will be posted to the right-section of the VMware Workspace ONE Provisioning Tool.  This process may take a few minutes to complete.

 

1.5. Validate that the VMware Workspace ONE Provisioning Tool Completed

Wait for the VMware Workspace ONE Provisioning Tool to complete.  The process has finished when the loading wheel disappears and the Status section shows checkmarks for all tasks and the final line shows Summary Report Created.

Once the VMware Workspace ONE Provisioning Tool has finished, the applications provided in the PPKG file have been installed. Continue to the next step to validate the application installs.

1.6. Validate That The Applications Were Installed

  1. Click the Windows button.
  2. Confirm that 7-Zip File Manager and Notepad++ show under the Recently added section.  Feel free to click and launch these applications to validate their install was successful.

Note that Google Chrome was already installed on this Virtual Machine, so that application does not show under Recently added.

You have successfully validated that the applications defined in your PPKG file have been successfully applied to your Windows 10 Virtual Machine.

2. Build and Validate on your own Windows 10 Virtual Machine (FOLLOW ALONG)

Note: DO NOT complete the following steps in your environment or you will be unable to connect to your Windows 10 Virtual Machine!

The following steps are provided as instructions for testing the full provisioning process with a Windows 10 Virtual Machine outside of the Hands on Labs environment.

If you are not interested in reviewing these steps, feel free to skip ahead to the next section.

2.1. Setup a fresh Windows 10 Virtual Machine to Test (FOLLOW ALONG)

Note: DO NOT complete the following steps in your environment or you will be unable to connect to your Windows 10 Virtual Machine!

  1. 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.
  2. Install Windows 10 on a fresh virtual machine (ideally 2 CPUs, 4+ GB RAM, 60 GB Hard Drive).
  3. 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.

2.2. Windows 10 Audit Mode (FOLLOW ALONG)

Note: DO NOT complete the following steps in your environment or you will be unable to connect to your Windows 10 Virtual Machine!

You know you have successfully entered Audit Mode when you see System Preparation Tool (Sysprep) running on the desktop.

2.3. Download the VMware Workspace ONE Provisioning Tool (FOLLOW ALONG)

Note: DO NOT complete the following steps in your environment or you will be unable to connect to your Windows 10 Virtual Machine!

  1. Open a web browser and navigate to https://my.workspaceone.com/products/VMware-Workspace-ONE-Provisioning-Tool.
  2. Enter the Platform, App Version, and Console Version for your environment.
  3. Click Installs and Upgrades.
  4. Click the VMware Workspace ONE Provisioning Tool download link.

2.4. VMware Workspace ONE Provisioning Tool (FOLLOW ALONG)

Note: DO NOT complete the following steps in your environment or you will be unable to connect to your Windows 10 Virtual Machine!

Once you launch the VMware Workspace ONE Provisioning Tool, you can 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 transfer these files directly to the virtual machine you are validating.

After supplying the Provisioning Package and configuration file, click one of the buttons depending on what you want to test:

  1. Click Apply Apps Only to only install apps from the PPKG file.
  2. Click Apply Full Process to initiate the end to end process of installing apps and applying the configuration file with Sysprep to test the full end user experience that would apply after receiving the device from Dell.

2.5. Notifications (FOLLOW ALONG)

Note: DO NOT complete the following steps in your environment or you will be unable to connect to your Windows 10 Virtual Machine!

The right panel of the VMware Workspace ONE Provisioning Tool will notify you of the progress of your tests.  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.

2.6. Confirm Installation of Apps (FOLLOW ALONG)

Note: DO NOT complete the following steps in your environment or you will be unable to connect to your Windows 10 Virtual Machine!

You can view the logs in C:\Dell to confirm the apps were installed. 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 sub-folders should match the number of apps exported and included in the provisioning package (ppkg) file.

2.7. Successfully Provisioned Device (FOLLOW ALONG)

Note: DO NOT complete the following steps in your environment or you will be unable to connect to your Windows 10 Virtual Machine!

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:

AD Type Description

Workgroup

 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.

3. 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.

3.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.

0 Comments

Add your comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.