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
• What is new? • Create new process• orIdentify integrate which apps• andDeploy drivers in factory to test• Mass environment production preload • What do I have to change?into existing process • Measure performance • Identify additional customizations • What do I need to •prepare?Validate tools and processes in • Validate tools/process in factory own environment • Understand impact ofenvironment app and • Who will do the work? • Manufacturing work driverback installation on• Validateprocess diagnostic tools in • How do I integrate into my existing process? schedule • Build sample image andWindows test 10 environment 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
Reduces time tocreate a newimage Improved management image ofinjectionOffline adesktopapp Benefits Lab Base Base Image Windows Windows Reference Prepare device Reference Device Install classic Windows app classic Install to Auditto mode, and Boot Boot online or Windows Windows app Classic ScanState.exe Package (SPP) Package Siloed Provisioning New! Repeat for Repeatfor each Application Multiple SPP’s 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)
Apps • Preinstalled Desktop and Store Free Space apps
32-bit vs. Drivers • Drivers and applets/utilities 64-bit dependent • Windows binaries OS + App • System files Partition Windows • Language packs, Features-on- Demand Other • Cumulative updates 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 Tools 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
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)? Test 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 https://msdn.microsoft.com/en- us/windows/hardware/commercialize/manufacture/mobile/mobile-deployment-and-imaging OEM Activation Tool OEM Corporate OEM Factory/TPI End-Customer • Stores Product Key 3 • Insert Product Key into BIOS • Online Use of Computer Inventory Product KeyComputer provides: • Calculate HW Hash for Each Build Rpt Computer Manufactured • Per-device unique identifier verifiable by Microsoft 1 2 • Adhere Genuine Windows 4 • OS Edition (e.g. Home, Pro) Label Factory Deliver Ship Deliver & • OEM identity Order Keys Computers Bill Event Hardware Hash provides: Computer Windows Order Deliver • MappingBuild of product key to HW components detected during manufacturing Activation Keys 1 3 Keys 2 Report 5 Request Activation 6 Microsoft
3 Computer Build Report Data Windows Activation Microsoft Operations Data Repository Services
MICROSOFT CONFIDENTIAL – Provided Under NDA
OHR reported data does not align with information stored in SMBIOS CHID and telemetry data can’t be reconciled with OHR data
OHR Field SMBIOS Field Call To Action
FRM_FACTOR_CL1 Enclosure or Chassis type 3 Update SMBIOS to v3.0.0 to add support for Tablet, Convertible and Detachable FRM_FACTOR_CL2 Define the chassis type consistently in SMBIOS (Baseboard Product field?) PC_MODEL_SKU Product Name Standardize on a single SMBIOS field that uniquely identifies a device’s configuration Baseboard Information Family SKU Number
Digital Inventory System 3.0 Digital Inventory System in the Cloud Digital Inventory Solution Migration Plan
Costing Comparison Capability Comparison OA3.0 Solution Overview This next version of DIS was design with goal of removing limitations for OEM’s, and adapt to the dynamic market needs. Some key new feature are: Multiple CBR upload: DIS 3.0 will allow the selection & upload of multiple CBR reports at once DLS limitations removed: The limit of 5 DLS per installation is removed, and partners can have an unlimited number of DLS partners Multiple OEM’s support: DIS 3.0 enables MSFT partners to manage multiple sold to OEM’s in a single instance, and unified user interface. Serial number & DPK mapping: DIS 3.0 will extract the serial # from the BIOS match it to DPK, and store it. This information is available for reporting and tracking purposes. Deployment simplification: DIS 3.0 will have a simple installation wizard This new solution will address key partner pain points preventing Microsoft from completely migrate from a physical COA to a digital world. The key features Cloud OA will offer are: One click onboarding process Digital key distribution CBR/OHR/PBR submission Leveraging DIS 3.0 & DPC Billing trigger assessment will be incorporated when needed Supported scenarios Cloud OA will support the traditional centralized, and decentralized model. Additionally, it will support a new scenario where IDH’s can manage multiple OEM’s in a single OA solution Phase: Run (RTM Feb One click setup 2017) i. Cloud OA wizard enabled Phase: Walk for DOC roles (RTM Aug 2016) DOC integration i. Key ordering Phase: Crawl One click setup ii. Key returns i. Cloud OA wizard (RTM Feb 2016) ii. Automated DOC account DPC integration creation i. Licensing tools integrated Scalable platform DPC integration into data transfer i. Cloud architecture i. Automated data transfer DOC integration ii. Automated account ii. Solution natively coded in between Cloud OA & DPC* i. Programmatic account provisioning Azure ii. Single sign-on* creation iii. Low onboard & run cost iii. User permissions cross ii. Programmatic access platform* iii. OA3.0 roles integration Self-serve One click setup iv. Automated account creation* i. TPI request form i. Single registration form v. Cross platform user profiles* Self-serve integration ii. Simple account linking for vi. DOC compatible user profiles* i. Partner categorization ii. TPI activation flag multitenant users vii. Automated email notification* functionality integration iii. Automated creation of DIS Self-serve ii. Automated DPC account iii. Automated certificate entities i. Digitalize OA3.0 form ii. Single welcome email* creation transfer Cloud OA infrastructure iii. First time login password iii. Automated user/roles iv. Certificate swap i. Key fulfillment change* account creation automation ii. Key transfer iv. Cross system profile* iv. Click to accept forms v. Pop-ups notifications Links iii. Multitenant users v. Simple profile editing function v. Link to DPC partners* to documentation* iv. Inventory management vi. Demo video per function vi. Link to DPC event vi. Chat support* v. Report submission vii. Training videos available registration* vii. Pop-up support messages (CBR/OHR/PBR) viii. Click to accept forms vii. Demo video per new viii. Tip tool vi. Services entitlements (AFO) ix. Environment indication tool function ix. Support forum* vii. Other DIS 3.0 features x. New simple UI x. Live training links* xi. Support page link DIS 1.95 DIS3.X
DIS 2.0 DIS 3.0 Migration Utility
DIS 3.XX Migration DIS 1.8
IX
Cloud COA Delivered OA To Be Delivered OA3.0 Solution Comparison OEM expense type Customized (TVO’s) DIS 3.0 (On- DIS on Azure Cloud OA premise) (VM’s) Server hardware N/A $16,191 $0.00 $0.00
Windows Server Licensing N/A $6,165 $0.00 $0.00
SQL Server Licensing N/A $11,688 $0.00 $0.00
Total capital investment $4M-$10M** $34,044.00 $0.00 $0.00
OEM expense type Customized (TVO’s) DIS 3.0 (On- DIS on Azure Cloud OA premise) (VM’s) Data center space N/A $31.68 $0.00 $0.00
Energy costs N/A $264.75 $0.00 $0.00 Based on 500+ partners running Maintenance N/A $53.97 $0.00 $0.00 Cloud OA Partner IT costs N/A $715.38 $238.46 $119.23 Estimate +/- Azure run cost $0.00 $0.00 $569.08 $5.00 to $20.00 20% Total monthly cost (per $75k and above*** $1,065.78 $807.54 $124.23 to $139.23 partner) Run cost savings of over 1000%+ and no capital investment required Capability Customized DIS 3.0 DIS on Azure Cloud OA (TVO’s) (On-premise) (VM’s)
Integration with OEM ERP systems MSFT investment only & Scalable platform (user adoption & easy to add available soon features) Capability not available on Easy setup/onboarding (One click setup) premise OA3.0 run infrastructure Integration with DPC & Connector Partial integration with DOC Self-serve Offline run mode Cloud offers Dynamic pricing Bill on binding BI capability (R&A activation & reporting) Agility: Automatic software updates from MSFT to OEM
Cloud OA removes the capability gaps in the ecosystem at a low cost Microsoft OEM Portals Portal gate “Registration” Microsoft Operations
Resellers
Virtual Databa server se Cloud OA OEM
Matchmaking
IDH
DPC
ODM Thank You