Microsoft Windows 10 Stuck On Oobe In Vm On Mac

-->

If you are installing Windows 10 on a PC running Windows XP or Windows Vista, or if you need to create installation media to install Windows 10 on a different PC, see Using the tool to create installation media (USB flash drive, DVD, or ISO file) to install Windows 10. Since Windows 10 1903, Microsoft quietly changed the Windows Out-of-box Experience (OOBE) or setup experience so that many users are no longer able to create a local account during set up as they.

When you try to create a new Azure Virtual Machine (VM), the common errors you encounter are provisioning failures or allocation failures.

  1. In order for your Windows 10 device to go through OOBE it should have a fresh image deployed - or for our VM scenario - it needs to have the sysprep process run against it. This is as simple as opening a Command Prompt (as an administrator) and running sysprep using the commands.
  2. Or, you can configure Windows to boot to the Out-of-Box Experience (OOBE). This is great so you can sysprep a virtual machine copy the VHD or VHDX file and use it for the first boot of different VMs. In Windows Server 2012 and Windows 8, Microsoft added an addition to sysprep called the mode switch “/mode:vm”.
  3. Windows 10, version 2004 (10.0.19041.0) Windows 10 SDK, version 2004 (10.0.19041.0) Visual Studio 2019 (latest as of 1/15/21) with the UWP,.NET desktop, and Azure workflows enabled and also includes the Windows Template Studio extension.
  • A provisioning failure happens when the OS image fails to load either due to incorrect preparatory steps or because of selecting the wrong settings during the image capture from the portal.
  • An allocation failure results when the cluster or region either does not have resources available or cannot support the requested VM size.

If your Azure issue is not addressed in this article, visit the Azure forums on MSDN and Stack Overflow. You can post your issue in these forums, or post to @AzureSupport on Twitter. You also can submit an Azure support request. To submit a support request, on the Azure support page, select Get support.

Top issues

Mac

The following top issues may help resolve your issue. To start troubleshooting, review these steps:

For other VM deployment issues and questions, see Troubleshoot deploying Windows virtual machine issues in Azure.

Collect activity logs

To start troubleshooting, collect the activity logs to identify the error associated with the issue. The following links contain detailed information on the process to follow.

Issue: Custom image; provisioning errors

Provisioning errors arise if you upload or capture a generalized VM image as a specialized VM image or vice versa. The former will cause a provisioning timeout error and the latter will cause a provisioning failure. To deploy your custom image without errors, you must ensure that the type of the image does not change during the capture process.

The following table lists the possible combinations of generalized and specialized images, the error type you will encounter and what you need to do to fix the errors.

The following table lists the possible upload and capture combinations of Windows generalized (gen.) and specialized (spec.) OS images. The combinations that will process without any errors are indicated by a Y, and those that will throw errors are indicated by an N. The causes and resolutions for the different errors you will run into are given below the table.

OSUpload spec.Upload gen.Capture spec.Capture gen.
Windows gen.N1YN3Y
Windows spec.YN2YN4

Y: If the OS is Windows generalized, and it is uploaded and/or captured with the generalized setting, then there won’t be any errors. Similarly, if the OS is Windows specialized, and it is uploaded and/or captured with the specialized setting, then there won’t be any errors.

Upload Errors:

N1: If the OS is Windows generalized, and it is uploaded as specialized, you will get a provisioning timeout error with the VM stuck at the OOBE screen.

N2: If the OS is Windows specialized, and it is uploaded as generalized, you will get a provisioning failure error with the VM stuck at the OOBE screen because the new VM is running with the original computer name, username and password.

Resolution

To resolve both these errors, use Add-AzVhd to upload the original VHD, available on-premises, with the same setting as that for the OS (generalized/specialized). To upload as generalized, remember to run sysprep first.

Capture Errors:

N3: If the OS is Windows generalized, and it is captured as specialized, you will get a provisioning timeout error because the original VM is not usable as it is marked as generalized.

N4: If the OS is Windows specialized, and it is captured as generalized, you will get a provisioning failure error because the new VM is running with the original computer name, username, and password. Also, the original VM is not usable because it is marked as specialized.

Resolution

To resolve both these errors, delete the current image from the portal, and recapture it from the current VHDs with the same setting as that for the OS (generalized/specialized).

Issue: Custom/gallery/marketplace image; allocation failure

This error arises in situations when the new VM request is pinned to a cluster that either cannot support the VM size being requested, or does not have available free space to accommodate the request.

Cause 1: The cluster cannot support the requested VM size.

Resolution 1:

  • Retry the request using a smaller VM size.
  • If the size of the requested VM cannot be changed:
    • Stop all the VMs in the availability set.Click Resource groups > your resource group > Resources > your availability set > Virtual Machines > your virtual machine > Stop.
    • After all the VMs stop, create the new VM in the desired size.
    • Start the new VM first, and then select each of the stopped VMs and click Start.

Cause 2: The cluster does not have free resources.

Resolution 2:

  • Retry the request at a later time.
  • If the new VM can be part of a different availability set
    • Create a new VM in a different availability set (in the same region).
    • Add the new VM to the same virtual network.

Next steps

If you encounter issues when you start a stopped Windows VM or resize an existing Windows VM in Azure, see Troubleshoot Resource Manager deployment issues with restarting or resizing an existing Windows Virtual Machine in Azure.

-->

Applies to

  • Windows 10

To get started with Windows Autopilot, you should try it out with a virtual machine (VM) or you can use a physical device that will be wiped and then have a fresh install of Windows 10.

In this topic you'll learn how to set-up a Windows Autopilot deployment for a VM using Hyper-V.

Note

Although there are multiple platforms available to enable Autopilot, this lab primarily uses Intune.

Hyper-V and a VM are not required for this lab. You can also use a physical device. However, the instructions assume that you are using a VM. To use a physical device, skip the instructions to install Hyper-V and create a VM. All references to 'device' in the guide refer to the client device, either physical or virtual.

The following video provides an overview of the process:

Microsoft Windows 10 Stuck On Oobe In Vm On Mac Catalina


For a list of terms used in this guide, see the Glossary section.

Prerequisites

These are the things you'll need to complete this lab:

Windows 10 installation mediaWindows 10 Professional or Enterprise (ISO file) for a supported version of Windows 10, semi-annual channel. If you do not already have an ISO to use, a link is provided to download an evaluation version of Windows 10 Enterprise.
Internet accessIf you are behind a firewall, see the detailed networking requirements. Otherwise, just ensure that you have a connection to the Internet.
Hyper-V or a physical device running Windows 10The guide assumes that you will use a Hyper-V VM, and provides instructions to install and configure Hyper-V if needed. To use a physical device, skip the steps to install and configure Hyper-V.
A Premium Intune accountThis guide will describe how to obtain a free 30-day trial premium account that can be used to complete the lab.

Procedures

A summary of the sections and procedures in the lab is provided below. Follow each section in the order it is presented, skipping the sections that do not apply to you. Optional procedures are provided in the appendix.

If you already have Hyper-V and a Windows 10 VM, you can skip directly to the Capture the hardware ID step. The VM must be running Windows 10, version 1903 or a later version.

Verify support for Hyper-V
Enable Hyper-V
Create a demo VM
Set ISO file location
Determine network adapter name
Use Windows PowerShell to create the demo VM
Install Windows 10
Capture the hardware ID
Reset the VM back to Out-Of-Box-Experience (OOBE)
Verify subscription level
Configure company branding
Configure Microsoft Intune auto-enrollment
Register your VM
Autopilot registration using Intune
Autopilot registration using MSfB
Create and assign a Windows Autopilot deployment profile
Create a Windows Autopilot deployment profile using Intune
Create a device group
Create the deployment profile
Create a Windows Autopilot deployment profile using MSfB
See Windows Autopilot in action
Remove devices from Autopilot
Delete (deregister) Autopilot device
Appendix A: Verify support for Hyper-V
Appendix B: Adding apps to your profile
Add a Win32 app
Prepare the app for Intune
Create app in Intune
Assign the app to your Intune profile
Add Office 365
Create app in Intune
Assign the app to your Intune profile
Glossary

Verify support for Hyper-V

If you don't already have Hyper-V, we must first enable this on a computer running Windows 10 or Windows Server (2012 R2 or later).

If you already have Hyper-V enabled, skip to the create a demo VM step. If you are using a physical device instead of a VM, skip to Install Windows 10.

Firstly, sign in to the G Suite admin console through administrator’s credentials i.e., username and password. If a user is not dependent on a password, then he/she can also assign a temporary password by resetting the password for every mailbox. G suite migration for microsoft outlook for mac. For creating a list, the users can follow the steps below:. A user can add maximum 50,000 mailboxes in the migration file & the file can have 10 MB large size.

If you are not sure that your device supports Hyper-V, or you have problems installing Hyper-V, see appendix A below for details on verifying that Hyper-V can be successfully installed.

Enable Hyper-V

To enable Hyper-V, open an elevated Windows PowerShell prompt and run the following command:

This command works on all operating systems that support Hyper-V, but on Windows Server operating systems you must type an additional command (below) to add the Hyper-V Windows PowerShell module and the Hyper-V Manager console. The following command will also install Hyper-V if it isn't already installed, so if you're using Windows Server, you can just type the following command instead of using the Enable-WindowsOptionalFeature command:

When you are prompted to restart the computer, choose Yes. The computer might restart more than once.

Alternatively, you can install Hyper-V using the Control Panel in Windows under Turn Windows features on or off for a client operating system, or using Server Manager's Add Roles and Features Wizard on a server operating system, as shown below:

If you choose to install Hyper-V using Server Manager, accept all default selections. Also be sure to install both items under Role Administration ToolsHyper-V Management Tools.

After installation is complete, open Hyper-V Manager by typing virtmgmt.msc at an elevated command prompt, or by typing Hyper-V in the Start menu search box.

To read more about Hyper-V, see Introduction to Hyper-V on Windows 10 and Hyper-V on Windows Server.

Create a demo VM

Now that Hyper-V is enabled, we need to create a VM running Windows 10. We can create a VM and virtual network using Hyper-V Manager, but it is simpler to use Windows PowerShell.

To use Windows PowerShell, we just need to know two things:

  1. The location of the Windows 10 ISO file.
    • In the example, we assume the location is c:isowin10-eval.iso.
  2. The name of the network interface that connects to the Internet.
    • In the example, we use a Windows PowerShell command to determine this automatically.

After we have set the ISO file location and determined the name of the appropriate network interface, we can install Windows 10.

Set ISO file location

You can download an ISO file for an evaluation version of the latest release of Windows 10 Enterprise here.

  • When asked to select a platform, choose 64 bit.

After you download this file, the name will be extremely long (ex: 19042.508.200927-1902.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-us.iso).

  1. So that it is easier to type and remember, rename the file to win10-eval.iso.
  2. Create a directory on your computer named c:iso and move the win10-eval.iso file there, so the path to the file is c:isowin10-eval.iso.
  3. If you wish to use a different name and location for the file, you must modify the Windows PowerShell commands below to use your custom name and directory.

Determine network adapter name

The Get-NetAdaper cmdlet is used below to automatically find the network adapter that is most likely to be the one you use to connect to the Internet. You should test this command first by running the following at an elevated Windows PowerShell prompt:

The output of this command should be the name of the network interface you use to connect to the Internet. Verify that this is the correct interface name. If it is not the correct interface name, you'll need to edit the first command below to use your network interface name.

For example, if the command above displays Ethernet but you wish to use Ethernet2, then the first command below would be New-VMSwitch -Name AutopilotExternal -AllowManagementOS $true -NetAdapterName Ethernet2.

Use Windows PowerShell to create the demo VM

All VM data will be created under the current path in your PowerShell prompt. Consider navigating into a new folder before running the following commands.

Important

VM switch: a VM switch is how Hyper-V connects VMs to a network.
If you have previously enabled Hyper-V and your Internet-connected network interface is already bound to a VM switch, then the PowerShell commands below will fail. In this case, you can either delete the existing VM switch (so that the commands below can create one), or you can reuse this VM switch by skipping the first command below and either modifying the second command to replace the switch name AutopilotExternal with the name of your switch, or by renaming your existing switch to 'AutopilotExternal.'
If you have never created an external VM switch before, then just run the commands below.
If you are not sure if you already have an External VM switch, enter get-vmswitch at a Windows PowerShell prompt to display a currently list of the VM switches that are provisioned in Hyper-V. If one of them is of SwitchType External, then you already have a VM switch configured on the server that is used to connect to the Internet. In this case, you need to skip the first command below and modify the others to use the name of your VM switch instead of the name 'AutopilotExternal' (or change the name of your switch).

After entering these commands, connect to the VM that you just created and wait for a prompt to press a key and boot from the DVD. You can connect to the VM by double-clicking it in Hyper-V Manager.

See the sample output below. In this sample, the VM is created under the c:autopilot directory and the vmconnect.exe command is used (which is only available on Windows Server). If you installed Hyper-V on Windows 10, use Hyper-V Manager to connect to your VM.

Install Windows 10

Note

The VM will be booted to gather a hardware ID, then it will be reset. The goal in the next few steps is to get to the desktop quickly so don't worry about how it is configured at this stage. The VM only needs to be connected to the Internet.

Ensure the VM booted from the installation ISO, click Next then click Install now and complete the Windows installation process. See the following examples:

After the VM restarts, during OOBE, it's fine to select Set up for personal use or Domain join instead and then choose an offline account on the Sign in screen. This will offer the fastest way to the desktop. For example:

Once the installation is complete, sign in and verify that you are at the Windows 10 desktop, then create your first Hyper-V checkpoint. Checkpoints are used to restore the VM to a previous state. You will create multiple checkpoints throughout this lab, which can be used later to go through the process again.

To create your first checkpoint, open an elevated Windows PowerShell prompt on the computer running Hyper-V (not on the VM) and run the following:

Click on the WindowsAutopilot VM in Hyper-V Manager and verify that you see Finished Windows Install listed in the Checkpoints pane.

Microsoft Windows 10 Stuck On Oobe In Vm On Mac Computer

Capture the hardware ID

Note

Normally, the Device ID is captured by the OEM as they run the OA3 Tool on each device in the factory. The OEM then submits the 4K HH created by the OA3 Tool to Microsoft by submitting it with a Computer Build Report (CBR). For purposes of this lab, you are acting as the OEM (capturing the 4K HH), but you're not going to use the OA3 Tool to capture the full 4K HH for various reasons (you'd have to install the OA3 tool, your device couldn't have a volume license version of Windows, it's a more complicated process than using a PS script, etc.). Instead, you'll simulate running the OA3 tool by running a PowerShell script, which captures the device 4K HH just like the OA3 tool.

Follow these steps to run the PS script:

  1. On the client VM: Open an elevated Windows PowerShell prompt and run the following commands. These commands are the same regardless of whether you are using a VM or a physical device:

When you are prompted to install the NuGet package, choose Yes.

See the sample output below. A 'dir' command is issued at the end to show the file that was created.

Verify that there is an AutopilotHWID.csv file in the c:HWID directory that is about 8 KB in size. This file contains the complete 4K HH.

Note

Although the .csv extension might be associated with Microsoft Excel, you cannot view the file properly by double-clicking it. To correctly parse the comma delimiters and view the file in Excel, you must use the Data > From Text/CSV function in Excel to import the appropriate data columns. You don't need to view the file in Excel unless you are curious. The file format will be validated when it is imported into Autopilot. An example of the data in this file is shown below.

You will need to upload this data into Intune to register your device for Autopilot, so the next step is to transfer this file to the computer you will use to access the Azure portal. If you are using a physical device instead of a VM, you can copy the file to a USB stick. If you’re using a VM, you can right-click the AutopilotHWID.csv file and copy it, then right-click and paste the file to your desktop (outside the VM).

If you have trouble copying and pasting the file, just view the contents in Notepad on the VM and copy the text into Notepad outside the VM. Do not use another text editor to do this.

Note

When copying and pasting to or from VMs, avoid clicking other things with your mouse cursor between the copy and paste process as this can empty or overwrite the clipboard and require that you start over. Go directly from copy to paste.

Reset the VM back to Out-Of-Box-Experience (OOBE)

With the hardware ID captured in a file, prepare your Virtual Machine for Windows Autopilot deployment by resetting it back to OOBE.

Microsoft Windows 10 Stuck On Oobe In Vm On Mac Desktop

On the Virtual Machine, go to Settings > Update & Security > Recovery and click on Get started under Reset this PC.Select Remove everything and Just remove my files. If you are asked How would you like to reinstall Windows, select Local reinstall. Finally, click on Reset.

Resetting the VM or device can take a while. Proceed to the next step (verify subscription level) during the reset process.

Verify subscription level

For this lab, you need an AAD Premium subscription. You can tell if you have a Premium subscription by navigating to the MDM enrollment configuration blade. See the following example:

Azure Active Directory > Mobility (MDM and MAM) > Microsoft Intune

If the configuration blade shown above does not appear, it's likely that you don't have a Premium subscription. Auto-enrollment is a feature only available in AAD Premium.

To convert your Intune trial account to a free Premium trial account, navigate to Azure Active Directory > Licenses > All products > Try / Buy and select Free trial for Azure AD Premium, or EMS E5.

Configure company branding

If you already have company branding configured in Azure Active Directory, you can skip this step.

Important

Make sure to sign-in with a Global Administrator account.

Navigate to Company branding in Azure Active Directory, click on Configure and configure any type of company branding you'd like to see during the OOBE.

When you are finished, click Save.

Note

Changes to company branding can take up to 30 minutes to apply.

Configure Microsoft Intune auto-enrollment

If you already have MDM auto-enrollment configured in Azure Active Directory, you can skip this step.

Open Mobility (MDM and MAM) in Azure Active Directory and select Microsoft Intune. If you do not see Microsoft Intune, click Add application and choose Intune.

For the purposes of this demo, select All under the MDM user scope and click Save.

Register your VM

Your VM (or device) can be registered either via Intune or Microsoft Store for Business (MSfB). Both processes are shown here, but only pick one for purposes of this lab. We highly recommend using Intune rather than MSfB.

Autopilot registration using Intune

  1. In the Microsoft Endpoint Manager admin center, choose Devices > Device enrollment Enroll devices > Windows enrollment > Windows Autopilot Deployment Program Devices and then on the Windows Autopilot devices page, choose Import.

    Note

    If menu items like Windows enrollment are not active for you, then look to the far-right blade in the UI. You might need to provide Intune configuration privileges in a challenge window that appeared.

  2. Under Add Windows Autopilot devices in the far right pane, browse to the AutopilotHWID.csv file you previously copied to your local computer. The file should contain the serial number and 4K HH of your VM (or device). It's okay if other fields (Windows Product ID) are left blank.

    You should receive confirmation that the file is formatted correctly before uploading it, as shown above.

  3. Click Import and wait until the import process completes. This can take up to 15 minutes.

  4. Click Refresh to verify your VM or device has been added. See the following example.

Autopilot registration using MSfB

Important

If you've already registered your VM (or device) using Intune, then skip this step.

Optional: see the following video for an overview of the process.

First, you need a MSfB account. You can use the same one you created above for Intune, or follow these instructions to create a new one.

Next, sign in to Microsoft Store for Business using your test account by clicking Sign in on the upper-right-corner of the main page.

Select Manage from the top menu, then click the Windows Autopilot Deployment Program link under the Devices card. See the following example:

Click the Add devices link to upload your CSV file. A message will appear indicating your request is being processed. Wait a few moments before refreshing to see your new device has been added.

Create and assign a Windows Autopilot deployment profile

Important

Autopilot profiles can be created and assigned to your registered VM or device either through Intune or MSfB. Both processes are shown here, but only pick one for purposes of this lab:

Pick one:

Create a Windows Autopilot deployment profile using Intune

Note

Even if you registered your device in MSfB, it will still appear in Intune, though you might have to sync and then refresh your device list.

Create a device group

The Autopilot deployment profile wizard will ask for a device group, so we must create one first. To create a device group:

  1. In the Microsoft Endpoint Manager admin center, choose Groups > New group.
  2. In the Group blade:
    1. For Group type, choose Security.
    2. Type a Group name and Group description (ex: Autopilot Lab).
    3. Azure AD roles can be assigned to the group: No
    4. For Membership type, choose Assigned.
  3. Click Members and add the Autopilot VM to the group. See the following example:
  1. Click Create.

Create the deployment profile

To create a Windows Autopilot profile, scroll back to the left hand pane and click Devices, then under Enroll devices Windows enrollment select Deployment Profiles.

Click on Create profile and then select Windows PC.

On the Create profile blade, use the following values:

SettingValue
NameAutopilot Lab profile
DescriptionLab
Convert all targeted devices to AutopilotNo

Click Next to continue with the Out-of-box experience (OOBE) settings:

SettingValue
Deployment modeUser-driven
Join to Azure AD asAzure AD joined
Microsoft Sofware License TermsHide
Privacy SettingsHide
Hide change account optionsHide
User account typeStandard
Allow White Glove OOBENo
Language (Region)Operating system default
Automatically configure keyboardYes
Apply device name templateNo

Click Next to continue with the Assignments settings:

SettingValue
Assign toSelected groups
  1. Click Select groups to include.
  2. Click the Autopilot Lab group, and then click Select.
  3. Click Next to continue and then click Create. See the following example:

Click on OK and then click on Create.

If you want to add an app to your profile via Intune, the OPTIONAL steps for doing so can be found in Appendix B: Adding apps to your profile.

Create a Windows Autopilot deployment profile using MSfB

If you have already created and assigned a profile via Intune by using the steps immediately above, then skip this section.

A video is available that covers the steps required to create and assign profiles in MSfB. These steps are also summarized below.

First, sign in to the Microsoft Store for Business using the Intune account you initially created for this lab.

Click Manage from the top menu, then click Devices from the left navigation tree.

Click the Windows Autopilot Deployment Program link in the Devices tile.

To CREATE the profile:

Select your device from the Devices list:

On the Autopilot deployment dropdown menu, select Create new profile:

Name the profile, choose your desired settings, and then click Create:

The new profile is added to the Autopilot deployment list.

To ASSIGN the profile:

To assign (or reassign) the profile to a device, select the checkboxes next to the device you registered for this lab, then select the profile you want to assign from the Autopilot deployment dropdown menu as shown:

Confirm the profile was successfully assigned to the intended device by checking the contents of the Profile column:

Important

The new profile will only be applied if the device has not been started, and gone through OOBE. Settings from a different profile can't be applied when another profile has been applied. Windows would need to be reinstalled on the device for the second profile to be applied to the device.

See Windows Autopilot in action

If you shut down your VM after the last reset, it's time to start it back up again, so it can progress through the Autopilot OOBE experience but do not attempt to start your device again until the PROFILE STATUS for your device in Intune has changed from Not assigned to Assigning and finally Assigned:

Also, make sure to wait at least 30 minutes from the time you've configured company branding, otherwise these changes might not show up.

Tip

If you reset your device previously after collecting the 4K HH info, and then let it restart back to the first OOBE screen, then you might need to restart the device again to ensure the device is recognized as an Autopilot device and displays the Autopilot OOBE experience you're expecting. If you do not see the Autopilot OOBE experience, then reset the device again (Settings > Update & Security > Recovery and click on Get started. Under Reset this PC, select Remove everything and Just remove my files. Click on Reset).

  • Ensure your device has an internet connection.
  • Turn on the device
  • Verify that the appropriate OOBE screens (with appropriate Company Branding) appear. You should see the region selection screen, the keyboard selection screen, and the second keyboard selection screen (which you can skip).

Soon after reaching the desktop, the device should show up in Intune as an enabled Autopilot device. Go into the Intune Azure portal, and select Devices > All devices, then Refresh the data to verify that your device has changed from disabled to enabled, and the name of the device is updated.

Once you select a language and a keyboard layout, your company branded sign-in screen should appear. Provide your Azure Active Directory credentials and you're all done.

Tip

If you recieve a message that 'Something went wrong' and it 'Looks like we can't connect to the URL for your organization's MDM terms of use' then verify you have correctly assigned licenses to the current user.

Windows Autopilot will now take over to automatically join your device into Azure Active Directory and enroll it to Microsoft Intune. Use the checkpoints you've created to go through this process again with different settings.

Remove devices from Autopilot

To use the device (or VM) for other purposes after completion of this lab, you will need to remove (deregister) it from Autopilot via either Intune or MSfB, and then reset it. Instructions for deregistering devices can be found at Enroll Windows devices in Intune by using Windows Autopilot and Remove devices by using wipe, retire, or manually unenrolling the device and below.

Delete (deregister) Autopilot device

You need to delete (or retire, or factory reset) the device from Intune before deregistering the device from Autopilot. To delete the device from Intune (not Azure Active Directory), log into the MEM admin center, then navigate to Intune > Devices > All Devices. Select the device you want to delete, then click the Delete button along the top menu.

This will remove the device from Intune management, and it will disappear from Intune > Devices > All devices. But this does not yet deregister the device from Autopilot, so the device should still appear under Intune > Device Enrollment > Windows Enrollment > Windows Autopilot Deployment Program > Devices.

The Intune > Devices > All Devices list and the Intune > Device Enrollment > Windows Enrollment > Windows Autopilot Deployment Program > Devices list mean different things and are two completely separate datastores. The former (All devices) is the list of devices currently enrolled into Intune.

Windows

Note

A device will only appear in the All devices list once it has booted. The latter (Windows Autopilot Deployment Program > Devices) is the list of devices currently registered from that Intune account into the Autopilot program - which may or may not be enrolled to Intune.

To remove the device from the Autopilot program, select the device and click Delete. You will get a popup dialog box to confirm deletion.

At this point, your device has been unenrolled from Intune and also deregistered from Autopilot. After several minutes, click the Sync button, followed by the Refresh button to confirm the device is no longer listed in the Autopilot program:

Once the device no longer appears, you are free to reuse it for other purposes.

If you also (optionally) want to remove your device from AAD, navigate to Azure Active Directory > Devices > All Devices, select your device, and click the delete button:

Appendix A: Verify support for Hyper-V

Starting with Windows 8, the host computer's microprocessor must support second level address translation (SLAT) to install Hyper-V. See Hyper-V: List of SLAT-Capable CPUs for Hosts for more information.

To verify your computer supports SLAT, open an administrator command prompt, type systeminfo, press ENTER, scroll down, and review the section displayed at the bottom of the output, next to Hyper-V Requirements. See the following example:

In this example, the computer supports SLAT and Hyper-V.

If one or more requirements are evaluated as No then the computer does not support installing Hyper-V. However, if only the virtualization setting is incompatible, you might be able to enable virtualization in the BIOS and change the Virtualization Enabled In Firmware setting from No to Yes. The location of this setting will depend on the manufacturer and BIOS version, but is typically found associated with the BIOS security settings.

You can also identify Hyper-V support using tools provided by the processor manufacturer, the msinfo32 tool, or you can download the Coreinfo utility and run it, as shown in the following example:

Note

A 64-bit operating system is required to run Hyper-V.

Appendix B: Adding apps to your profile

Add a Win32 app

Prepare the app for Intune

Before we can pull an application into Intune to make it part of our AP profile, we need to 'package' the application for delivery using the IntuneWinAppUtil.exe command-line tool. After downloading the tool, gather the following three bits of information to use the tool:

  1. The source folder for your application
  2. The name of the setup executable file
  3. The output folder for the new file

For the purposes of this lab, we'll use the Notepad++ tool as our Win32 app.

Download the Notepad++ msi package here and then copy the file to a known location, such as C:Notepad++msi.

Run the IntuneWinAppUtil tool, supplying answers to the three questions, for example:

After the tool finishes running, you should have an .intunewin file in the Output folder, which you can now upload into Intune using the following steps.

Create app in Intune

Log into the Azure portal and select Intune.

Navigate to Intune > Clients apps > Apps, and then click the Add button to create a new app package.

Under App Type, select Windows app (Win32):

On the App package file blade, browse to the npp.7.6.3.installer.x64.intunewin file in your output folder, open it, then click OK:

On the App Information Configure blade, provide a friendly name, description, and publisher, such as:

On the Program Configuration blade, supply the install and uninstall commands:

Install: msiexec /i 'npp.7.6.3.installer.x64.msi' /qUninstall: msiexec /x '{F188A506-C3C6-4411-BE3A-DA5BF1EA6737}' /q

Note

Likely, you do not have to write the install and uninstall commands yourself because the IntuneWinAppUtil.exe command-line tool automatically generated them when it converted the .msi file into a .intunewin file.

Simply using an install command like 'notepad++.exe /S' will not actually install Notepad++; it will only launch the app. To actually install the program, we need to use the .msi file instead. Notepad++ doesn't actually have an .msi version of their program, but we got an .msi version from a third party provider.

Click OK to save your input and activate the Requirements blade.

On the Requirements Configuration blade, specify the OS architecture and the Minimum OS version:

Next, configure the Detection rules. For our purposes, we will select manual format:

Click Add to define the rule properties. For Rule type, select MSI, which will automatically import the right MSI product code into the rule:

Click OK twice to save, as you back out to the main Add app blade again for the final configuration.

Return codes: For our purposes, leave the return codes at their default values:

Click OK to exit.

You may skip configuring the final Scope (Tags) blade.

Click the Add button to finalize and save your app package.

Once the indicator message says the addition has completed.

You will be able to find your app in your app list:

Assign the app to your Intune profile

Note

The following steps only work if you previously created a GROUP in Intune and assigned a profile to it. If you have not done that, please return to the main part of the lab and complete those steps before returning here.

In the Intune > Client Apps > Apps pane, select the app package you already created to reveal its properties blade. Then click Assignments from the menu:

Select Add Group to open the Add group pane that is related to the app.

For our purposes, select Required from the Assignment type dropdown menu:

Available for enrolled devices means users install the app from the Company Portal app or Company Portal website.

Select Included Groups and assign the groups you previously created that will use this app:

In the Select groups pane, click the Select button.

In the Assign group pane, select OK.

In the Add group pane, select OK.

In the app Assignments pane, select Save.

At this point, you have completed steps to add a Win32 app to Intune.

For more information on adding apps to Intune, see Intune Standalone - Win32 app management.

Add Office 365

Create app in Intune

Log into the Azure portal and select Intune.

Navigate to Intune > Clients apps > Apps, and then click the Add button to create a new app package.

Under App Type, select Office 365 Suite > Windows 10:

Under the Configure App Suite pane, select the Office apps you want to install. For the purposes of this labe we have only selected Excel:

Click OK.

In the App Suite Information pane, enter a unique suite name, and a suitable description.

Enter the name of the app suite as it is displayed in the company portal. Make sure that all suite names that you use are unique. If the same app suite name exists twice, only one of the apps is displayed to users in the company portal.

Click OK.

In the App Suite Settings pane, select Monthly for the Update channel (any selection would be fine for the purposes of this lab). Also select Yes for Automatically accept the app end user license agreement:

Click OK and then click Add.

Assign the app to your Intune profile

Note

The following steps only work if you previously created a GROUP in Intune and assigned a profile to it. If you have not done that, please return to the main part of the lab and complete those steps before returning here.

In the Intune > Client Apps > Apps pane, select the Office package you already created to reveal its properties blade. Then click Assignments from the menu:

Select Add Group to open the Add group pane that is related to the app.

For our purposes, select Required from the Assignment type dropdown menu:

Available for enrolled devices means users install the app from the Company Portal app or Company Portal website.

Select Included Groups and assign the groups you previously created that will use this app:

In the Select groups pane, click the Select button.

In the Assign group pane, select OK.

In the Add group pane, select OK.

In the app Assignments pane, select Save.

At this point, you have completed steps to add Office to Intune.

For more information on adding Office apps to Intune, see Assign Office 365 apps to Windows 10 devices with Microsoft Intune.

If you installed both the win32 app (Notepad++) and Office (just Excel) per the instructions in this lab, your VM will show them in the apps list, although it could take several minutes to populate:

Glossary

OEMOriginal Equipment Manufacturer
CSVComma Separated Values
MPCMicrosoft Partner Center
CSPCloud Solution Provider
MSfBMicrosoft Store for Business
AADAzure Active Directory
4K HH4K Hardware Hash
CBRComputer Build Report
ECEnterprise Commerce (server)
DDSDevice Directory Service
OOBEOut of the Box Experience
VMVirtual Machine