Notes On Microsoft Course For Windows IoT
Notes On Microsoft Course For Windows IoT
Notes On Microsoft Course For Windows IoT
Introduction
- OneCore.lib
Embedded Mode
- full version of Windows 10 with lockdown capabilities powering a long range of industry devices
across retail, manufacturing, health, government and other industries
When to use?
- does not contain Edge but contains IE11, Cortana, but basic apps are included, Outlook, Clock etc
- Windows Product Key is injected or installed into each device during manufacturing
Internet Activation
- normal process, AVS server, an activation failurile will be showed, invalid activation marker (UX),
3 hours after the machine is online, until reboot and again after 3 hours, no automatic reboot as in
evaluation mode, no forced activation, no loss of features
3 states to activation:
- just ARM
- mobile POS, Industry Hand-Held Terminal (HHT)
- Chassis flexibility
- Screen size limit: 8 inches
1. Controlled Update
2. Unlimited self signed LoB apps running on the device (signature)
3. Enables Embedded Mode
- can use volume licenses and inject the license file to convert the device to IoT enteprise and get
Embedded mode
- OEMs can preload a license file into an image and then IoT features are enabled from startup,
custom UI layout
Activation
UWP Apps
- with display (headed), without displays (headless), controlled by configuration read at boot-
time
- custom OEM shell for UI
- OMA/DM
- MDM
- CSP
- MDM in Windows 10 – Enrollment,
- Field Medic
WSUS (Windows Service Updates Service) vs WUfB (Windows Update for Business) – on LTSB
Edition specific
Enteprise
- My OEM (WSUS, Intune, System Center, 3rd party MDM) and Windows Updates
- New Devices (SOC)
- 10 year life cycle
- security updates
- no frequent feature updates
- LTS roll-up every 2-3 years
- move from one LTSB to another using in-place upgrade, can skin an LTSB
- manage update via WSUS
- you can move from LTSB to CBB
7. Connectivity
Provisioning
Features on demand v2