1. Microsoft Windows Nt Server 6.3

Page 2 of 24 - NT 6.x fast installer: install win7 directly to usb external drive - posted in Windows 7: Hi jaclaz,just an addition, I do not know in details but I can say WimcaptEx.exe can be used with only 'wimgapi.dll 32bit' on hostosx64 (post 130). 20+ years ago when I joined Microsoft I was handed a diskette (maybe it was two), and was told “Here is SQL Server. Go install it”. So I proceeded to install SQL Server 4.20 on my Windows NT 3.1 desktop machine (I won’t tell you the hardware details. OEM Deployment of Windows 10 for desktop editions.; 62 minutes to read +3; In this article. Getting ready to build and test Windows 10 desktop PCs? This lab shows you the steps to make and deploy Windows images. We'll show you how to use the tools and commands to setup an end-to-end deployment.

OEM Deployment of Windows 10 for desktop editions. 62 minutes to read.In this articleGetting ready to build and test Windows 10 desktop PCs? This lab shows you the steps to make and deploy Windows images. We'll show you how to use the tools and commands to setup an end-to-end deployment. The commands can be scripted, helping you quickly customize new images for specific markets to meet your customers' needs.We'll walk you through the process of building a customized Windows deployment. Here's what we'll cover:We'll start by preparing your environment, then we'll cover the steps for:.

Preparing and mounting a WinPE image. Adding packages. Adding drivers. Creating WinPE mediaNext we'll move onto customizing your Windows image. We'll start with to a mounted Windows image, where we'll cover:.

Adding Drivers. Adding Languages. Adding Updates. Reinstalling inbox apps. Preinstalling Microsoft Office.

Adding tiles to the Start Layout. Setup OOBE to display a custom EULA. Configuring and using answer files to customize Windows SetupWe'll finish customizing the Windows image by and finish making changes, including:. Making changes in Audit mode. Preparing Push Button ResetFinally, we'll.

Finalizing the imageLet's get started! Prepare your lab environment. NoteIf you haven't gathered the files you need to go through this lab, see.At this point, you should have your tools ready to go. At this point, you should have:A USB drive, formatted with two partitions, with the following on the NTFS, partition ( O:):. The extracted folder structure and files from USB-BA technician PC that has:. A folder called C:templab with the following media downloaded:. Windows installation media.

The most recent version of the Microsoft Office OPK. Windows Features on Demand ISOs. Windows Language pack ISO.

OPK App Update or Inbox Apps ISO. Windows ADK installer. WinPE ADK Add-on (if using the ADK for Windows 10 version 1809, or later).

Drivers for your image (if needed)Let's setup your lab. Install the Windows ADK for Windows 10The Windows ADK is a collection of tools that enables you to manage and deploy custom Windows installations to new computers. ImportantUse the matching version of ADK for the images being customized. For example, if you're working with Windows 10, version 1809, use the ADK for Windows 10, version 1809.On your technician PC:.If you have a previous version of the Windows Assessment and Deployment Kit (ADK), uninstall it.Download the version of the that matches the version of Windows that you’re installing.Run the ADK installer to install the ADK with the following options. If you're using the ADK for Windows 10.

Version 1809, WinPE isn't part of the ADK installer and is a separate add-on package that you have to install after you install the ADK:. Deployment Tools. User State Migration Tool (USMT).

Windows Preinstallation Environment (Windows PE).When installation finishes, close the installer window.Create a bootable Windows PE (WinPE) partitionWinPE is a small, command-line based operating system that you can use to capture, update, and optimize Windows images. In this section, we'll show you how to prepare a basic WinPE image on a bootable USB flash drive and try it out. Prepare WinPE files.On your technician PC, start the Deployment and Imaging Tools Environment as an administrator:. Click Start, type Deployment and Imaging Tools Environment. Right-click Deployment and Imaging Tools Environment and select Run as administrator.Use copype to create a working directory that has the base WinPE files: copype amd64 C:winpeamd64.

TipIf this doesn't work, make sure you're in the Deployment and Imaging Tools Environment, and not the standard command prompt.Customize WinPEYou can customize a WinPE image (boot.wim) in several ways by adding files and components to a mounted WinPE image.Here are some examples of how you can modify your WinPE image:.Add an optional component. Ship in the ADK. These are packages that you can add to your WinPE image to add functionality to WinPE.Add a graphics or network driver. (WinPE includes generic video and network drivers, but in some cases, additional drivers are needed to show the screen or connect to the network.). To learn more, see.Set the power scheme to high-performance. Speeds deployment.

Note, our sample deployment scripts already set this scheme automatically. See.Optimize WinPE: Recommended for devices with limited RAM and storage (for example, 1GB RAM/16GB storage). After you add drivers or other customizations to Windows PE, see to help reduce the boot time.When you add packages to WinPE, performance will be reduced and boot time will increase. Only add packages that you need to complete a successful deployment. Mount your WinPE imageTo customize a Windows image, you have to mount it before you can work with it. This is true for WinPE images as well.

Mounting an image extracts the contents of an image file to a location where it can be viewed and modified. Throughout this lab we'll use DISM to mount and modify images. DISM comes with Windows, but we'll be using the version that is installed by the ADK, which we'll access through the Deployment and imaging tools environment.Boot.wim is the WinPE image file. You can find it in the files that you copies with copype.cmd.Mount the image:.

From the Deployment and imaging tools environment, mount the image:Dism /mount-image /imagefile:c:WinPEamd64mediasourcesboot.wim /index:1 /mountdir:c:winpeamd64mountAdd packages, optional components, dependencies, and language packs to WinPE (optional)Use Dism /Add-Package to add packages to your mounted WinPE image. The ADK has you can add for additional WinPE functionality. Some packages have dependencies and require other packages to be installed. For these packages, you'll have to install the dependencies before you add the a package. For example, if you want to use Powershell in WinPE, you have to install the NetFx as well as the language-specific OCs.

You can find OC CABs in C:Program Files (x86)Windows Kits10Assessment and Deployment KitWindows Preinstallation EnvironmentWinPEOCs. NoteThis method requires.inf-based drivers. Get.inf-based drivers from your hardware vendor. Dism /image:C:winpeamd64mount /Add-Driver /driver:'C:Out-of-Box Driversmydriver.inf'Where C:Out-of-Box Driversmydriver.inf is the path of the driver you're adding.To install all of the drivers in a folder and all its subfolders use the /recurse option.

Microsoft Windows Nt Server 6.3

For example: Dism /Image:C:Winpeamd64mount /Add-Driver /Driver:c:drivers /recurseWhere C:drivers is the drivers folder that you're adding. Set the power scheme to high-performanceSetting WinPE to use high-performance mode will speed deployment. NoteOn some devices, you might need to go into the boot menus to choose the USB drive. If you're given a choice between booting in UEFI mode or BIOS mode, choose UEFI mode. To learn more, see.If the device does not boot from the USB drive, see the troubleshooting tips in.WinPE starts at a command line, and runs wpeinit to set up the system. This can take a few minutes.Leave this PC booted to Windows PE for now. You can remove the bootable USB drive.

Customize your Windows imageNow that you have your WinPE image customized for your deployment, we'll get into how to get your Windows image ready for deployment. The process is similar to how we changed our WinPE image, but Windows has many additional customization options.You can make either offline or online or online customizations to a Windows image.

Offline customizations are done to the windows image (install.wim) from either the Technician PC or from the destination PC while booted into WinPE. In most scenarios, offline customizations are customizations you perform from the Technician PC.

Online customizations are done on the Reference PC after it’s been booted into audit mode.The table below shows which customizations can be made online and offline. In a manufacturing environment, it’s recommended to do as many customizations as possible offline.

ScenarioOfflineOnlineAdding device driversXXAdding Microsoft Store appsXXAdding Desktop (win32) apps-XAdding language packsXXRemove default language packX-Adding features-on-demandXXAdding the latest cumulative updateXXImage optimizationXXMicrosoft Store apps duplicate files cleanupX-Microsoft OfficeXXPrepare and mount a Windows imageIn this section we'll cover how to mount Windows images on your technician PC. Mounting a Windows image is the same process that we used to mount the WinPE image earlier. When we mount our Windows image (install.wim), we'll be able to access a second image, WinRe.wim, which is the image that supports recovery scenarios.

Updating install.wim and WinRE.wim at the same time helps you keep the two images in sync, which ensures that recovery goes as expected.Before we continue, make sure that you've created your USB-B drive. We showed you how to set it up in the section. Backup your Windows image fileBefore working on your Windows image, you want to make sure you have a backup copy in case something goes wrong. Make a copy of the original image:First copy the install.wim from your Windows installation media to USB-B. Install.wim includes both Home and Professional images. We'll export the Home image from install.wim, and then work with that image during this lab.Insert USB-B into your technician computer.Mount the Windows 10 Home.img from the Win Home 10 32-BIT/X64 English OPK.From the mounted image, copy D:sourcesinstall.wim to C:templabimages.

(Where D: is the drive letter of the mounted image.).From the Start menu, open Windows Kits, open the Deployment and Imaging Tools Environment as administrator.Make a copy of your image in case something goes wrong. TipIf winre.wim cannot be seen under the specified directory, use the following command to set the file visible: attrib -h -a -s C:mountwindowsWindowsSystem32Recoverywinre.wimTroubleshoot: If the mounting operation fails, make sure you're using DISM from the Deployment and Imaging Tools Environment. Do not mount images to protected folders, such as the UserDocuments folder. If DISM processes are interrupted, consider temporarily disconnecting from the network and disabling virus protection.Offline customizationsWith your images mounted, you can start customizing. We'll show you how to make offline customizations to your Windows image. Offline customizations are changes that you can make to a mounted image without having to boot into the Windows installation.

First, we'll walk through adding (and removing) languages from your Windows image. About LanguagesIn this section, we'll show you how to add languages to a Windows installation. If you want to add a language, you'll need a language pack from the Language Pack ISO, as well as an internet connection or access to the Feature on Demand ISO.Notes. Add languages before major updates. Major updates include hotfixes, general distribution releases, or service packs.

If you add a language later, you'll need to reinstall the updates. Add major updates before apps. These apps include universal Windows apps and desktop applications.

If you add an update later, you'll need to reinstall the apps. We'll show you how to add these later in Lab 6: Add universal Windows apps. Add your languages to your recovery image, too: Many common languages can be added to your recovery image. We'll show you how to add these later in Lab 12: Update the recovery image.Always use language packs and Features-On-Demand (FOD) packages that match the language and platform of the Windows image.Features on demand (FODs) are Windows feature packages that can be added at any time. When a user needs a new feature, they can request the feature package from Windows Update. OEMs can preinstall these features to enable them on their devices out of the box.Common features include language resources like handwriting recognition.

Some of these features are required to enable full Cortana functionality.The following table shows the types of language packages and components available for Windows 10: ComponentSample file nameDependenciesDescriptionLanguage packMicrosoft-Windows-Client-Language-Packx64de-de.cabNoneUI text, including basic Cortana capabilities.Language interface packLanguageExperiencePack.am-et.neutral.appxRequires a specific fully-localized or partially-localized language pack. Example: ca-ES requires es-ES.UI text, including basic Cortana capabilities.

To learn more, see Available Language Packs for Windows.BasicMicrosoft-Windows-LanguageFeatures-Basic-de-de-PackageNoneSpell checking, text prediction, word breaking, and hyphenation if available for the language.You must add this component before adding any of the following components.FontsMicrosoft-Windows-LanguageFeatures-Fonts-Thai-PackageNoneFonts required for some regions. ImportantIf you install an update that contains language-dependent resources prior to installing a language pack, the language-specific changes in the update won't be applied when you add the language pack. You need to reinstall the update to apply language-specific changes. To avoid reinstalling updates, install language packs before installing updates.Language updates have a specific order they need to be installed in. For example, to enable Cortana, install, in order: Microsoft-Windows-Client-Language-Pack, then –Basic, then –Fonts, then –TextToSpeech, and then –Speech. If you’re not sure of the dependencies, it’s OK to put them all in the same folder, and then add them all using DISM /Add-Package.Make sure that you are using language packs and features on demand that match the architecture of the image you are working with. Below are examples for building 64-bit systems.

Copy language files.Mount the Language pack ISO, and copy the language pack.cab files for the languages you're adding to C:templabLanguagePacks. The examples below will use the German and Japanese languages.Mount the Feature on Demand ISO, and copy the LanguageFeatures.cab files for the languages you're adding to C:templabLanguagePacks.

TipTroubleshooting: If an error occurs when running these commands, try the command again on the package that failed.Example: Error: 0x800f0825Package Microsoft-Windows-LanguageFeatures-Basic-en-us-Package may have failed due to pending updates to servicing components in the image.If the command completes with errors, check the DISM log file. At C:windowsLogsDISMdism.log. Add languages to Windows REHere we'll show you how to add languages to WinRE. Adding languages to WinRE ensures that the language that a customer expects is available in recovery scenarios. Follow these steps if you added languages to your Windows image.WinRE uses the same language packs as WinPE. TipIf you're creating several devices with identical hardware configurations, you can speed up installation time and first boot-up time by maintaining driver configurations when capturing a Windows image. Add drivers to your Windows image.Add a single driver that includes an.inf file.

In this example, we're using a driver named media1.inf: Dism /Add-Driver /Image:'C:mountwindows' /Driver:'C:DriversPnP.Media.V1media1.inf'Where 'C:DriversPnP.Media.V1media1.inf' is the base.inf file in your driver package.If you want to add an entire folder of drivers, you can use the /Recurse option. This adds all.inf drivers in the folder and all its subfolders.

WarningWhile /Recurse can be handy, it's easy to bloat your image with it. Some driver packages include multiple.inf driver packages, which often share payload files from the same folder. During installation, each.inf driver package is expanded into a separate folder, each with a copy of the payload files. We've seen cases where a popular driver in a 900MB folder added 10GB to images when added with the /Recurse option. Dism /Add-Driver /Image:'C:mountwindows' /Driver:c:drivers /Recurse.Verify that the drivers are part of the image: Dism /Get-Drivers /Image:'C:mountwindows'Check the list of packages and verify that the list contains the drivers you added.Add drivers to your WinRE imageIf you added drivers to your Windows image, you should also add them to your WinRE image. Adding drivers to your recovery image ensures they are available during recovery scenarios. Adding drivers to a WinRE image is the same process as adding drivers to a regular Windows image.

Dism /Add-Driver /Image:'C:mountwinre' /Driver:'C:DriversPnP.Media.V1media1.inf' /LogPath=C:mountdism.log. NoteYou can use the /recurse option to add an entire folder of drivers UpdatesWhile your image is mounted, you can add Windows updates.

The process is similar to the one we used to add drivers earlier.Reminder:. Add languages before major updates. Major updates include hotfixes, general distribution releases, or service packs.

If you add a language later, you'll need to re-add the updates. Add major updates before apps. These apps include universal Windows apps and desktop applications. If you add an update later, you'll need to re-add the apps. For major updates, update the recovery image too: These may include hotfixes, general distribution releases, service packs, or other pre-release updates. We'll show you how to update these later in Lab 12: Update the recovery image. If a Servicing Stack Update (SSU) is required, you'll have to apply it before applying the most recent General Distribution Release or any future GDRs.Add Windows updates to your imageUse DISM to apply the latest servicing stack update (SSU) and general distribution release (GDR) as well as any prerequisite KB updates.

You can find KB updates in the following locations:GDR:SSU:KB Files. ImportantIf you install an update (hotfix, general distribution release GDR, or service pack SP) that contains language-dependent resources prior to installing a language pack, the language-specific changes in the update won't be applied when you add the language pack. You need to reinstall the update to apply language-specific changes. To avoid reinstalling updates, install language packs before installing updates.Get a Windows update package. For example, grab the.

Extract the.msu file update to a folder, for example, E:updateswindows10.0-kb4016240-x640e60aebeb151d4b3598e4cfa9b4ccb1fc80e6e4d.msu. Make sure that your update matches the architecture of the image you are working with.To learn more, see.Add the msu to your mounted image using dism /add-package.

Dism /Add-Package /Image:C:mountwindows /PackagePath:'E:updateswindows10.0-kb4000001-x64.msu'You can also add multiple updates in the same command: Dism /Add-Package /Image:C:mountwindows /PackagePath:'E:updateswindows10.0-kb4000001-x64.msu' /PackagePath:'E:updateswindows10.0-kb0000002-x64.msu'. NoteEach package is typically a new KB that increases the build revision number of Windows. You can find the revision number of windows in the following registry key:HKEYLOCALMACHINESOFTWAREMicrosoftWindows NTCurrentVersionUBR.Lock in the update to ensure it get restored during recovery. DISM /Cleanup-Image /Image=C:mountwindows /StartComponentCleanup /ScratchDir:C:Temp.Verify that the updates are in the image. Dism /Image:C:mountwindows /Get-PackagesReview the resulting list of packages and verify that the list contains the package. For example: Package Identity: PackageforRollupFix31bf3856ad364e35amd6415063.250.1.1State: InstalledRelease Type: Security UpdateInstall Time: 6:26 PMThe operation completed successfully.Add Update packages to WinREIn this section, we cover how to add updates to the WinRE image. ImportantYou have to apply cumulative updates to your WinRE image in addition to your Windows image.

Because updates are cumulative, when a new update is installed, old updates can be removed. The WinRE optimization that we cover later in the lab will remove unnecessary updates which will keep the WinRE image from growing in size.To apply the update that you downloaded in the previous section to your WinRE image, you have to run dism /add-package to apply the update to the mounted WinRE image.

Dism /Add-Package /Image:C:mountwinre /PackagePath:'E:updateswindows10.0-kb4000001-x64.msu'Features and Apps Features on DemandAdd a Feature on Demand (FOD) to your Windows image. Are features that you can choose to preinstall. You can see a list of available FODs, and recommendations for preinstallation.Here we'll show you how to preinstall the.Net Framework Feature on Demand.Note: While it’s possible to add FODs using the /add-package command, we recommend using DISM with the /Add-Capability option.Mount the Features on Demand ISO.On your technician PC, use DISM to get a list of available FODs in an image: dism /image:C:mountwindows /get-capabilitiesThis will show a list of available capabilities.Add the.NET framework. Dism /image:C:mountwindows /add-capability /capabilityname:NetFX3 /Source:E:Where E: is the mounted FOD ISO.NET framework is now added to your image. AppsThis section covers working with Apps, including reinstalling inbox apps after updates, how to add Microsoft Store apps, and how to add Microsoft Office.This section continues to use your mounted Windows image. If your image isn't still mounted, mount it.Reminder: Install apps only after you have installed languages and updates, in that order. Reinstall inbox appsNow that you've added languages and updates to your image, you have to reinstall the apps that come with Windows.

This makes sure that the apps will work and include the languages you have added to your image. To reinstall these apps, you'll need the App update OPK or the inbox Apps ISO. Extract the inbox apps ISO to c:templabappsinboxamd64. Run the E:appsReinstallInboxApps-x64.bat script.Your apps are now ready to work with your image. Add a Microsoft Store appTo complete this section, you'll need to have the App update OPK or the inbox apps ISO.

Whichever you are using, we'll refer to it as the App update OPK in the following steps.Use DISM to add the HEVC codec.appx from the files you extracted in Step 1:.Install the HEVC.appx: DISM /Add-ProvisionedAppxPackage /Image:c:mountwindows /PackagePath:'C:templabappsamd64Microsoft.HEVCVideoExtension8wekyb3d8bbwe.x64.appx' /licensepath:'C:templabappsinboxamd64Microsoft.HEVCVideoExtension8wekyb3d8bbwe.x64.xml' /DependencyPackagePath:'C:templabappsinboxamd64Microsoft.VCLibs.x64.14.00.appx' /DependencyPackagePath:'C:templabappsinboxamd64Microsoft.VCLibs.x86.14.00.appx'. NoteInclude both the x86 and x64 versions of the dependency packages.Use DISM /Add-ProvisionedAppxPackage to add any additional apps to your image.Verify that the apps are installed: Dism /Image:'C:mountwindows' /Get-ProvisionedAppxPackagesInstall a Microsoft Store app that won't be pinned to the Start MenuFor this section, you'll need to have at least two apps to add to your image. If you don't have any signed apps you can skip to the next section.New in Windows 10, version 1803: A Microsoft Store app can now be installed without being pinned to the Start Menu. To install an app without also pinning it, use DISM /Add-ProvisionedAppxPackage with the /region switch when installing the app. When you create a custom Start Menu later in the lab, you'll be able to exclude an installed app from the Start Menu.Gather your apps for installation.Install your apps, specifying a region with the /region option for each app.

You can specify multiple regions by separating the regions with a. We'll show you how you can use LayoutModification.xml with /region later in the lab: Dism /Add-ProvisionedAppxPackage /PackagePath:app1.appxbundle /region='all'Dism /Add-ProvisionedAppxPackage /PackagePath:app2.appxbundle /region='US'Note: If your apps have dependencies, include them in the command using the /DependencyPackagePath. Like the examples in the previous section, it's common for apps to have dependencies on.NET.CoreRuntime and.VCLibs, but If your apps do not share those dependencies, then do not include them in your command.Optimize your installed appsNew in Windows 10, version 1803: You can reduce app disk usage by running DISM /Optimize-ProvisionedAppxPackages after you install apps. This command will only work when run against an offline image: DISM.exe /Image:'C:mountwindows' /Optimize-ProvisionedAppxPackagesPreinstall Microsoft Office Related setsThe Office apps are delivered as a set of apps that are installed and serviced together. The main package for Office is a set of shared code and each Office app (for example, Word, Excel, and PowerPoint) is installed as an optional package.

These packages are delivered as appxbundles that support all Store languages. NoteThe command for adding the Office apps in audit mode (online instead of offline) would be the same, but replace /Image:C:mountwindows with /online.Notes on Language SupportWhen install Office with DISM, Office language files are automatically added that match the languages that are in the Windows image. By default, Office will use the UI language of Windows. NoteThe Start layout and taskbar pins can be lost if the user resets their PC with the built-in recovery tools. To make sure these settings stay on the device, update the recovery image along with the Windows image.The Start tile layout in Windows 10 provides OEMs the ability to append tiles to the default Start layout to include Web links, secondary tiles, classic Windows applications, and universal Windows apps. OEMs can use this layout to make it applicable to multiple regions or markets without duplicating a lot of the work.

In addition, OEMs can add up to three default apps to the frequently used apps section in the system area, which delivers system-driven lists, including important or frequently accessed system locations and recently installed apps.To take advantage of the new features, and to have the most robust and complete Start customization experience for Windows 10, consider creating a LayoutModification.xml file. This file specifies how the OEM tiles should be laid out in Start. For more information about how to customize the new Start layout, see.Get started: Use the sample layoutmodification.xml we've included in the USB-B files. Start with this file for this section of this lab. You can find it in USB-BStartLayoutlayoutmodification.xml.To learn more about layoutmodification.xml, see.

About the Start Menu layout.Use the optional Region attribute in the RequiredStartGroups element to use different layouts for different regions. The Region value must be equal to two-letter country/region codes, and separated by a pipe ' ' delimiter if you're specifying multiple regions. The regions listed in the group are related to the regions you specified when you added apps to your image using the /region option.

If the country/region setting for the Windows device matches a RequiredStartGroups, then the tiles laid out within the RequiredStartGroups is applied to Start.If you specify a region-agnostic RequiredStartGroups (or one without the optional Region attribute) then the region-agnostic RequiredStartGroups is applied to Start.In your layoutmodification.xml, add regions to RequiredStartGroups:.Specify the tiles you want to add within an AppendGroup. OEMs can add a maximum of two AppendGroups. The following example shows two groups called 'Fabrikam Group 1' and 'Fabrikam Group 2', which contains tiles that will be applied if the device country/region matches what’s specified in Region (in this case, the regions are Germany, Spain, France, United Kingdom, Italy, and United States). Each group contains three tiles and the various elements you need to use depending on the tile that you want to pin to Start.In the Add Microsoft Store Apps section above, we asked you to install two apps using the /region switch: App1 and App2. Since we included a /region switch for both, both will be installed and appear in the All Apps list.

However, to get just App2 to also appear as a Start menu tile, add the following line inside your second in the LayoutModification.xml file, such as:Since we set the region to 'US' for App2 when provisioning it, we should set the region to 'US' here in our LayoutModification.xml to ensure App2 only appears as a Start menu tile in US images. So, ensure your region parameter looks like this:Or at least includes the US, such as this:.Add Microsoft Office Start Menu tiles.

This is a requirement for OEMs that participate in the Jumpstart program.You can have tiles appear on the Windows 10 Start menu for Word, PowerPoint and Excel. The tiles appear in a designated area for Microsoft apps (upper left in the following diagram). All additional apps will be accessible in the Apps list on the left.Add the following to the LayoutModification.xml file to add the tiles. NoteTo Add a desktop app, use the start:DesktopApplicationTile tag.

If you know the application user model ID for the app, use that to identify it. NoteIf the license terms are included, the OEM must include a version of the license terms in each language that is preinstalled onto the PC. A license term text must be an.rtf file, and have an.html file with a matching name in the same folder.

See for more information on license files.To begin adding license terms, you'll have to create folders for your license files, and then configure OOBE to show the license on first boot.Create folders for your system languages under the following directory: C:mountwindowsWindowsSystem32oobeinfodefault.Name each folder under the C:mountwindowsWindowsSystem32oobeinfodefault directory as the Language Decimal Identifier that corresponds to the language. Do this step for each language pack that's in the Windows image.Note: Please see.For example, if en-us and de-de language packs are added to the Windows image, add a folder named '1033' (representing en-us language) in C:mountwindowsWindowsSystem32oobeinfodefault. Then add a folder named '1031' (de-de language) under the same C:mountwindowsWindowsSystem32oobeinfodefault directory. MD c:mountwindowswindowssystem32oobeinfodefault1031MD c:mountwindowswindowssystem32oobeinfodefault1033.Create a license terms.rtf file for each language you have in your image, and copy them to the language-specific oobe folder.For example: Move the English agreement.rtf file to C:mountwindowsWindowsSystem32oobeinfodefault1033 directory and move the German agreement.rtf to C:mountwindowsWindowsSystem32oobeinfodefault1031. Copy E:resourcesenglish-agreement.rtf c:mountwindowswindowssystem32oobeinfodefault1033agreement.rtfcopy E:resourcesgerman-agreement.rtf c:mountwindowswindowssystem32oobeinfodefault1031agreement.rtf.Open a text editor and create.html versions of your license terms.

Save the terms to the same folders as the.rtf versions. You can use the from to create sample files. The names of the EULA files should be identical, except for the extension. C:mountwindowswindowssystem32oobeinfodefault1033agreement.html (English version)C:mountwindowswindowssystem32oobeinfodefault1031agreement.html (German version).Create an oobe.xml file to specify the license agreement.rtf file path.

Windows will automatically find the accompanying.html file. Below is a sample oobe.xml which is located at USB-BConfigSetoobe.xml agreement.rtf.Copy oobe.xml file to `C:mountwindowswindowssystem32oobeinfo.Copy oobe.xml to the laguage-specific folders you created earlier.For example: Copy oobe.xml to C:mountwindowsWindowsSystem32oobeinfodefault1033, which has a file called agreement.rtf in English.

To add the German agreement, copy oobe.xml to C:mountwindowsWindowsSystem32oobeinfodefault1031 directory, which has the German agreement.rtf file. Copy E:configsetoobe.xml c:mountwindowswindowssystem32oobeinfodefault1033copy E:configsetoobe.xml c:mountwindowswindowssystem32oobeinfodefault1031.Now each language folder has an oobe.xml, agreement.rtf, and agreement.thml file in that corresponding language.When the image first boots into OOBE, it will display the license agreement.

Create an image info file and add it to your image.Create an csup.txt file to specify when the Windows image was created. This file must include the date that the image was created, in the form of 'MM-DD-YYYY', with no other characters, on a single line at the top of the file. This command will create the file: echo 4-24-2018 'C:mountwindowsWindowscsup.txt'Customize Windows with an answer fileAnswer files (or Unattend files) can be used to modify Windows settings in your images during Setup. You can also create settings that trigger scripts in your images that run after the first user creates his/her account and picks the default language.

Answer files allow you specify various setup options, including how to partition disks, the location of the Windows image to install, and the product key to apply. Values that apply to the Windows installation, such as the names of user accounts, display settings, and Internet Explorer Favorites can also be specified. The answer file for Setup is typically called Unattend.xml.Unattend files include several sections, each of which are processed at different times throughout the Windows installation process. These phases are called configuration passes. Here are the most often-used passes:You can specify which configuration pass to add new settings to:.

1 - windowsPE: These settings are used by the Windows Setup installation program. If you’re modifying existing images, you can usually ignore these settings. 2 - offlineServicing: Settings in offlineServicing are processed when DISM is used to apply an unattend file to an offline image. 4 - specialize: Most settings should be added here. These settings are triggered both at the beginning of audit mode and at the beginning of OOBE. If you need to make multiple updates or test settings, generalize the device again and add another batch of settings in the Specialize Configuration pass. 6 - auditUser: Runs as soon as you start audit mode.AuditUser is a good place to run a system test script.

We'll add Microsoft-Windows-DeploymentRunAsynchronousCommand as our example. To learn more, see Add a Custom Script to Windows Setup.

7 - oobeSystem: Use sparingly. Most of these settings run after the user completes OOBE. The exception is the Microsoft-Windows-DeploymentResealMode = Audit setting, which we’ll use to bypass OOBE and boot the PC into audit mode.If your script relies on knowing which language the user selects during OOBE, you’d add it to the oobeSystem pass.While you can set many Windows settings in audit mode, some settings can only be set by using an answer file or Windows Configuration Designer, such as adding manufacturer’s support information. A full list of answer file settings (also known as Unattend settings) is in the.

Make an answer fileUse Windows System Image Manager (SIM) to create and modify unattend files. SIM is installed as part of the ADK. We have included some answer files in USB-B that will get you started. Make sure that your answer settings include the required settings as outlined in the OEM Policy Document:.For OA 3.0 systems: md c:mountwindowswindowspanthercopy /y E:AnswerFilesOA3.0Unattend.xml C:MountWindowsWindowsPanther(where E: is USB-B).For non-OA 3.0 systems: md c:mountwindowsWindowspanthercopy /y E:AnswerFilesNonOA3.0Unattend.xml C:MountWindowsWindowsPanther(where E: is USB-B)Create a catalog file in Windows SIMCatalog files (.clg) are files with information about settings that are applicable to a particular Windows image. When working with a Windows image in SIM, you have to first create a catalog file for the Windows WIM you're working with. Start Windows System Image Manager (WSIM). Click File Select Windows Image.

In Select a Windows Image, browse to and select the image file (D:install.wim). Select the Home edition of Windows 10 and click OK. Click Yes to create the catalog file. Windows SIM creates the file based on the image file, and saves it to the same folder as the image file. This process can take several minutes.The catalog file appears in the Windows Image pane. Windows SIM lists the configurable components and packages in that image.

Create an answer fileIf you're not working with the existing unattend file, you can create a new one in Windows SIM:. Click file New Answer FileThe new answer file will appear in the right-pane. Add answer file settingsIn this section, we'll show you how to create an answer file that can configure settings when you deploy your Windows image.Before you start, create a folder called Panther in your mounted Windows image. Windows will automatically look in this folder for an answer file.

NoteIf you don't want to enable S-Mode, you can.New in Windows 10, version 1803: Windows 10 S is no longer a separate SKU from other versions of Windows. S-mode is now a mode that can be activated on Home and Pro SKUs.Set S ModeIn this section, we'll show you how to enable S mode in a Windows image. ImportantMake sure to remove the manufacturing registry key before shipping your Windows 10 in S mode device.

NoteIf you're going to be capturing and deploying your final image as an FFU, choose the options to not configure recovery. This allows you to expand the Windows partition, if needed, after you apply your FFU. You can configure recovery after you expand the Windows partition.Run applyimage.bat and specify the image to apply: D:cd DeploymentApplyImage.bat D:Imagesinstall.wimWhere D: is the drive letter of your script and image on your USB Storage drive.When prompted by the script:.Choose whether or not to configure the recovery partition. Y: Configures the Windows recovery partition. N: Does not configure the recovery partition.

The recovery partition can be configured later. Choose this option if you're going to be capturing and deploying your image as an FFU.Press Y to format the drive.Choose N to not to deploy as Compact OS.Press N to indicate the image does not include extended attributes (EA). NoteOnly use compact OS on Flash drive based devices as compact OS performance is heavily dependent on the storage device capabilities.

Compact OS is NOT recommended on rotational devices. Please reference Compact OS for more information.Remove the USB drive and reboot the reference PC. ExitThe PC should boot into Windows Audit mode based on the settings of the unattend file we created earlier. If you're not using an unattend.xml file that sets the PC to boot into Audit Mode, you can press Ctrl+Shift+F3 during OOBE to boot into Audit mode.Make online customizations (audit mode)You can use audit mode to customize Windows using the familiar Windows environment. In audit mode, you can add Windows desktop applications, change system settings, add data, and run scripts.To make sure your audit mode changes are included in the recovery image, you'll need to capture these changes into a provisioning package using ScanState.

This package gets used by the system recovery tools to restore your changes if things go wrong. You can optionally save drive space by running the applications directly from the compressed recovery files; this is known as single-instancing.If you want to capture the changes in an image and apply it to other devices, you'll need to use Sysprep to generalize the image. Verify Customizations in Audit ModeWe don't recommend connecting your PC to the internet during manufacturing, and also don't recommend isntalling updates from Windows Update in audit mode because it will likely generate an error during sysprep. After setup has finished, the computer logs into Windows in Audit mode automatically as an Administrator. Verify the changes from the answer file (see manufacturer name, support phone number and other customizations) are present.Verify the editionEarlier in the lab, we upgraded the edition from Windows Home to Windows Professional.

Verify this change:.Open Command Prompt as administrator.Run: dism /online /get-current-edition.Make sure it's the right edition. It should look like this: Current edition is:Current Edition: ProfessionalThe operation completed successfully.Note: If you are working with a device that has S Mode enabled, the edition will still just say 'Professional.' This is because S Mode is a mode, not an edition.Verify S ModeIf you enabled S Mode earlier in the lab, verify that S Mode is enabled. From Start, open Settings.

In Settings, open Update & Security. Choose Activation from the left paneIf your device has S Mode enabled, it will show here. Apps and Store opportunitiesThrough Windows 10 and the Microsoft Store, you have tremendous opportunities for brand and device differentiation, revenue creation, and customer access.Microsoft Store apps are at the center of the Windows 10 experience. They are Windows universal apps, so you can build apps for desktops, tablets, or phones that run Windows 10. As an OEM, you can provide an engaging customer experience and increase brand loyalty by providing a great set of value-added software and services along with the high-quality hardware that you build.Important: The key below must be set in Audit mode.You have to change a registry setting to add your OEM ID.

If you're an OEM Microsoft Store Program participant, contact PartnerOps@microsoft.com to get your OEM ID. ImportantThe OEMID registry key is not restored automatically during PBR in Windows 10. Please refer to the scanstate section of this guide on how to restore the OEMID registry key during PBR operation. Prepare your image for Push Button ResetThis section provides guidance for setting up the recovery environment for Push Button Reset (PBR) scenarios.Please reference Push-button reset and Windows Recovery Environment (Windows RE) and Hard Drives and Partitions for more information.Push-button reset, is a built-in recovery tool which allows users to recover the OS while preserving their data and important customizations, without having to back-up their data in advance. ImportantDon't ship a Windows 10 in S mode device with the registry key in place.Finalize and Capture your imageWe'll show you how to finalize and capture a factory image for mass deployment. To start this section, make sure your reference machine is shutdown after running sysprep in the previous section.Boot the Reference computer into WinPE.After WinPE has booted connect USB-B.Troubleshooting:.If the reference PC boots from its internal HDD, Windows will enter the specialize and OOBE passes. You won't be able to capture a stable and generalized image if any of the configuration passes have completed.

If either of those passes have completed, you'll need To generalize the image again. You can do with in Audit Mode ( during OOBE). In Audit mode, run the Sysprep command from above.

Make sure the PC boots to WinPE on the next restart.If the system still boots to the internal HDD, check the PC's boot priority. Make sure that the USB has a higher boot priority than the internal hard drive.Identify Windows Partition Drive letter using diskpart.At the X:windowssystem32 prompt, type diskpart and press the key to start Diskpart.At the DISKPART prompt type list volume.Under the 'Label' column, locate the volume that is labeled 'Windows'.Note what letter it is has been assigned under the 'Ltr' column (Example: C).

This is the USB key's drive letter.Type exit to quit Diskpart.(CompactOS Only) Convert installed customizationsThis section shows how to reduce the size of ScanState packages. ImportantOnly do this step if you are deploying to a device with limited storage. Single instancing impacts the launch performance of some desktop applications.See for more information.To reduce the size of your ScanState recovery packages, run the following command from WinPE on your reference device: DISM /Apply-CustomDataImage /CustomDataImage:C:RecoveryCustomizationsapps.ppkg /ImagePath:C: /SingleInstanceCapture your imageIn this section, we'll tell you how to capture your sysprepped image. You can capture either a or an. Capture a WIMOn your reference PC:.Identify Windows Partition Drive letter.At the X:windowssystem32 prompt, type diskpart and press the key to start Diskpart.At the DISKPART prompt type list volume.Under the 'Label' column, locate the volume that is labeled 'Windows'.Note what letter it is has been assigned under the 'Ltr' column (Example: C). This is the drive letter that needs to be used.Type exit to quit Diskpart.Capture the image of the windows partition to USB-B. This process takes several minutes.Note: We recommend using a cache directory when running DISM.

In this step we'll create scratchdir on the USB-B key for temporary files, but you can choose any hard drive with available space for your scratch directory. MD e:scratchdirDism /Capture-Image /CaptureDir:C: /ImageFile:E:ImagesCustomImage.wim /Name:'CustomImage' /scratchdir:e:scratchdirThis captures an image called CustomImage.wim to E:Images. When the image capture is complete, you can shut down your reference PC.With your image captured, you can skip to.

Capture an FFUOn your reference PC:.Identify Windows Partition Drive letter.At the X:windowssystem32 prompt, type diskpart and press the key to start Diskpart.At the DISKPART prompt type list disk.Under the 'Disk ###' column, identify the the disk that has the Windows installation, and note the assigned disk number. This will look something like Disk 0.Type exit to quit Diskpart.Capture an image of the windows disk to USB-B. This process takes several minutes. DISM.exe /capture-ffu /imagefile=E:ImagesCustomImage.wim /Name:'CustomImage' /capturedrive=.PhysicalDrive0 /description:'Windows 10 FFU'This captures an image called CustomImage.wim to E:Images.

When the image capture is complete, you can shut down your reference PC.Verify your final imageIn this section, we'll cover how to deploy your captured image for testing and verification.