source

Windows 10 Anniversary Update
Customization, Deployment and
Manufacturing
Jessie Labayen
Principal Program Manager
Agenda
OEM Activation
Windows 10 Desktop
Manufacturing and Deployment
Plan
•
•
•
•
•
Try
Integrate/
Test
Deploy/
Pilot run
Full
production
• Mass
production
Deploy
in factory
test
environment
• or
Identify
which apps• and
drivers
to
• Create new process
integrate
What is new?
into existing processpreload
• Measure performance
What do I have to change?
Identify additional
Validate tools and •processes
in
•customizations
Validate tools/process in factory
What do I need to •prepare?
own environment • Understand impact ofenvironment
app and
Who will do the work?
process diagnostic tools in
• Manufacturing work driver
back installation on
• Validate
How do I integrate into
my existing process?
schedule
Windows
• Build sample image and
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
• May be a small order with option to change configuration
during the selling season
• May be a large order placed by a channel or enterprise
customer
Almost the same HW and SW through the entire run rate
Lower manufacturing cost
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
Lab
Offline injection of a desktop app
Improved image management
Reduces time to create a new image
Boot online or
to Audit mode, and
Install classic Windows app
Prepare
Reference
device
Windows
Base Image
Reference
Device
Classic
Windows app
ScanState.exe
Siloed Provisioning
Package (SPP)
New!
Repeat for 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
Free Space
OS + App
Partition
Other
Partitions
•
Recovery image for preinstalled
desktop apps (USMT.PPKG)
Apps
•
Preinstalled Desktop and Store
apps
Drivers
•
Drivers and applets/utilities
Windows
•
•
•
Windows binaries
System files
Language packs, Features-onDemand
Cumulative updates
Recovery
•
32-bit vs.
64-bit
dependent
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
Mount WIM.
Inject LPs/FODs.
Inject AppX packages.
Inject CUs.
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>
1.
2.
3.
4.
5.
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
Baseline
Compact OS applied
With single-instancing
Hiberfile Reduced
Hiberfile Off
32-Bit
11.68 GB
8.85 GB
7.66 GB
7.26 GB
6.8 GB
Change
-2.83 GB
-4.02 GB
-4.42 GB
-4.88 GB
64-Bit
17.24 GB
13.45 GB
12.28 GB
11.03 GB
8.03 GB
Change
-3.79 GB
-4.96 GB
-6.21 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/systembuilder-deployment-of-windows-10-for-desktop-editions
https://msdn.microsoft.com/en-us/windows/hardware/commercialize/manufacture/desktop/oemdeployment-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
Image
Creation
SMT
OS Flash
Device
Assembly and
Testing
Some items have dependencies on Silicon Vendors
Provisioning/
Security
Pack and QA
Sampling
https://msdn.microsoft.com/enus/windows/hardware/commercialize/manufacture/mobile/mobile-deployment-and-imaging
OEM Activation Tool
OEM Corporate
• Stores Product Key
Inventory
3
OEM Factory/TPI
End-Customer
• Insert Product Key into BIOS
• Online Use of Computer
• Calculate HW Hash for Each
Computer Manufactured
Per-device unique identifier verifiable
by Microsoft
• Adhere
Genuine Windows
2
4
1
OS Edition (e.g. Home, Pro)
Label
Factory Deliver
Ship
OEM identity Order Keys
Computers
Computer
Product Key
Buildprovides:
Rpt
•
•
Deliver &
Bill Event
Order
Keys
•
Hardware Hash provides:
1
•
Computer
Deliver
Mapping
of
Build
3 product key to HW components
2detected during manufacturing
Keys
Report
5
Windows
Activation
Request
Activation
6
Microsoft
3
Computer Build Report Data
Microsoft Operations
Data Repository
Windows Activation
Services
MICROSOFT CONFIDENTIAL – Provided Under NDA
<HardwareInventory>
<p n="ProcessorModel" v="Intel(R) Core(TM) i7-4600U CPU @
2.10GHz" />
<p n="TotalPhysicalRAM" v="8" />
<p n="PrimaryDiskType" v="SSD" />
<p n="PrimaryDiskTotalCapacity" v="256" />
<p n="InternalDiskCount" v="1" />
<p n="SmbiosUuid" v="ff239101-53ee-11cb-84db-84201d6edc06" />
<p n="MacAddress" v="00 15 5D 19 D3 0D" />
<p n="InternalPrimaryDisplaySizePhysicalH" v="310" />
<p n="InternalPrimaryDisplaySizePhysicalV" v="174" />
<p n="InternalPrimaryDisplayResolutionHorizontal" v=“1920" />
<p n="InternalPrimaryDisplayResolutionVertical" v="1080" />
<p n="OpticalDiskDriveType" v="No" />
<p n="DigitizerSupportID" v="Touch" />
<p n="GraphicsAdapterType" v="Undefined" />
<p n="PresentIntegratedVideoPort" v="Undefined" />
<p n="ChassisTypes" v="Notebook" />
<p n="CollectionOS" v="FullOS" />
</HardwareInventory>
Align reported information for higher quality and consistent reporting data
Reduce OHR requirements moving towards elimination of OHR
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
FRM_FACTOR_CL2
Enclosure or Chassis type 3
Update SMBIOS to v3.0.0 to add support for Tablet, Convertible and Detachable
Define the chassis type consistently in SMBIOS (Baseboard Product field?)
PC_MODEL_SKU
Product Name
Baseboard Information
Family
SKU Number
Standardize on a single SMBIOS field that uniquely identifies a device’s configuration
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
2017)
One click setup
i.
Phase: Walk
(RTM Aug 2016)
Phase: Crawl
(RTM Feb 2016)
Scalable platform
i.
ii.
iii.
Cloud architecture
Solution natively coded in
Azure
Low onboard & run cost
One click setup
i.
ii.
iii.
Single registration form
Simple account linking for
multitenant users
Automated creation of DIS
entities
Cloud OA infrastructure
i.
ii.
iii.
iv.
v.
vi.
vii.
Key fulfillment
Key transfer
Multitenant users
Inventory management
Report submission
(CBR/OHR/PBR)
Services entitlements (AFO)
Other DIS 3.0 features
One click setup
i.
ii.
DPC integration
i.
Automated data transfer
between Cloud OA & DPC*
ii.
Single sign-on*
iii. User permissions cross
platform*
iv. Automated account creation*
v.
Cross platform user profiles*
vi. DOC compatible user profiles*
vii. Automated email notification*
Self-serve
i.
ii.
iii.
Digitalize OA3.0 form
Single welcome email*
First time login password
change*
iv. Cross system profile*
v.
Simple profile editing function
vi. Demo video per function
vii. Training videos available
viii. Click to accept forms
ix. Environment indication tool
x.
New simple UI
xi. Support page link
Cloud OA wizard
Automated DOC account
creation
DOC integration
i.
ii.
iii.
Programmatic account
creation
Programmatic access
OA3.0 roles integration
Self-serve
i.
ii.
iii.
iv.
v.
vi.
vii.
Partner categorization
functionality
Automated DPC account
creation
Automated user/roles
account creation
Click to accept forms
Link to DPC partners*
Link to DPC event
registration*
Demo video per new
function
Cloud OA wizard enabled
for DOC roles
DOC integration
i.
ii.
Key ordering
Key returns
DPC integration
i.
ii.
Licensing tools integrated
into data transfer
Automated account
provisioning
Self-serve
i.
TPI request form
integration
ii.
TPI activation flag
integration
iii. Automated certificate
transfer
iv. Certificate swap
automation
v.
Pop-ups notifications Links
to documentation*
vi. Chat support*
vii. Pop-up support messages
viii. Tip tool
ix. Support forum*
x.
Live training links*
DIS 1.95
DIS3.X
DIS 3.0
DIS 2.0
Migration
Utility
DIS 3.XX
Migration
DIS 1.8
IX
COA
Delivered
To Be Delivered
Cloud
OA
OA3.0 Solution
Comparison
OEM expense type
Customized (TVO’s)
DIS 3.0 (Onpremise)
DIS on Azure
(VM’s)
Cloud OA
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
$4M-$10M**
$34,044.00
$0.00
$0.00
Customized (TVO’s)
DIS 3.0 (Onpremise)
DIS on Azure
(VM’s)
Cloud OA
Data center space
N/A
$31.68
$0.00
$0.00
Energy costs
N/A
$264.75
$0.00
$0.00
Maintenance
N/A
$53.97
$0.00
$0.00
Partner IT costs
N/A
$715.38
$238.46
$119.23
Azure run cost
$0.00
$0.00
$569.08
$5.00 to $20.00
$75k and above***
$1,065.78
$807.54
$124.23 to $139.23
Total capital investment
OEM expense type
Total monthly cost (per
partner)
Run cost savings of over 1000%+ and no capital investment required
Based on 500+
partners running
Cloud OA
Estimate +/20%
Capability
Integration with OEM ERP systems
Scalable platform (user adoption & easy to add
features)
Easy setup/onboarding (One click setup)
Customized
(TVO’s)
DIS 3.0
(On-premise)
DIS on Azure
(VM’s)
Cloud OA
MSFT investment only &
available soon
Capability not available on
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
server
Databa
se
Cloud OA
OEM
Matchmaking
IDH
DPC
ODM
Thank You