Mar 06, 2018 Hi, Microsoft Official website only provide the evaluation of Windows Server 2012 R2 Datacenter 64-bit ISO for download, in general, we can convert from evaluation to retail version using command line below with your own license: DISM /online /Set-Edition:/ProductKey:/AcceptEula However, you had Standard version license key, and it is unable to do. Oct 03, 2016 Microsoft Windows 7 Home Premium OEM ISO Free Download Microsoft Windows 7 Home Premium is a complete operating system with better security and improved performance to fulfill the basic needs. This free download of Home Premium is the complete standalone ISO Image installer for genuine OEM version for both 32bit and 64bit architecture.
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. 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:
Next we'll move onto customizing your Windows image. We'll start with offline customizations to a mounted Windows image, where we'll cover:
We'll finish customizing the Windows image by deploying your image to a PC and then booting into Audit mode and finish making changes, including:
Finally, we'll Finalize and Capture your image, verify everything works, and prepare your image for deployment.
Let's get started!
Prepare your lab environment
Note
If you haven't gathered the files you need to go through this lab, see Get the tools you need for OEM deployment of Windows 10 for desktop editions.
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:):
A technician PC that has:
Let's setup your lab.
Install the Windows ADK for Windows 10
The Windows ADK is a collection of tools that enables you to manage and deploy custom Windows installations to new computers.
Important
Use 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:
Create a bootable Windows PE (WinPE) partition
WinPE 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
Customize WinPE
You 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:
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 image
To 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:
Add 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 WinPE Optional Components 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 Environment<arch>WinPE_OCs . Here's how to add Powershell support for en-us:
Note
Only add additional packages when necessary. The more packages you add, the greater the impact to boot time and performance.
Add drivers to WinPE (If needed)
If you need to add drivers to WinPE, you'll use
Dism /Add-Driver . You'll only need to do this if WinPE doesn't already include the drivers for your hardware.
Here's how to add drivers to WinPE:
Note
This method requires .inf-based drivers. Get .inf-based drivers from your hardware vendor.
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. For example:
Where
C:drivers is the drivers folder that you're adding.
Set the power scheme to high-performance
Setting WinPE to use high-performance mode will speed deployment. The sample scripts set WinPE to high-performance mode when they run, but if you want to make sure that WinPE always runs in high-performance mode, you can modify
startnet.cmd in the WinPE image.
Cleanup your WinPE image
Run
dism /cleanup-image to reduce the disk and memory footprint of WinPE and increase compatibility with a wide range of devices:
See WinPE: Optimize and shrink the image for more details.
Commit your changes and unmount your image
If you've added extra files in your WinPE image, you can delete them to reduce your image size and improve performance. When you're done working with your image, you can commit your changes and unmount your image. Then export your customized WinPE image into your WinPE folder:
Create a bootable WinPE drive
Now that you've updated your WinPE image to include everything it needs, you can make a bootable WinPE drive. From the Deployment and Imaging Tools Environment:
Boot your reference PC to WinPE
Leave this PC booted to Windows PE for now. You can remove the bootable USB drive.
Customize your Windows image
Now 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.
Prepare and mount a Windows imageMicrosoft Windows 10 Professional 64 Bit Oem Download
In 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 Get the tools you need section.
Backup your Windows image file
Before 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.
Mount your Windows image
Create a mount directory and mount basicimage.wim:
(where E: is the drive letter of USB-B)
Mount your WinRE image
If a system can't successfully boot into Windows, it will fail over to the Windows Recovery Environment (WinRE). WinRE can repair common causes of unbootable operating systems. WinRE is based on WinPE, and to make it work for your customers, you can add drivers, languages, Windows PE Optional Components, and other troubleshooting and diagnostic tools.
The WinRE image is included inside the Windows 10 image, and is eventually copied to the Windows RE tools partition on the destination PC or device. To modify the WinRE image, you'll mount the Windows image, then mount the WinRE image inside it. Make your changes, unmount the WinRE image, then unmount the Windows image.
You should update your recovery image to ensure a consistent recovery experience whenever you:
Note
This lab assumes youâd rather keep winre.wim inside of install.wim to keep your languages and drivers in sync. If youâd like to save a bit of time on the factory floor, and if youâre okay managing these images separately, you may prefer to remove winre.wim from the image and apply it separately.
Offline customizations
With 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 Languages
In 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
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:
Add or change languages
In this section, we'll add languages and Features On Demand to your Windows image. We'll add the German (de-de) language pack, then we'll add the Japanese (ja-jp) language. Japanese is an example of a language that requires additional font support.
Important
If 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
Configure language settings
This section covers how to change the default language and timezone of your mounted Windows image.
Set the default timezone
You can use DISM to set the default timezone for a PC. Here we'll set the time zone. See Default time zones for a list of available time zones.
Remove the base language from the image
This section covers removing a language from the Windows image. This is an optional step.
Now that our image has been set to use German as the default language, we can remove the English language features from it and make it a non-English image. To remove en-US completely from the image, you'll have to remove several components.
Warning
Don't remove the English base language if you're shipping a PC in English.
For removing the language components from a 64-bit image:
Tip
Troubleshooting: If an error occurs when running these commands, try the command again on the package that failed.Example:
If the command completes with errors, check the DISM log file. at C:windowsLogsDISMdism.log.
Add languages to Windows RE
Here 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. You can find these language packs on the language pack ISO, and you can find language-specific WinPE OCs in the ADK installation folder at
C:Program Files (x86)Windows Kits10Assessment and Deployment KitWindows Preinstallation Environmentamd64WinPE_OCs<lang>
To complete this section, copy the language packs from the Language pack ISO and the WinPE OCs from
C:Program Files (x86)Windows Kits10Assessment and Deployment KitWindows Preinstallation Environmentamd64WinPE_OCs to C:TempLabLanguagePacksRE<language> .
Remove the base languages from WinRE (Optional)
Similar to removing the base language in install.wim, we can remove the base language from WinRE as well.
For removing language components from a 64-bit image:
Drivers
You can add drivers to ensure Windows can successfully boot for the first time. Make sure that you add your driver to the right image:
The following shows how to add drivers in various ways. If your hardware doesn't require any additional drivers, you don't have to add any.
Tip
If 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
Microsoft Windows 7 Oem DownloadAdd drivers to your WinRE image
If 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.
Note
You can use the /recurse option to add an entire folder of drivers
Updates
While your image is mounted, you can add Windows updates. The process is similar to the one we used to add drivers earlier.
Reminder:
Add Windows updates to your image
Use 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: https://aka.ms/win10releaseinfo
SSU: https://msdn.microsoft.com/en-us/windows/hardware/commercialize/manufacture/whats-new-in-windows-manufacturing
KB Files: https://catalog.update.microsoft.com
Important
If 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.
Add Update packages to WinRE
In this section, we cover how to add updates to the WinRE image.
Important
You 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.
Features and AppsFeatures on Demand
Add a Feature on Demand (FOD) to your Windows image. Features on Demand are features that you can choose to preinstall. You can see a list of available FODs, and recommendations for preinstallation here.
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.
.NET framework is now added to your image.
Apps
This 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 apps
Now 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.
Your apps are now ready to work with your image.
Add a Microsoft Store app
To 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.
Install a Microsoft Store app that won't be pinned to the Start Menu
For 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.
Optimize your installed apps![]()
New 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:
Preinstall Microsoft OfficeRelated sets
The 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.
Add Office apps to your image
To add the Office apps to an image, use DISM with the
/Add-ProvisionedAppxPackage option. This option also requires the following information for each app you add:
Modify the Start layoutNew in Windows 10, version 1803
Apps can now be pinned to the All Apps list without also having to be pinned as a Start tile. This is done through the new 'region' switch (as described in the previous section). In the previous section, we added three apps to our image: App1, App2, and Office. In this lab, we will omit App1 from LayoutModification.xml to ensure that App1 only appears in the All Apps list, and not also as a Start menu tile. We will also include App2 in LayoutModification.xml to demonstrate that even if the 'region' switch was used when adding the app to the image, the app will still appear in the Start Menu if included in the LayoutModification.xml file. In other words, the LayoutModification.xml file takes precedence.
Start menu
If you donât create a LayoutModification.xml file and you use the Start Unattend settings, Windows will take the first 12
SquareTiles or DesktoporSquareTiles settings specified in the Unattend file. The system then places these tiles automatically within the newly-created groups at the end of Start. The first six tiles are placed in the first OEM group and the second set of six tiles are placed in the second OEM group. If OEMName is specified in the Unattend file, the value for this element is used to name the OEM groups that get created.
Note
The 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 Customize the Windows 10 Start Layout.
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 LayoutModification XML.
About the Start Menu layout
Note
To 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. Otherwise, if you pinned tiles that require .url or .lnk files, add the files to the following legacy Start Menu directories:
Example:
Add a license agreement and info fileAdd an OEM-specific license
In this section, we'll cover how an OEM can add their own license terms during OOBE.
Note
If 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 OEM license terms 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.
When the image first boots into OOBE, it will display the license agreement.
Create an image info file and add it to your image
Customize Windows with an answer file
Answer 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.
Microsoft Windows 7 Pro Oem Iso Download
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:
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 Unattended Windows Setup reference.
Make an answer file
Use 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:
Create a catalog file in Windows SIM
Catalog 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.
The catalog file appears in the Windows Image pane. Windows SIM lists the configurable components and packages in that image.
Create an answer file
If you're not working with the existing unattend file, you can create a new one in Windows SIM:
Microsoft Windows 7 Starter Oem Download
The new answer file will appear in the right-pane.
Add answer file settings
In 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.
Add OEM info (optional)
Next you'll have to make sure that the logo you specified above is in your Windows image.
Set the device to automatically boot to audit mode
Using the same unattend.xml file, set the PC to automatically boot into Audit mode.
Enable S-Mode
Note
If you don't want to enable S-Mode, you can skip to the next section.
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. We'll use an Unattend file that has a setting in Pass 2 - offlineServicing, and use DISM to apply it to our mounted Windows image.
S mode is now applied to the Windows image. When the PC boots, the same Code Integrity policy that is enforced in Windows 10 S will be enforced on your Windows installation.
Enable Manufacturing mode
If you plan to make additional changes to your image in audit mode, such as editing the registry, running a script, or running a command from the command-prompt, you have to temporarily enable Manufacturing Mode, which allows unsigned code that is normally blocked in S Mode to run in Audit mode. This allows you to run scripts, installers and diagnostic tools (i.e., unsigned code) during the manufacturing process. Manufacturing Mode is enabled by adding a registry key to the offline image, and itâs disabled by removing the key when booted into audit mode.
After you unmount your image and commit your changes (below), your Windows 10 in S Mode image will have the manufacturing key that will allow you to run unsigned code in audit mode.
Important
Make sure to remove the manufacturing registry key before shipping your Windows 10 in S mode device. We show you how to do that later in the lab, or you can learn how at Manufacturing mode
Set the Windows edition
In this section, we will upgrade the Windows OS edition from Home to Pro.
Notes:- You cannot set a Windows image to a lower edition.- Note: You should not use this procedure on an image that has already been changed to a higher edition.- Since S-mode is not enabled until this image is booted on the Reference device, it doesnât matter if you run the /Set-Edition command before or after applying the unattend settings (which includes the S-mode
<SkuPolicyRequired> element).- You wouldn't normally switch editions offline like we'll show you here. Instead of upgrading editions, you would've mounted a Windows Professional wim to begin with. This step is included here for instructional purposes; just to show you the use of the /Set-Edition command.
Keep Windows settings through a recovery
In recovery scenarios, Windows doesn't automatically save settings created through with answer files, Windows Start Menu customizations created with LayoutModification.xml, or first-login info from oobe.xml.
To make sure Windows saves your customizations:
Optimize WinRE (part 1)
Unmount your images
You now have a customized Windows image that you can deploy to other PCs. In the next section, we'll show you how to deploy the image to your reference PC, make online changes, and then finalize the Windows image to get it ready for final deployment.
Deploy your images to a new PC
In this section we'll deploy an image to a PC so that it can be customized in Audit mode. Before you start this section:
Boot to WinPE
If you're not already booted into WinPE on the device you're deploying your image to, boot into WinPE:
Use a deployment script to apply your image
Run a script to create partitions and apply your image. We'll use applyimage.bat in USB-Bdeployment to do this for us.
ApplyImage.bat uses diskpart scripts to create the partitions and define the partition layout. This script and the subscripts it calls must be placed in the same subfolder. You can update these scripts to change the partition sizes as you desire.
Note
If 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.
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 Mode
We 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.
Verify the edition
Earlier in the lab, we upgraded the edition from Windows Home to Windows Professional. Verify this change:
Verify S Mode
If you enabled S Mode earlier in the lab, verify that S Mode is enabled.
If your device has S Mode enabled, it will show here.
Apps and Store opportunities
Through 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 [email protected] to get your OEM ID.
OEMID
SCMID
Important
The 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 Reset
This 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. It reduces the need for custom recovery applications by providing users with more recovery options and the ability to fix their own PCs with confidence.
I
Prepare ScanState
To start working with Push Button Reset, you'll need to copy ScanState to USB-B.
Use scanstate to capture Classic Windows applications and settings on your image.
Note: You'll use your technician PC to prepare ScanState.
Create a Scanstate migration file
In this section, you'll create a configuration file that will restore files and registry keys during Push-button reset.
Create a migration XML file used to restore registry values manually entered during manufacturing process. The sample below restores the OEMID registry value set earlier in this document.
Note:USB-Brecoveryrecoveryimageregrecover.xml already contains the registry values. You can use this file instead of creating a new file.
Create recovery package using Scanstate
On your reference PC:
Use ScanState to capture installed customizations into a provisioning package, and then save it to c:Recoverycustomizations. We'll use samples from USB-BRecoveryRecoveryImage to create the provisioning package.
Important: For Push Button Reset to work properly, packages have to be .ppkg files that are stored in C:RecoveryCustomizations.
Create Extensibility scripts to restore additional settings
You can customize the Push-button reset experience by configuring extensibility points. This enables you to run custom scripts, install additional applications, or preserve additional user, application, or registry data.
During recovery, PBR calls EnableCustomizations.cmd which we'll configure to do 2 things:
This will restore the additional layout settings from these 2 answer files during PBR.
[!ImportantRecovery scripts and unattend.xml must be copied to c:RecoveryOEM for PBR to pickup and restore settings defined in the unattend.xml.
Copy unattend.xml files for restoring settings
For OA 3.0 systems:
For non-OA 3.0 systems:
Copy winre.wim backup
During the deployment winre.wim file is moved. Before capturing a final image, the backup winre.wim we created must be copied back, or the recovery environment will not work in the final image deployment.
Reseal the image
In this section, we'll use sysprep.exe to reseal our image and get it ready for factory deployment.
Remove the Windows 10 in S mode manufacturing key
If you have manufacturing mode enabled, remove the manufacturing registry key:
Finalize and Capture your image
We'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.
(CompactOS Only) Convert installed customizations
This section shows how to reduce the size of ScanState packages.
Important
Only do this step if you are deploying to a device with limited storage. Single instancing impacts the launch performance of some desktop applications.
See Compact OS for more information.
To reduce the size of your ScanState recovery packages, run the following command from WinPE on your reference device:
Capture your image
In this section, we'll tell you how to capture your sysprepped image. You can capture either a WIM or an FFU.
Capture a WIM
On your reference PC:
With your image captured, you can skip to Verify your final image.
Capture an FFU
On your reference PC:
Verify your final image
In this section, we'll cover how to deploy your captured image for testing and verification.
Deploy your image to the reference device
Validate the configuration
Your PC will restart and boot into Windows for the first time.
Verify Recovery
Microsoft Windows 7 Oem Download
Note: The Push-button reset UI has been redesigned in Windows 10. The Keep my files option in the UI now corresponds to the Keep my files feature. Remove everything corresponds to the Remove everything feature.
Optimize final image
At this point, you have a Windows image that is almost ready for deployment. In this section, we'll show you how to put the finishing touches on your image so you're ready for deployment.
Final shipment
You have to boot a PC at least once to allow the specialize configuration pass of Windows Setup to complete before shipping a PC.
The specialize configuration pass adds hardware-specific information to the PC and is complete when Windows OOBE appears.
Reference the OEM Policy Documentation for more details.
Reducing Disk Footprints
Throughout this guide, we have shown a few places where you can reduce the disk footprint:
This section shows a few more ways you can gain additional free space.
Reducing and turning off Hiberfile
Reducing and turning off hiberfile can return between 400MB to 1.5GB OS space on the deployed OS.
Microsoft Windows 10 Home Oem Download
Reducing Hiberfile by 30%
When you run sysprep.exe with unattend.xml, you can add a FirstLogonCommand that will reduce hiberfile:
Turn Off Hiberfile
When you run sysprep.exe with unattend.xml, you can add a FirstLogonCommand that will turn off hiberfile:
Capture your image with the unattend.xml file that contains these settings.
Disk footprint with optimizations
The table below shows additional space saved by using compact OS, Single instancing, and reducing or turning Off Hiberfile on 2GB (x86) and 4GB (x64).
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |