Windows 10 Anniversary Update Customization, Deployment and Manufacturing Jessie Labayen Principal Program Manager
Agenda OEM Activation
Windows 10 Desktop Manufacturing and Deployment
Integrate/ Deploy/ Full Plan Try Test Pilot run production • Deploy in factory test environment • Mass production • Identify which apps and drivers to • Create new process or integrate • What is new? preload into existing process • Measure performance • What do I have to change? • Identify additional customizations • Validate tools and processes in • Validate tools/process in factory • What do I need to prepare? own environment • Understand impact of app and environment • Who will do the work? driver installation on process • Manufacturing work back • Validate diagnostic tools in • How do I integrate into my existing process? schedule Windows 10 environment • Build sample image and test
Follow the process that best fits your company’s needs while noting the difference in factory cost and downstream impact Build-to-Stock/Plan Build-to-Order A build based on a pre-determined (forecasted) order A build that may be based on forecasted or just-in-time order Predictable May be a single device ordered by a user through an OEM • site Almost the same HW and SW through the entire run rate May be a small order with option to change configuration • Lower manufacturing cost during the selling season May be a large order placed by a channel or enterprise • customer Flexibility is a high priority Just-in-time changes on hardware and app configuration Higher manufacturing cost
Preinstalling Apps, Drivers and Settings Imaging and Recovery
Preinstalled app principles Respects customer consent - Customers can control their permissions and privacy Trustworthy - Kept up-to-date and highly rated by customers in the Store Well-behaved - Respects customers' bandwidth; app update behavior is controlled and considerate of customers Efficient - Launches quickly, shuts down smoothly, respects online/offline status and does not impact other experience Durable - Full-featured apps that are not time-limited Language pack dependency Always add the language pack first before installing apps If you add a language pack after preinstalling the app, you will need to reinstall the app
Use drivers that install via INF instead of SETUP .EXE Enables you to install the driver offline (faster) or online (slower) WICD, DISM and Windows Update only support INF driver installation 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 Bundled hardware apps Apps that are bundled with the driver consume additional disk space and memory footprint Check dependency on functionality and impact (e.g., responsiveness, battery life, media playback) What if I only get a driver as SETUP .EXE
Benefits Offline injection of a desktop app Improved image management Reduces time to create a new image Boot online or Lab Prepare to Audit mode, and Reference Install classic Windows app device Classic Repeat for each Reference Siloed Provisioning Windows ScanState.exe Multiple SPP’s Windows app Application Device Package (SPP) Base Image New!
Windows Imaging and Configuration Designer (WICD) – A UI based tool used to customize both Windows Desktop and Mobile DISM – An advanced command line based tool used to customize and deploy Windows Desktop only Improvements in Extended Attributes reduces first boot (OOBE) time Support for Siloed Provisioning Packages (SPP) improves image creation and management Recovery Improved reliability and experience * Applies to Mobile also
Disk Footprint Optimization Guidance
What is disk footprint WinRE Recovery image for preinstalled • Recovery desktop apps (USMT.PPKG) Preinstalled Desktop and Store • Apps apps Free Space 32-bit vs. Drivers and applets/utilities • Drivers 64-bit dependent Windows binaries • OS + App System files • Partition Language packs, Features-on- Windows • Demand Cumulative updates Other • Partitions
Windows disk footprint - compact OS Replaces WIMBoot Per-file compression of OS Compression is performed during image apply Single-instancing of PPKG
Local disk recovery (aka PBR v2) Windows 10 Recovery recovers to an updated state OS and drivers are always restored to the most recent “rollup”, not the factory image Updates since the most recent “rollup” are discarded and reinstalled by Windows Update after recovery OEM customizations such as apps are restored to the factory state Refresh will not restore user installed Store apps Windows RE T ools Partition Size Requirements/Impact The Windows RE tools partition should always include sufficient free space to ensure that backup applications can function properly
Windows disk footprint – LP and FOD Language Pack (LP) Language packs have an immediate impact on image size in manufacturing, even though unused ones are cleaned up after OOBE Features-on-Demand (FOD) Only preinstall FODs that are applicable to your hardware and/or target audience (e.g., do not preinstall the handwriting FOD unless you ship with pen or plan to offer pen support in your hardware
Windows disk footprint – CU’s 1. Mount WIM. 2. Inject LPs/FODs. 3. Inject AppX packages. 4. Inject CUs. 5. Perform cleanup where <mount> is the path to the mounted WIM. dism /image:<mount> /cleanup-image /startcomponentcleanup /resetbase 6. Unmount and save WIM. 7. Export WIM where source.wim is the WIM from step 6 and target.wim is a new WIM filename. dism /export-image /sourceimagefile:<source.wim> /sourceindex:1 /destinationimagefile:<target.wim>
Windows disk footprint – system files Hibernation file (hiberfil.sys) By default, both hibernate and fast startup features are enabled which requires a hibernation file size equivalent to <80% of the total memory installed Options to reclaim disk space Option 1 – Disable hibernate only feature (“reduced” option is 20% of physical memory installed) Implementation – Run powercfg /h /type reduced from an elevated command prompt while in Audit Mode Reclaimed disk space varies (>=600 MB) depending on total memory installed Option 2 – Disable hibernate and fast startup Implementation – Run powercfg /h off from an elevated command prompt while in Audit Mode Reclaimed disk space varies (>=800 MB) depending on total memory installed
Apps and drivers Apps and Drivers are language pack dependent Even though unused OS language packs are removed, resource files for preinstalled apps/drivers may remain – check with your ISV and IHV Apps and Drivers are architecture (x86 vs. x64) dependent 64-bit versions use more disk space Driver bundled applets Are the bundled applets required? Do they offer additional functionality and/or an improved experience?
Disk footprint estimates Configuration 32-Bit Change 64-Bit Change Baseline 11.68 GB 17.24 GB Compact OS applied 8.85 GB -2.83 GB 13.45 GB -3.79 GB With single-instancing 7.66 GB -4.02 GB 12.28 GB -4.96 GB Hiberfile Reduced 7.26 GB -4.42 GB 11.03 GB -6.21 GB Hiberfile Off 6.8 GB -4.88 GB 8.03 GB -9.21 GB 32-bit Configuration – Single language Windows Home + Office 2016 + drivers with 2 GB of RAM 64-bit Configuration – Singe language Windows Home + Office 2016 + drivers with 8 GB of RAM Data reflected in the table are estimates based on a pre-release version and hardware configuration and subject to change.
Considerations What is the purpose of running the test? Are you using telemetry and/or factory/field failure rates to define the tests (type and run time)? Work with your IHV to optimize test time and factory floor resources Burn-in If you are doing it, why? Is there positive ROI by doing burn-in at the expense of increased manufacturing time (cost)? T est tools Are the tools for manufacturing or design validation? Manufacturing tests should focus on validating the assembly and/or component quality
Windows Desktop Call to Action
Windows Desktop Call to Action NEW Enable extended attributes to improve first boot (OOBE) performance NEW
References Push Button Reset MSDN Implementation Deployment Step by Step Guide (v2.02) https://msdn.microsoft.com/en-us/windows/hardware/commercialize/manufacture/desktop/system- builder-deployment-of-windows-10-for-desktop-editions https://msdn.microsoft.com/en-us/windows/hardware/commercialize/manufacture/desktop/oem- deployment-of-windows-10-for-desktop-editions Compact OS Implementation, Single Instancing, and Image Optimizations https://msdn.microsoft.com/en-us/library/windows/hardware/dn940129(v=vs.85).aspx
Windows 10 Mobile
Mobile is a separate image (OS) from Desktop Mobile is a worldwide image Mobile disk footprint is different than Desktop Mobile image creation and deployment processes can be applied to Desktop Mobile does not require OEM activation
Windows 10 Mobile supports the following high-level manufacturing flow but can be customized to your specific needs Device Image Provisioning/ Pack and QA SMT OS Flash Assembly and Creation Security Sampling Testing Some items have dependencies on Silicon Vendors
Recommend
More recommend
