Home > Demo Guides > Workspace ONE
*Windows 10 Out of Box Experience (OOBE)¶
*Omnissa Employees Only
This internal walkthrough guides you through enrolling Windows 10 using Microsoft's Out of Box Experience (OOBE). Once enrolled the device will provision as it does in the scripted Enterprise - Corporate Owned Demo. This guide describes the process using a Windows 10 Enterprise virtual machine.
Due to OOBE licensing requirements, this demo is only available using a shared demonstration account provided herein.
Overview¶
Before You Begin¶
You'll need the following:
- Device: Either a VM or physical Windows 10 Enterprise PC, at least version 1607, but 1703 or higher is recommended.
- VM
- Physical
A Windows 10 Enterprise VM—with snapshot taken during Windows 10 installation—is the recommended OOBE demo machine.
If you need an OOBE VM, the way to your own OOBE-ready VM is to build it using the Windows 10 1803 Business Editions ISO available here (TestDrive Office 365 account required.). OOBE VM build time: ~ 10 minutes, after ISO download.
Simply download the ISO, then using for ex. VMware Fusion or VMware Workstation, use the ISO to create a new VM. During VM creation, do NOT use the 'easy install' option. Choose "Windows 10 Enterprise" when prompted. When the VM setup is at the below pictured step (at the 'sign in' screen) snapshot the VM. This is where the OOBE demo begins!
(2:30 min.) showing start-to-finish building and snapshotting an OOBE VM.
If using a physical Windows 10 machine, from the command line, execute the following command to restart your PC in OOBE.
C:\Windows\System32\Sysprep\sysprep.exe /oobe
- You must use the cbabbage@asismon.com AAD licensed demo user account (internal only).
- No previous device record in the Workspace ONE UEM console. Since a shared demo account is used, make note of your device's serial number/UDID and delete that machine before a demo.
- Network access from your device to testdrive.awmdm.com over TCP ports 80 and 443.
- Optional configuration: To either disable or preconfigure most OOBE screens, you may use an unattended setup answer file during OOBE. Put the unattended setup answer file on a USB drive and insert before powering on. This and this Microsoft document will get you started.
Introduction¶
Windows 10 OOBE facilitates extraordinarily low configuration overhead for new PCs.
On a new machine, when prompted during setup, all a user needs to do is enter their corporate email and credentials, then Windows and Workspace ONE UEM set up the machine automatically. OOBE enrollment automatically enrolls a device into the correct Workspace ONE UEM organization group as part of the machines's initial setup and configuration. No administrator required!
Regarding demo timing, please be advised, OOBE enrollment can take considerable time to complete.
OOBE Enrollment¶
On the Windows 10 PC, on the "sign in with Microsoft" screen, enter the user's organizational email address for Office 365:
cbabbage@asismon.com
Tip¶
After restoring the snapshot, if booted to the sign-in screen, the VM may not connect to Microsoft upon initial sign in, causing an account validation error when you enter the email address. Rebooting should fix it.
At the Workspace ONE Access sign in, enter OOBE demo account credentials:
When prompted to choose a Group ID, choose corp.
Your device will enroll into the Enterprise - Corporate Owned Demo OG.
Group ID (OG) selection is a configurable enrollment mode in Workspace ONE UEM. TestDrive utilizes this setting to enable demo flow choice. This setting would not be configured for production OOBE.
Accept the privacy settings.
Since we are sharing a demo account, the user account's PIN configuration should be bypassed. When prompted, click Set up PIN. On the following screen, simply close the window. You'll receive a notification--skip it.
You're now ready to use the desktop. The device will provision as a corporate-liable device enrolled in the Enterprise - Corporate Owned Demo OG.
Device Provisioning¶
Please refer to the Windows Desktop - Endpoint Management guide.
OOBE provisioning time will vary, and may be considerable, due to the following factors:
- Windows is still setting itself up in the background and high priority system processes take priority over MDM provisioning.
- Computer and network performance
After the corporate device provisioning is underway, one of the first visible changes is the desktop wallpaper change. This change is made by Workspace ONE UEM product provisioning.
Additionally, through Workspace ONE UEM's software distribution over CDN, the Win32 Horizon Client will automatically provision with no user interaction required.
Login to the console (testdrive.awmdm.com) with the demo account (vmwdp.com\cbabbage).
Use the Device Administrator at World Wide Enterprisesadmin role.
Review the profiles and apps available to the device. Note the installed automatic profiles and optional profiles. Use each to guide your discussion as needed.
Key automatic profiles applied:
- Windows Defender firewall settings
- Corporate restrictions
- Windows Information Protection
- Windows Updates