Windows 11 and Office 2106

Deployment and Imaging

Framework

Version 1.1
Bruce Murphy
ayfun Karabayir
annis Mansolas
Design-in Strategists
Microsoft Corporation, Device Technical Sales
Microsoft Confidential – Shared Under NDA - Information Subject to Change
The information presented today is Microsoft Confidential Information, subject
to NDA between the parties and not for external discussion or distribution.

Any leak of this confidential information could seriously impact Microsoft’s

product plans, which would be a detriment to both of us.

Additionally, this content is for discussion purposes only and does not
Reminder About constitute an agreement between the parties; all proposed terms are subject
to separate agreement between the parties. All existing Microsoft programs
Confidentiality mentioned in this document are subject to the existing terms of such
programs.

Storage and destruction of Confidential Information disseminated as part of

the meeting should be handled in accordance with the applicable NDA.

Please make sure that you are viewing this presentation in a location where
confidentiality can be maintained.

No screenshots or other recording of the presentation is allowed.

Thank you.

Microsoft Confidential – Shared Under NDA - Information Subject to Change

Deployment and Imaging This is a simplified guide to deploying Windows 11 x64 and Office 2106 for
OEMs.
Framework Its purpose is to remove the complexity of command line deployment using
DISM and the Office C2R Deployment method
Introduction

The reference documentation for OEM Deployment of Windows 11 for

desktop editions can be found here
https://docs.microsoft.com/en-us/windows-hardware/manufacture/deskt
op/oem-deployment-of-windows-desktop-editions

Microsoft Confidential – Shared Under NDA Microsoft Confidential – Shared Under NDA - Information Subject to Change
The information contained in this document represents the current view of Microsoft Corporation and its Affiliates ("Microsoft") on the
issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be
interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented
after the date of publication.

MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE INFORMATION IN THIS DOCUMENT.

Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this
document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic,
mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in

Disclaimer
this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not
give you any license to these patents, trademarks, copyrights, or other intellectual property.

Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and
events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address,
logo, person, place or event is intended or should be inferred.

MICROSOFT DOES NOT MAKE ANY REPRESENTATION OR WARRANTY REGARDING SPECIFICATIONS IN THIS DOCUMENT OR ANY PRODUCT
OR ITEM DEVELOPED BASED ON THESE SPECIFICATIONS. MICROSOFT DISCLAIMS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING
BUT NOT LIMITED TO THE IMPLIED WARRANTIES OR MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND FREEDOM FROM
INFRINGEMENT. WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, MICROSOFT DOES NOT MAKE ANY WARRANTY OF ANY KIND
THAT ANY ITEM DEVELOPED BASED ON THESE SPECIFICATIONS, OR ANY PORTION OF A SPECIFICATION, WILL NOT INFRINGE ANY
COPYRIGHT, PATENT, TRADE SECRET OR OTHER INTELLECTUAL PROPERTY RIGHT OF ANY PERSON OR ENTITY IN ANY COUNTRY. IT IS
YOUR RESPONSIBILITY TO SEEK LICENSES FOR SUCH INTELLECTUAL PROPERTY RIGHTS WHERE APPROPRIATE. MICROSOFT SHALL NOT
BE LIABLE FOR ANY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF THESE SPECIFICATIONS, INCLUDING LIABILITY
FOR LOST PROFIT, BUSINESS INTERRUPTION, OR ANY OTHER DAMAGES WHATSOEVER. SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY OR CONSEQUENTIAL OR INCIDENTAL DAMAGES; THE ABOVE LIMITATION MAY NOT APPLY TO YOU.

© 2008 Microsoft Corporation. All rights reserved.

Microsoft, Windows, Windows 11, Windows 10, Windows 8.1, Windows 8, Windows 7 and Windows Vista are either registered trademarks
or trademarks of Microsoft Corporation in the United States or other countries or regions.

Thank you.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Microsoft Confidential – Shared Under NDA - Information Subject to Change

Timeline for Updating
• Before GA, we will ship tested scripts addressing OPK + ZDP + LCU
• Post GA, we will test and validate Refresh OPKs
• Update Unattend.xml to support China specific Device Config requirements, verify and validate (within 2 weeks)
• Update scripting to support ARM (with 1 month)

General Availability GA + 1 Month

Preinstalling Windows 11

Manufacture Windows 11 at OPK + ZDP + LCU Refresh OPK

GA
Available in September

Preinstalling Windows 11

China Device Config Refresh OPK

ARM Support Refresh OPK + ARM support

Microsoft Confidential – Shared Under NDA - Information Subject to Change

Information

Process Build your

Deploy to
reference PC
and

Overview
Automated image building framework custom image finalize

Leverage the Images Folder Structure and extract all

required files to this structure, build custom WinPE
(Network or USB), and leverage the automated image
building framework

Build your custom image with Windows updates, Office,

Custom Wallpaper on the Technician PC

Deploy to reference PC boot with WinPE, deploy, update

drivers, applications and finalize
Factory
Deployment Capture and
Capture and store your final image with WinPE store
and key
injection
Factory deployment and key injection boot with WinPE,
deploy your final image and complete key injection and
ship

Microsoft Confidential – Shared Under NDA - Information Subject to Change

Information

Preparing your Technician PC

Requirements
Windows 11 Pro, Windows 11 ADK, WinPE Addons, Microsoft
Media Tool, Images Scripts

Prerequisites
Windows 11
Deployment Download OPKs
Requirements
Download all OPKs to the Technician PC

Microsoft Confidential – Shared Under NDA - Information Subject to Change

Information

List of required Windows 11 OPKs

Technician PC 1 – Install the Windows ADK and WinPE Addons |
Due to the intensive CPU and disk
Download and install the Windows ADK | Microsoft Docs
operations using DISM it is
recommended to use a powerful 2 – Download all OPKs |
system with at least: Digital Operations Center (microsoftoem.com)*
X22-62133 Win 11 21H2 64ARM64 OPK ADK
X22-77379 Win 11 21H2 x64 English HomeProSLSN OPK -
Quad core CPU 2
8Gb RAM X22-62160 Win 11 21H2 x64 MultiLang OPK
128Gb SSD storage LangPackAllLIP LoF
X22-62137 Win 11 21H2 64ARM64 MultiLang OPK Inbox
Windows 11 Pro
Apps
1
Windows 11 Assessment and X22-62162 Win 11 21H2 x64 MultiLang OPK Feat on
Deployment Kit (ADK) and WinPE Demand RDX
Environment Addons X22-79194 Win 11 21H2 x64 MltLng OPK Inbox Apps (Win
2
All Windows 11 OPKs and Office Security AppX) JuneRTM
X22-79196 Win 11 21H2 64ARM64 MltLng OPK Windows
3
Images folders and scripts
Recovery Environment
Set sleep setting to never sleep X22-89545 Win 11 21H2 64/ARM64 MultiLang 9B LCU
For assistance with downloading OPK from the Software Order
You will also need one or two fast 16GB OPK Center
of the Microsoft Digital Order Center please refer to the Help &
or larger USB drives OR DHCP enabled Support
network 3- Extract Images.zip file to C:\ Section of DOC
Microsoft Confidential – Shared Under NDA - Information Subject to Change
Information

List of required Office 2106 OPKs

Technician PC 1 – Download all Office OPKs |
Due to the intensive CPU and disk
Digital Operations Center (microsoftoem.com)*
operations using DISM it is X22-61128 Office C2RScriptsConfigDeployment Tool for
recommended to use a powerful OEM OPK v2106
system with at least: X22-61138 Office 2106 English OPK

Quad core CPU

Optionally download the Office 2106 OPK for the
8Gb RAM languages you intend to preinstall. For a list of all Office
128Gb SSD storage 2106 languages please refer to Office OPK 2106 Part
Numbers.xlsx spreadsheet at
Windows 11 Pro
1
Windows 11 Assessment and https://devicepartner.microsoft.com/en-us/assets/detail/offi
Deployment Kit (ADK) and WinPE ce-opk-2106-part-numbers-xlsx
Environment Addons
2
All Windows 11 OPKs and Office
3
Images folders and scripts
Set sleep setting to never sleep
For assistance with downloading OPK from the Software Order Center
You will also need one or two fast 16GB of the Microsoft Digital Order Center please refer to the Help &
Support
or larger USB drives OR DHCP enabled Section of DOC
network
Microsoft Confidential – Shared Under NDA - Information Subject to Change
Deployment and Imaging Installing ADK
Preparing your projects folder
Framework Designing your image
Preparing a deployment WinPE USB drive
Preparing your
Technician PC
Workspace

Microsoft Confidential – Shared Under NDA - Information Subject to Change

Technician PC

Preparing the
Images folder
Open the embedded Images.zip
archive and extract its contents to the
root of the C:\ drive on your Technician
PC

Images.zip

Ver 1.1 09-29-2021

Microsoft Confidential – Shared Under NDA - Information Subject to Change

Technician PC

Installing ADK

Install the ADK using the X22-62133

OPK or online at
https://docs.microsoft.com/en-us/windo
ws-hardware/get-started/adk-install

Install the WinPE Addons

Ensure that at least the Deployment

Tools and User State Migration Tool
(USMT) boxes are selected

Microsoft Confidential – Shared Under NDA - Information Subject to Change

Technician PC

Preparing the
Images folder
Share the folder C:\Images for
network-based image building and
deployment

The folder must be shared as ‘Images’

Example
\\[computername]\images

Ensure network is set as

Private and Firewall rules are
updated accordingly to allow access
to the shared folder

Microsoft Confidential – Shared Under NDA - Information Subject to Change

Technician PC

Images\Images - This is where custom project images are stored

Images\ Mount - Used for mounting wim files for customization process.
Folder Functions
Must be empty before starting a new custom image – never store and files
here this folder should always be empty for DISM mount functions
Images\ Projects – Projects are stored here and inherit the file system and
files from Images\Windows folder when CreateProject.cmd is run
Images\ Scripts - contains scripts required for WinPE environment
including the WinPEMenu.cmd
Images\ Windows\Drivers - Drivers placed here will be injected into the
Windows and WinRE images
Images\ Windows\FOD – Retail Demo Experience and Language Features
on Demand packages
Images\ Windows\InboxApps - Inbox UWP Apps Updates and other UWP
apps – these are managed through the UpdateInboxApps.cmd script
Images\ Windows\Language - Language files for multi language
Windows images
Images\ Windows\Unattend - OEM customization files and other scripts
required for automated processing
Images\ Windows\Updates – Place any .msu update packages including
the ZDP and any other LCUs
Images\ Windows\WinRE\Languages – WinRE language files for multi
language Windows images, these are included in the ADK
Images\ Windows\WinRE\Updates - Any relevant WinRE updates
Images\ WinPE\Drivers - Drivers that are required for WinPE
Microsoft Confidential – Shared under NDA – Information subject to change
Technician PC

Drivers

Driver customization folders

Images\Windows\Drivers and Images\WinPE\Drivers

If you are preparing a system specific image you can place Windows drivers
in this folder that will be added to the image

If you are preparing a generic Windows image and do not want to include
system specific driver then you’ll have the opportunity to add drivers on the
Reference PC during image customization.

Only .inf based drivers can be added

Drivers than use an installer (Setup.exe) cannot be added using
DISM
Only install applicable driver architecture
IHVs may deliver the driver package that includes both x86 and
x64 binaries, only install the applicable architecture not both

Microsoft Confidential – Shared under NDA – Information subject to change

Technician PC

Adding Languages
Images\Windows\Languages
Languages

Copy the contents of the the LanguagesAndFeatures folder of the X22-

62160 Win 11 21H2 x64 MultiLang OPK LangPackAllLIP LoF OPK

Delete the Microsoft-Windows-Client-Language-Pack_x64_xx-yy.cab

main language files of the languages you do not want to add.

In the example only the German (de-de) and Greek (el-gr) main language
files are left.

You can delete the Microsoft-Windows-Client-Language-Pack_x64_en-us.cab

file too since it’s already in the image.

Do not remove the rest 3,000+ files as they are needed for the correct
configuration of satellite packages

If you are building an English only image, you can leave the folder empty

Microsoft Confidential – Shared under NDA – Information subject to change

Technician PC

Features on
Demand

FOD customization folders

Images\Windows\FOD

From the X22-62162 Win 11 21H2 x64 MultiLang OPK Feat on

Demand RDX OPK copy at least the Microsoft-Windows-RetailDemo-
OfflineContent-Content-
Package~31bf3856ad364e35~amd64~~.cab and the Microsoft-
Windows-RetailDemo-OfflineContent-Content-en-us-
Package~31bf3856ad364e35~amd64~~.cab files

Also copy the Microsoft-Windows-RetailDemo-OfflineContent-

Content-xx-yy-Package~31bf3856ad364e35~amd64~~.cab files of
all the languages you are adding.

In this example the packages for German (de-de) and English (en-us) have
also been added

Microsoft Confidential – Shared under NDA – Information subject to change

Technician PC

Language FOD customization folders

Features on Images\Windows\FOD
Demand
If you intend shipping Windows 11 with additional Languages Preinstalled
From the X22-62160 Win 11 21H2 x64 MultiLang OPK LangPackAllLIP
LoF OPK copy the following files for the languages that you are adding
(English not required):

Microsoft-Windows-LanguageFeatures-TextToSpeech-xx-yy-
Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-LanguageFeatures-Basic-xx-yy-
Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-LanguageFeatures-Handwriting-xx-yy-
Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-LanguageFeatures-OCR-xx-yy-
Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-LanguageFeatures-Speech-xx-yy-
Package~31bf3856ad364e35~amd64~~.cab

Note: Only some Languages have the Microsoft-Windows-

LanguageFeatures-Speech package
Some Languages require the optional fonts package e.g. Japanese;
Microsoft-Windows-LanguageFeatures-Fonts-Jpan-
Package~31bf3856ad364e35~amd64~~.cab
Microsoft Confidential – Shared under NDA – Information subject to change
Technician PC

InboxApps
Images\Windows\InboxApps
Inbox Apps

Copy all the contents of the amd64fre folder of the X22-62137 Win 11
21H2 64ARM64 MultiLang OPK Inbox Apps OPK

Copy the contents (4 files) of the x64\

Microsoft.SecHealthUI_8wekyb3d8bbwe folder of the X22-79194 Win
11 21H2 x64 MltLng OPK Inbox Apps (Win Security AppX) JuneRTM\
SW ELCTRNC Win 11 21H2 x64 MltLng InboxAppsOEM
(WinSecurityAppX) JuneRTM\Layer\X22-79198.zip archive -
overwriting the two existing files:
Microsoft.SecHealthUI_8wekyb3d8bbwe.appx
Microsoft.SecHealthUI_8wekyb3d8bbwe.xml

Note: 4 files to be copied for WinSecurtyAppx;

Microsoft.SecHealthUI_8wekyb3d8bbwe.appx
Microsoft.SecHealthUI_8wekyb3d8bbwe.xml
Microsoft.UI.Xaml.appx
Microsoft.VCLibs.appx

Microsoft Confidential – Shared under NDA – Information subject to change

Technician PC
Adding Office
Images\Windows\Office

Office Copy the contents of the 2106ODT folder of the X22-61128 Office
C2RScriptsConfigDeployment Tool for OEM OPK v2106 in the
Windows\Office folder.

Copy the contents of the X22-61138 Office 2106 English OPK in the
Images\Windows\Office folder.

Optionally copy the contents of additional Office 2106 OPKs of the Office
languages that you intend to preinstall

Notes:
The top folder of each Office 2106 OPK is Office. This is the folder that must
be copied in the Windows\Office folder so you’ll end up with an Images\
Windows\Office\Office\Data\... folder structure.

Office 2106 OPKs have different language resource files but the base files
are the same. If you are copying multiple Office OPKs then you’ll get a ‘file-
overwrite’ prompt. It’s OK to skip overwriting files to speed up the copying
process.
The Office languages you add will not all be preinstalled by default. You will
be prompted to select which Office languages will be preinstalled later in
the project creation process.
MicrosoftIf you don’t
Confidential want
– Shared under NDA –to add subject
Information multiple
to change languages in a multilanguage Windows
Technician PC

Unattend

Unattend Folder Contents

Images\Windows\Unattend

If you are using a custom desktop background image (wallpaper) then

please rename it to wallpaper.jpg* and copy it in this folder choosing to
overwrite the existing file

If you don’t plan to use a custom wallpaper, then please delete the existing
wallpaper.jpg file

The folder contains the file Unattend.xml which is used to add OEM
information to the Windows image. This file will be customized with the
information you will be asked to provide during CreateImage.cmd process
in the image creation process.

All other files and scripts are required for successful image creation.

Note: If you are using a custom desktop background image, then you must ensure you own the copyright
of that image. For Windows 11 we additionally require you to provide images which follow the composition
guidance in the Windows Engineering Guide
Microsoft Confidential – Shared under NDA – Information subject to change
Technician PC

Updates

Windows Updates
Images\Windows\Updates

Place all .msu update packages here and DISM will programmatically
update the Install.wim file during the CreateImage.cmd process

X22-77379 Win 11 21H2 x64 English HomeProSLSN OPK -2 Contains the

ZDP Windows10.0-KB5005027-x64.msu which must be placed in the
Windows\Update folder

X22-89545 Win 11 21H2 64/ARM64 MultiLang 9B LCU OPK – Contains

the final Release LCU Windows10.0-KB5005635-x64.msu which must be
placed in the Windows\Update

Microsoft Confidential – Shared under NDA – Information subject to change

Technician PC

WinRE WinRE - Updates

Images\Windows\WinRE\Updates

Place all applicable .msu update packages here and DISM will
programmatically update the WinRE.wim file during the CreateImage.cmd
process

X22-77379 Win 11 21H2 x64 English HomeProSLSN OPK -2 Contains

the ZDP Windows10.0-KB5005027-x64.msu which must be placed in
the Windows\WinRE\Updates folder

X22-79196 Win 11 21H2 64ARM64 MltLng OPK Windows Recovery

Environment contains fixes required for WinRE, copy Windows10.0-
KB5005662-x64.msu from the X22-79197.zip here

X22-89545 Win 11 21H2 64/ARM64 MultiLang 9B LCU OPK – Contains

the final Release LCU Windows10.0-KB5005635-x64.msu which must be
placed in the Windows\WinRE\Update folder

Microsoft Confidential – Shared under NDA – Information subject to change

Technical PC
WinRE - Languages
Images\Windows\WinRE\Languages

WinRE Place all WinPE language packs here which you want to be applied to WinRE
C:\Program Files (x86)\Windows Kits\10\Assessment and
Deployment Kit\Windows Preinstallation Environment\amd64\
WinPE_Ocs\xx-yy

You will require the following files for each language; if adding multiple
languages you may preserve the folder structure from C:\Program Files
(x86)\Windows Kits\10\Assessment and Deployment Kit\Windows
Preinstallation Environment\amd64\WinPE_OCs
lp.cab
WinPE-Rejuv_xx-yy.cab
WinPE-EnhancedStorage_xx-yy.cab
WinPE-Scripting_xx-yy.cab
WinPE-SecureStartup_xx-yy.cab
WinPE-SRT_xx-yy.cab
WinPE-WDS-Tools_xx-yy.cab
WinPE-WMI_xx-yy.cab
WinPE-StorageWMI_xx-yy.cab
WinPE-HTA_xx-yy.cab

You must match the WinRE languages with the preinstalled Windows
languages
Microsoft Confidential – Shared under NDA – Information subject to change
Deployment and Imaging Creating a custom WinPE
Start a new project
Framework Create image

Creating a New
Image

Microsoft Confidential – Shared Under NDA - Information Subject to Change

Technician PC

All the processes below require the following method of execution

Launch the Deployment and Imaging Tools Environment shortcut with

Run as Administrator option selected

Change to the Images directory

CD C:\Images

Microsoft Confidential – Shared under NDA – Information subject to change

Technician PC

Creating a custom WinPE

The function of this USB is to boot the reference

PC with WinPE and store Images or create a
network mapping back to the Technician PC

Run the CreateWinPE.cmd from the C:\

Images with one of the following command line
switches

CreateWinPE.cmd /dualpart – Dual

partitioned bootable WinPE with NTFS partition
for Images to be stored

CreateWinPE.cmd /network – Single

partitioned bootable WinPE with network
mapping capabilities
You will need to supply the Computer Name, Animations are for display of process and not time related

User Account name and the Password for that

account
Microsoft Confidential – Shared under NDA – Information subject to change
Technician PC

Starting a New Project

Mount the X22-77379 Win 11 21H2 x64 English
HomeProSLSN OPK -2 OPK Windows 11 image by
double clicking on the ISO file and noting the DVD
drive letter it is assigned, e.g. D:\*
Animations are for display of process and not time related
*Alternatively, copy the \Sources\install.wim file to the C:\Images folder for quick
access

Navigate to the C:\Images folder and type:

CreateProject.cmd [projectname] D:\Sources\

install.wim

Where [projectname] is a name for your project, e.g.

“testproj”, and Drive\Sources\install.wim is the
path to the install.wim file on the mounted ISO file or
your hard disk.

All files and folders from Images\Windows will be

copied to Images\Projects\[projectname]

The Images\Projects\[projectname] folder is now

presented for verification, additions and removals
Microsoft Confidential – Shared under NDA –of
Information subject to change
Technician PC

Create New Image

Type CreateImage.cmd [projectname] to start the
image building process

You will be prompted to select the Windows 11

Edition you wish to create. The default OA 3.0
Manufacturing Key will be automatically applied to the
image and the unattend.xml updated

The image will be mounted, and your Drivers,

Languages, FOD and Updates will be applied
programmatically

All drivers in your Images\Projects\[projectname]\

Drivers folder will be applied to both Windows and
WinRE

The script pauses at the end of this process for your

review of applied packages and drivers Animations are for display of process and not time related

Microsoft Confidential – Shared under NDA – Information subject to change

Technician PC

Create New Image

OEM Customizations

During the next step of the process you will need to

provide additional details to set;
csup.txt date (required for Device Configuration
discount) which is placed in the Windows folder of the
mounted image. Ensure you follow the format MM-DD-
YYYY

Select the default language of the image (this will

also be applied as the default language for WinRE)
Please note that a corresponding Language Pack must
be have been included in your \Images\Windows\
Languages folder
Default = *en-US

Type the name of your time zone

Default = *Pacific Standard Time

Note: You can find a list of language/region tags at

https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/available-lang
uage-packs-for-windows
and Time Zones at Microsoft Confidential – Shared under NDA – Information subject to change
Technician PC

Create New Image

Office Language Selection

If you have included Office in your image you will

prompted to select the Office languages, you want to
include in your image from the file which is presented
in Notepad. Completely remove the lines with
languages you do not want to include, select File and
Save and close Notepad when done.

Image customization is now complete, and the custom

image is placed in the folder Images\Images\
[projectname].wim

Copy the [projectname].wim file to your USB or

leave in place for Network deployment method

Note: You must have added these language OPKs during the Workspace preparation
phase.

Microsoft Confidential – Shared under NDA – Information subject to change

Technician PC

Create New Image

OEM Customizations

Select whether you want to enable S Mode

Type your OEM name and support URL - this is

mandatory and will appear in the Windows inbox Get
Help app

Note: S Mode selection is available only if you are preparing a Windows 11 Home or
Windows 11 N Home image

Microsoft Confidential – Shared under NDA – Information subject to change

Deployment and Imaging Copy image to the USB drive (USB Deployment Method)
Boot the reference PC and apply the image
Framework Customize the image
Capture the final image
Applying the Image
to the Reference PC

Microsoft Confidential – Shared Under NDA - Information Subject to Change

Reference PC

Applying the image USB Deployment Method

Copy the C:\Images\Images and C:\

Images\Scripts folders to the NTFS USB
drive/partition

USB and Network Method

Configure the BIOS of the reference PC

appropriately and boot from the WinPE USB
drive

Select option [1] Apply .wim file

Available wim files are presented select the
image you want to apply (do not press Enter)
Select Y for Recovery Partition and Y to format the disk
Select N for Compact OS option and N for Extended
Attributes

Animations are for display of process and not Select option [2] Apply Recovery
time related
Select Y as disk already has Recovery partition
When finished select option [5] Exit and
reboot the reference PC into Audit mode.

Microsoft Confidential – Shared under NDA – Information subject to change

Reference PC

Image customization The reference PC will start in Windows 11 in

Audit mode and an automated process will
start in a paused state, SYSPREP will be
closed.

When ready, press any key in the script

window to start Office configuration and
installation.

Animations are for display of process and not time related

Microsoft Confidential – Shared under NDA – Information subject to change

Reference PC

Image customization When Office installation is finished click

‘Close’ to close the Office window

Now is the time to add missing system

drivers or applications

When ready, click any key in the paused

script window to configure recovery, finalize
the image and shut down the PC

Note: The script must not be interrupted until the PC is shut down.

Microsoft Confidential – Shared under NDA – Information subject to change

Reference PC

Image capture Boot the reference PC from the WinPE USB

drive – Do not allow Windows to boot

USB Deployment Method

Ensure the USB with the Images and Scripts
folder is also in the PC

Select option [3] Capture .wim file

The Windows image will be captured in the

USB drive \Images folder using filename
(network method will leverage the network
share)

[projectname]_Final.wim

When finished select option [5] Exit and

Reboot

Animations are for display of process and not time related

Microsoft Confidential – Shared under NDA – Information subject to change

Reference PC

Final Image Deployment Boot the reference PC from the WinPE USB
(Factory Floor)
USB Deployment Method
Ensure the USB with the Images and Scripts
folder is also in the PC

Select option [1] Apply .wim file from the

menu and select the final image
[projectname]_Final.wim

When finished select option [5] Exit and

Reboot to reboot the destination PC to
Audit mode

After Quality checking and OA 3.0 DPK

injection use the Sysprep pane to seal the
PC to OOBE mode, shutdown and ship.

For images shipping with S Mode enabled,

please leverage the file placed on the
desktop ‘Sysprep S Mode.cmd’ to run
final registry entries and it will execute
Sysprep /OOBE /Shutdown. Do not
execute the Sysprep application directly.
Microsoft Confidential – Shared under NDA – Information subject to change
Thank you