Edytuj

Universal image

  • Artykuł

Microsoft Managed Desktop has created an image containing Windows Pro and Microsoft 365 Apps for Enterprise that you can use with Microsoft Managed Desktop.

However, it's best to use images appropriate to Microsoft Managed Desktop provided by the manufacturer whenever possible, even if that means an older Windows version must be updated once the user signs in. Using the Microsoft Managed Desktop Universal image should be the final option.

About the universal image:

  • We update the image with the latest Windows monthly quality updates every 30-60 days, and Microsoft 365 Apps for Enterprise updates at least twice a year.
  • The image contains a recovery provisioning package to ensure Microsoft 365 Apps for Enterprise is restored following Windows recovery scenarios.
  • You can deploy the image with USB drives.
  • You can provide model specific drivers which will be deployed via a scripted process to insert drivers for Windows, WinRE, and WinPE.
  • You can modify the included scripts and folders with other customizations, such as adding specific cumulative updates, file copy code, or performing other checks.
  • Drivers and quality updates are added to Windows during deployment from the USB drive.

Note

It's your responsibility to add all necessary drivers, perform all testing, and ensure there are no issues with the final deployed image. We provide the universal image "as-is" but will provide technical guidance and answer questions. Contact MMDImage@microsoft.com.

Submit requests for the universal image by creating a change request in the admin center. You'll receive instructions on how to download the universal image.

Tip

To enable rapid testing and validation of the Microsoft Managed Desktop platform in your Hyper-V environment, you'll need a VHDX file. To obtain the VHDX file, submit a request.

Language support

The following are the images we support as part of the download script:

Image type Region Language support
Regional universal image EMEA Supports regions and languages in Europe and the Middle East:
  • Arabic
  • Bulgarian  
  • Croatian
  • Czech
  • Danish
  • Dutch
  • English (US, GB, AU, IN)
  • Estonian
  • Finnish
  • French (France)
  • German
  • Greek
  • Hebrew
  • Hungarian
  • Italian
  • Latvian
  • Lithuanian
  • Norwegian (Bokmål)
  • Polish
  • Portuguese (Brazil)
  • Romanian
  • Russian
  • Serbian (Latin)
  • Slovak
  • Slovenian
  • Spanish (Spain)
  • Swedish
  • Turkish
  • Ukrainian
Regional universal image APAC Supports regions and languages for Asia Pacific area:
  • English (US, GB)
  • Japanese
  • Chinese (PRC)
  • Chinese (Taiwan)
  • Korean
  • Thai
  • Vietnamese (LiP)
  • Indonesian
Regional universal image NA Supports regions and languages for North America:
  • English (US, GB)
  • Spanish (Mexico)
  • French (Canada)
Standard universal image — Supports English (US, GB)
EN-US universal Image — Supports English (US)

Multi-model driver support

Note

This feature is available in the universal image by default as of May 31, 2022. Any universal images downloaded prior to May 31, 2022 doesn't include multi-model driver support.

This feature allows customers to stage different model drivers in separate folders. Model-specific drivers are injected at the time of image deployment. The feature depends on:

  • The Sku_Folder.json mapping file which contains the system SKU (displayed by SMBIOS System SKU) and driver folder names.
  • The corresponding driver folder (created by you) where drivers (also provided by you) can be found for that model.

The feature supports driver injection to Windows, WinRE, and WinPE.

Prerequisites

Prerequisites to deploy multi-model driver support are as follows:

  • System SKU
  • A workstation to author content on the USB
  • Model-specific drivers

System SKU

The System SKU is a variable stored in the System Management BIOS (SMBIOS) in the UEFI layer of manufactured devices. You can view a device's System SKU by referencing the system information file (also referred to as msinfo). To view the contents of the system information file, run the msinfo32.exe on the device you're planning to deploy to. For more information about msinfo32.exe, see Description of the Microsoft System Information (Ms32info.exe) tool.

The msinfo32 file provides the following information, including the System SKU:

Item Value
OS Name Microsoft Windows 10 Enterprise
Version 10.0.19044 Build 19044
Other OS Description Not available
OS Manufacturer Microsoft Corporation
System Name
System Manufacturer Microsoft Corporation
System Model Surface Pro 4
System Type x-64-based PC
System SKU Surface_Pro_4
Processor Intel(R) Core(TM) i7-6650U CPU @ 2.20GHz, 2208 Mhz...
BIOS Version/Date Microsoft Corporation 109.2748.78, Not Available
SMBIOS Version 3.3
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer Microsoft Corporation

Workstation

Run Windows 10 or higher with administrative rights. You'll use this to edit the JSON file, create folders on the USB, and copy over drivers to the USB.

Note

You must use a local administrator account. Elevating to admin or using the ‘Run as admin’ option on a standard user device will fail during the scripting process when downloading the USB files.

Model specific drivers

OEMs have allowed customers to download all the drivers needed for their models. Please work with your OEM to locate the drivers for your specific device. There will be two types of drivers you should plan to stage on the USB:

Driver Description
Windows drivers Typical Windows drivers include (but are not limited to):
  • Chipset
  • Graphics
  • Network
  • Audio
  • Keyboard/Trackpad
  • Storage Controller
WinPE/WinRE drivers Typical WinPE/WinRE drivers (critical drivers only):
  • Keyboard/Trackpad
  • Storage Controller
  • Network
Where to find OEM Drivers
OEM Link
Dell Drivers & Downloads
HP Official HP® Drivers and Software Download
Lenovo Lenovo Drivers and Updates
Surface Download drivers and firmware for Surface

Add system SKU specific drivers

Use the following steps to add system SKU specific drivers.

Step 1: Prepare the USB key

Follow this process to edit the JSON file and create driver folders once you have downloaded Universal Image to a USB key.

There are two partitions on the USB as created by the Microsoft Managed Desktop script:

  • WinPE (E:)
  • Images (F:)

The JSON file (SKU_Folder.json) is located on the Images partition in the <USB Image Partition>:\Images\Drivers folder. For example, F:\Images\Drivers where "F:" is the USB Images partition.

Step 2: Edit the JSON file

  1. Locate the JSON file in the Images\Drivers folder and add entries to map the driver folders to the correct device model (System SKU).
  2. Insert an entry for "SystemSKU": “name of System SKU”. The name should exactly match the System SKU found in the prerequisite section.
  3. Insert an entry for the “Folder”: “name of folder containing drivers”. The name should exactly match the driver folder name you created on the USB key with the drivers. For more information, see Create driver folders. The path for drivers is based on <USB Images partition>:\Images\Drivers. You don't need a full path, just the name of the folder within that location.
  4. You don't need to include _OS, _WinPE, _WinRE in the folder name in the JSON file. We'll automatically look for your folder name to contain those extensions.

The following is an example of a JSON file filled out for several HP and Surface devices. The HP device is the same model, but for two different regions.

In this example, we know the drivers are the same for the HP device (even though it's in two different regions). Therefore, we have one driver folder to be applied for two regions (America and UK – HP has SKU MODELS where region is after the #). Similar logic, using multiple SystemSku entries mapping to the same Folder name, can be used anytime you want a folder to be applied to multiple models.

[
    {
        "SystemSKU": "Surface_Pro_6_1976_Commercial",
        "Folder": "Pro6"
    },
    {
        "SystemSKU": "Surface_Laptop_4_1950:1951",
        "Folder": "SL4_Intel"
    },
    {
        "SystemSKU": "46Z55UP#ABA",
        "Folder": "HP Elitebook 830 G5"
    },
    {
        "SystemSKU": "46Z55UP#ABU",
        "Folder": "HP Elitebook 830 G5"
    }
]

In each example above, the SystemSKU is exactly what is listed for ‘System SKU’ in the msinfo32 file of each device model.

Step 3: Create driver folders

You choose the name of each folder that you're placing the drivers into on the USB key.

All driver folders you create will be on the Images partition in the <USB Image Partition>:\Images\Drivers folder.

We support three folder name extensions to determine specific driver locations for a SystemSKU.

Folder name extension Description
_OS Drivers in this folder will only be applied to full Windows (not WinPE or WinRE).
_WinRE Drivers in this folder will only be applied to WinRE.
_WinPE Drivers in this folder will be online injected into the running instance of WinPE.

Note

Some drivers are built in such a way that they don't support online injection without performing a reboot. For those cases, we recommend you inject the driver into WinPE offline (<USB WinPE Partition>\Sources\Boot.wim). Utilize the first option outlined in Method for making drivers available to WinPE.

If you want to create driver folders applicable to ALL models, we support the following folder locations:

  • OS
  • WinRE
  • WinPE

Note

If you place drivers in these folders, we'll load those drivers in addition to any SKU model-specific driver folders that are applicable.

The following is an example of SKU-specific driver folders for HP and SurfacePro7, and generic driver folders in F:\Images\Drivers.

SKU specific driver folder Folder names
HP HP-specific driver folders include:
  • HP_Driver_OS
  • HP_Driver_WinPE
  • HP_Driver_WinRe
SurfacePro7 SurfacePro7-specific driver folders include:
  • SurfacePro7_OS
  • SurfacePro7_WinPE
  • SurfacePro7_WinRe
Generic driver folders Generic driver folders include:
  • OS
  • WinPE
  • WinRe

For the previous example, the JSON file contains:

[
    {
        "SystemSKU": "Surface_Pro_7_1866",
        "Folder": "SurfacePro7"
    },
    {
        "SystemSKU": "46Z55UP#ABA",
        "Folder": "HP_Driver"
    }
]

Based on this example, this is the behavior of the driver injection on a Surface Pro 7 device where the SKU model is reported as Surface_Pro_7_1866:

  • Drivers in the <USB Images partition>:\Images\Drivers\SurfacePro7_OS folder will have all drivers in it applied to the device as well as any drivers in the <USB Images partition>:\Images\Drivers\OS folder.
  • Drivers in the SurfacePro7_WinRE folder and drivers in the WinRE folder will be applied to the Winre.wim file during deployment.
  • Drivers in the SurfacePro7_WinPE folder and drivers in the WinPE folder will be loaded online once WinPE has started from the USB key.
  • All drivers in other folders will NOT be loaded for the Surface Pro 7. If any applicable folders are blank, those folders are ignored.

Step 4: Deploy the image

Start up your device from the USB key. Example instructions of starting a Surface device from a USB key can be found here.

FAQ

Question Answer
Where can I get the universal image? Please submit a request via the admin center to the Microsoft Managed Desktop team.
Can I run the download script on a Microsoft Managed Desktop device? No. We utilize a service to download and install the universal image from the cloud onto a USB key. This service requires local administrative rights. Devices managed by Microsoft Managed Desktop do not have sufficient permissions (even when elevating) to enable the required service. Please use another system with local admin rights.
My drivers for WinPE are not working, what could be wrong? Some drivers injected in WinPE may require a restart. In which case, they must be inserted by injecting them into the boot.wim file offline using Deployment Image Servicing and Management (DISM) commands. For more information, see Add and Remove Drivers to an Offline Windows Image. 
What is the size of WinPE partition? The default WinPE partition created on the USB is 4GB in size. Adding WinPE drivers should be limited to only those drivers needed in WinPE to reduce the risk of exceeding the 4GB size limitation.
Can I use my model specific drivers on other models? It's recommended to only use drivers that OEMs have targeted for specific models. Utilizing drivers across multiple models (applying model specific drivers to different models) can result in errors within Windows.
How much hard drive space do I need when downloading the universal image? In general, please ensure that your device has 30 GB of open space when downloading the universal image.
How can I identify the Microsoft Managed Desktop image version in devices already deployed? All the universal images released after March-2021 onwards set the following registry keys to identify the image, build version, UI version, and region.
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Managed365/Original Image Build Version
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Managed365/UI Version
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Managed365/Region

Images released before March-2021 should have a file ‘VersionTracking’ with version details. That file can be found in the directory: Windows\System32\ImageVersionTracking.
Can I run the PowerShell installation script using “Run as different user” that has admin rights? No. The scripts need local administrator rights. It's recommended to run the PowerShell installation script as a local administrator account on the device.
Will 32GB USB drives be sufficient for the universal image? It's recommended to use a 64GB USB for the universal image, especially, for our larger images that contain many languages such as the regional universal image for EMEA.
Why am I getting a “Can’t validate argument” message when running the PowerShell installation script? This error usually occurs because the account running the script has insufficient permissions. We highly recommend you use a local administrator account. Do not run this script as “Run as a different user”.