Ligthing control with windows 10 iot

Windows 10 IoT Core Services

Windows 10 IoT Core Services is a new cloud services subscription that provides the essential services needed to commercialize a device on Windows 10 IoT Core. Through this subscription, OEMs have access to long term support on Windows 10 IoT Core Long Term Servicing Channel (LTSC) releases along with services to publish device updates and assess device health.

What’s included with Windows 10 IoT Core Services?

A subscription to Windows 10 IoT Core Services comes with three main benefits:

Benefit	Description
Long Term Support	Access to Windows 10 IoT Core LTSC releases with security and reliability updates only (no new features).
Update control with Device Update Center	Create and publish device updates at scale using cloud-side controls.
Device Health Attestation (DHA)	Rights to commercialize a device with DHA to affirm device health remotely.

Long Term Support

OEMs get long term support on Windows 10 IoT Core via access to monthly updates from the Windows Long-Term Servicing Channel (LTSC) releases. This includes security and reliability updates for the operating system to keep device security up to date. Devices using LTSC releases won’t receive feature updates, enabling OEMs to focus updates on stability by minimizing changes to the base operating system.

Update Control with Device Update Center

Update control with the newly announced Device Update Center (DUC) provides the ability to create, customize, and publish device updates. These updates are distributed by the same content distribution network (CDN) as Windows Update which is used daily by millions of Windows customers around the world. Updates can be applied to the operating system and device drivers as well as OEM-specific applications and files. Updates can be flighted to test devices prior to broader distribution.

Here’s a diagram of the update flow in Device Update Center:

Commercialize with Device Health Attestation

Device Health Attestation (DHA) enables enterprises and OEMs to raise the security bar of their organization’s assets with hardware-attested security. Evaluating the trustworthiness of a device at boot time is essential for a trusted IoT system. However, a device cannot attest to its own trustworthiness — this must be done by an external entity such as the DHA cloud service. This service evaluates device health and can be combined with a device management system, such as Azure IoT Device Management. Based on DHA report data, the device management system can take corrective actions such as re-imaging the device, denying network access, or creating a service ticket.

Is this for me?

If you work with IoT devices, you might be wondering if Windows 10 IoT Core Services is right for you or your organization. The answer depends on how you use and obtain Windows 10 IoT devices. The following information will help you decide whether this subscription service is right for you.

1. If you are creating a device and you control the update and maintenance of the full software image on the device, this service is for you. If you only install apps on the device and someone else updates the full software image, such as the operating system and drivers, this service isn’t for you. If you’re not sure, contact your supplier and ask if they maintain the operating system, drivers, and other parts of the system image on the device or whether you are expected to maintain the system image. This service is designed for the party that maintains the system image for the device which is typically the ODM or OEM of the device, not the end customer purchasing or using the device.
2. Your devices should be running Windows 10 IoT Core. If they are running Windows 10 IoT Enterprise, another version of Windows, or another operating system, this service isn’t for you. Services such as Azure IoT Device Management and Microsoft Intune offer cross-platform support which may be useful ingredients in configuring alternate solutions for those operating systems.
3. If you want to build a device with the Long Term Servicing Channel (LTSC) releases of Windows 10 IoT Core, this service is for you. You must subscribe to Windows 10 IoT Core Services to commercialize a device with an LTSC release of Windows 10 IoT Core. If you only want to run Semi-Annual Channel releases of Windows 10 IoT Core, you aren’t required to subscribe to this service.
4. If you want to use any one of the three services included in Windows 10 IoT Core Services on your devices, this service is for you. Even if you only need one of the three services included in the subscription, you need to purchase the subscription for your devices. The services are only sold together as a single product — they are not available for purchase separately.

Getting started

Windows 10 IoT Core Services is available through Azure, Cloud Solutions Provider, and OEM channels. If you already meet the prerequisites below and are familiar with creating resources in Azure, you can skip straight to the Windows 10 IoT Core Services page on Azure.com and the Create blade in the Azure Portal to get started. For more details on these steps, keep reading below.

Prerequisites

1. Create or use an existing Azure Active Directory domain for registering with Windows Hardware Dev Center. You will need to sign in with an account with administrator rights to your AAD tenant domain to sign legal agreements during the registration process.
2. You must have an Extended Validation (EV) code signing certificate. Please check whether your company already has an EV code signing certificate. If your company already has an EV code signing certificate, have the certificate available during the registration process. If your company doesn’t have a certificate, you will need to purchase a certificate from an authorized partner as part of the registration process.
3. Register for a Windows Hardware Dev Center account to get access to Device Update Center. Make sure you sign in as an administrator with the Azure Active Directory domain you will use for Device Update Center and have your Extended Validation (EV) code signing certificate available.

Creating a new resource

After you’ve completed the prerequisites above, follow these steps when you are ready to create a resource for Windows 10 IoT Core Services with your Azure subscription.

1. Log into the Azure Portal with the AAD account you will use for purchasing the resource.
2. In the navigation pane on the left, click on Create a resource.
3. In the Search box, search for «IoT» and select «Windows 10 IoT Core Services» from the list.
4. Review in the information on the overview blade for Windows 10 IoT Core Services, including the Prerequisites information. When you’re ready, click the Create button at the bottom of the overview blade.
5. On the Create blade, fill out the fields in the form. These fields can also be edited later in the resource properties.
   • Name: This is a friendly name for this instance of the Windows 10 IoT Core Services resource. This name is only used in the Azure Portal. Pick something that will help you distinguish this resource instance from others you might add to your Azure subscription. For example, consider a name that describes this group of devices such as «Industrial Extraction Monitor Device — Preproduction».
   • Quantity: Specify the number of devices to use with this resource. If you need to add more devices later, you can increase the quantity of devices using this resource or you can create a separate resource to track the additional devices. The minimum quantity is 10. If you have more than 500,000 devices, create separate resource instances with at most 500,000 devices per instance.
   • Billing AAD domain name: This corresponds to the Azure Active Directory domain name associated with the organization that is purchasing this resource. This field is automatically populated with the AAD domain of the user currently logged into the Azure Portal.
   • Admin AAD domain name: This corresponds to the Azure Active Directory domain name associated with the organization that logs into Device Update Center to publish updates for the system image for the device. By default (or if left blank), this field is populated with the AAD domain of the user currently logged into the Azure Portal. However, it can be changed to a different AAD domain, if needed.
   • Notes: This is a free-form text field to attach your own custom notes to this resource instance. This optional field is only used in the Azure Portal to help you organize your resources.
   • Subscription: Specify the Azure subscription to use for purchasing this resource. For more details on which subscriptions are available in your account, see the Subscriptions section of the Azure Portal in the navigation pane on the left.
   • Resource group: Specify the Resource Group to use for organizing this resource. All resources in Azure are organized into Resource Groups. You can use an existing group or create a new resource group when creating this resource.
6. After filling out the fields above, click the Create button at the bottom of the form. This will start the deployment process to add a new instance of the Windows 10 IoT Core Services resource to your Azure subscription.
7. After the resource is successfully deployed, you can find it on the Dashboard or All Resources section of the Azure Portal. If the deployment fails, check the error message for details. Also verify that you’ve completed the Prerequisites above and specified the correct Admin AAD domain name for logging into Windows Hardware Dev Center.

Updating a resource

After you’ve created a resource for Windows 10 IoT Core Services, you can update the resource by editing its properties in the Azure Portal.

1. Log into the Azure Portal with the AAD account you used when creating the resource.
2. Find the instance of the resource you want to change by selecting it in the Dashboard or All Resources section of the navigation pane in the Azure Portal.
3. On the Overview page of the resource properties, click the Edit button.
4. Change the fields as needed and then click Save.

Deleting a resource

When you no longer need the resource for Windows 10 IoT Core Services, you can delete the resource from your Azure subscription in the Azure Portal.

1. Log into the Azure Portal with the AAD account you used when creating the resource.
2. Find the instance of the resource you want to delete by selecting it in the Dashboard or All Resources section of the navigation pane in the Azure Portal.
3. On the Overview page of the resource properties, click the Delete button.

Using Device Update Center

As a device manufacturer, you can maintain the security and reliability of your device by regularly updating the device image. This is accomplished by using Device Update Center to create and publish updates specific to your device model which will be offered by Windows Update when the device scans for applicable updates.

1. Before creating updates, start by creating a baseline image which is applied to the device during manufacturing as described in the Build Your Image section of the Windows IoT Core docs.
2. It’s critical that you correctly populate the SMBIOS fields of your device and that your build environment is set up with the same corresponding values.
3. Ensure that you’ve registered for a Windows Hardware Dev Center account to get access to Device Update Center. Make sure you sign in as an administrator with the Azure Active Directory domain you will use for Device Update Center and have your Extended Validation (EV) code signing certificate available.
4. Log into Device Update Center using the same AAD account you used when registering with Windows Hardware Dev Center. The AAD domain name on this account should also match the Admin AAD domain name specified when creating the resource in the Azure Portal.
5. Follow the instructions in the Device Update Center User Guide to create and publish updates for your device.

Источник

Общие сведения о Windows 10 IoT An overview of Windows 10 IoT

Контейнеры Windows для коммерческого развертывания поддерживаются в Windows Server, Windows IoT Server, Windows IoT Корпоративная и Windows IoT Базовая. Windows Containers are supported for commercial deployments on Windows Server, Windows IoT Server, Windows IoT Enterprise and Windows IoT Core. Начиная с обновления Windows 2018 за октябрь (сборка 17763), контейнеры Windows можно использовать только с Windows Корпоративная и Профессиональная для разработки и тестирования. As of Windows October Update 2018 (Build 17763), Windows Containers can only be used with Windows Enterprise and Professional for dev/test purposes.

Что представляет собой Windows 10 IoT What is Windows 10 IoT?

Windows 10 IoT — это продукт семейства Windows 10, обеспечивающий производительность, безопасность и управляемость корпоративного уровня для Интернета вещей. Windows 10 IoT is a member of the Windows 10 family that brings enterprise-class power, security, and manageability to the Internet of Things. В ней используются процессы, экосистема и облачные подключения платформы Windows, что позволяет организациям создавать системы Интернета вещей с защищенными устройствами, которые можно быстро подготавливать, легко контролировать и без проблем подключать к общей облачной системе. It leverages Windows’ embedded experience, ecosystem and cloud connectivity, allowing organizations to create their Internet of Things with secure devices that can be quickly provisioned, easily managed, and seamlessly connected to an overall cloud strategy.

Выпуски Windows 10 IoT Windows 10 IoT Editions

Система Windows 10 IoT предоставляется в двух выпусках. Windows 10 IoT comes in two editions. Windows 10 IoT Базовая — это младший продукт в линейке операционных систем Windows 10. Windows 10 IoT Core is the smallest member of the Windows 10 operating system family. Она умеет выполнять только одно приложение, но обеспечивает полную управляемость и безопасность, характерные для Windows 10. While only running a single app, it still has the manageability and security expected from Windows 10. В отличие от нее, Windows 10 IoT Корпоративная является полной версией Windows 10 с множеством функций для создания специализированных устройств со строго заданным набором приложений и периферийных устройств. By contrast, Windows 10 IoT Enterprise is a full version of Windows 10 with specialized features to create dedicated devices locked down to a specific set of applications and peripherals.

Различия между Windows 10 IoT Базовая и Windows 10 IoT Корпоративная Differences between Windows 10 IoT Core and Windows 10 IoT Enterprise

Хотя Windows 10 IoT Базовая и Windows 10 IoT Корпоративная имеют сходные названия, их возможности и уровни поддержки существенно различаются. While Windows 10 IoT Core and Windows 10 IoT Enterprise are similar in name, there are differences in what they offer as well as what they support. Ниже приведен список функций, подчеркивающих различия между этими выпусками. Below is a feature list that highlights edition differences.

Компонент / Выпуск Feature / Edition	Windows 10 IoT Базовая Windows 10 IoT Core	Windows 10 IoT Корпоративная Windows 10 IoT Enterprise
Возможности для пользователя User experience	Одно активное приложение UWP одновременно (работа с фоновым стеком описана в документации по IoT оболочки) с поддержкой фоновых приложений и служб. One UWP app in the foreground at a time (see IoT Shell documentation for app backstack handling) with supporting background apps and services.	Традиционная оболочка Windows с расширенными функциями блокировки Traditional Windows Shell with Advanced Lockdown Features
Поддерживается работа без монитора Headless supported	Да Yes	Да Yes
Поддерживаемая архитектура приложений App architecture supported	Только пользовательский интерфейс универсальной платформы Windows UWP UI only	Полная поддержка пользовательского интерфейса Windows (например, UWP, WinForms, и т. д.) Full Windows UI support (e.g. UWP, WinForms, etc)
Кортана Cortana	Пакет SDK для Кортаны Cortana SDK	Да Yes
Присоединение к домену Domain join	Только AAD AAD only	AAD и традиционный домен AAD and Traditional Domain
Управление Management	MDM MDM	MDM MDM
Технологии безопасности устройств Device Security Technologies	Доверенный платформенный модуль, Secure Boot, BitLocker, Device Guard и аттестация работоспособности устройств TPM, Secure Boot, BitLocker, Device Guard, and Device Health Attestation	Доверенный платформенный модуль, Secure Boot, BitLocker, Device Guard и аттестация работоспособности устройств TPM, Secure Boot, BitLocker, Device Guard and Device Health Attestation
Поддержка архитектуры ARM CPU Architecture support	x86, x64 и ARM x86, x64, and ARM	x86 и x64 x86 and x64
Лицензирование Licensing	Лицензионное соглашение для Интернета и соглашения для встроенных OEM систем, без отчислений Online Licensing Agreement and Embedded OEM Agreements, Royalty-free	Прямые и косвенные соглашения для встроенных OEM систем Direct and Indirect Embedded OEM Agreements
Сценарии использования Usage scenarios	Цифровые подписи, интеллектуальные здания, шлюз Интернета вещей, компьютерный интерфейс, умный дом, носимая электроника Digital Signage, Smart Building, IoT Gateway, HMI, Smart Home, Wearables	Промышленные планшеты, точки продаж, киоски, цифровые вывески, банкоматы, медицинские устройства, производственное оборудование, тонкий клиент Industry Tablets, Retail Point of Service, Kiosk, Digital Signage, ATM, Medical Devices, Manufacturing Devices, Thin Client

Сведения о минимальных требованиях см. на сайте оборудования для Windows. For minimum requirement details, please visit the Windows Hardware site.

Если вы хотите узнать больше о точках продаж, посетите раздел документации UWP по этой теме. If you’re interested in learning more about Point of Service, please visit the UWP docs on this topic.

Различия между Windows 10 Desktop и Windows 10 IoT Базовая Differences between Windows 10 Desktop and Windows 10 IoT Core

Различия в доступности функций в версиях Windows Desktop и IoT Базовая Different features available on Desktop and IoT Core

• Папка «Входящие» для Кортаны теперь недоступна в Windows 10 IoT Базовая, начиная с версии 1809 (17763). Inbox Cortana is no longer available on Windows 10 IoT Core since version 1809 (17763). Если вам нужно быстро вывести на рынок устройства с поддержкой голосового взаимодействия, вы можете интегрировать поддержку Кортаны в устройства с помощью предварительной версии пакета SDK для устройств с Кортаной. If you are looking to bring a voice-enabled device to market quickly, you can integrate Cortana support into the device using the preview of the Cortana Devices SDK.
• API FileOpenPicker не поддерживается в Windows 10 IoT Базовая. The FileOpenPicker API is not supported in Windows 10 IoT Core. Чтобы обращаться к локальным дискам или съемным носителям, эту функцию нужно реализовать в самом приложении. To access local drives or removable storage, you can implement this in your own application.
• Устройство под управлением Windows 10 IoT Базовая будет загружать приложение по умолчанию, а не интерфейс настольного компьютера. The Windows 10 IoT Core device will boot to the default app instead of a desktop-like PC. Это приложение не только предоставляет удобную оболочку для взаимодействия после загрузки, но и позволяет использовать для приложения открытый код, чтобы вы могли применять эти функции для установки и запуска собственных пользовательских приложений с автоматической настройкой. The purpose of this application is not only to provide you with a friendly shell to interact with upon first boot, but to also allow you to use the open-sourced code for this application so that you can use these features to plug and play your own custom application(s).

Различия в поддержке драйверов Differences in driver-supported areas

• Windows 10 Desktop поддерживает большее количество драйверов, чем Windows 10 IoT Базовая. Windows 10 Desktop has more supported drivers than Windows 10 IoT Core. Чтобы те же устройства работали в Windows 10 IoT Базовая, может потребоваться компиляция драйвера из исходного кода для конкретного устройства Windows 10 IoT Базовая или другой обходной путь, особенно при работе с архитектурой ARM. To make the same device(s) work on Windows 10 IoT Core as on Desktop, you may need to build a driver from source for a Windows 10 IoT Core device or find another workaround, especially for ARM architecture.
• Для libusb в Windows 10 IoT Базовая (ARM) не существует стандартного драйвера. Вам потребуется скомпилировать его из исходного кода для использования в архитектуре ARM. There is no out-of-the-box driver for libusb for Windows 10 IoT Core (ARM) — you will need to build from source to target the ARM architecture.

Различия в наборе доступных реестров Differences in available registry set

• На рабочем столе есть параметр «Автоматически скрыть полосы прокрутки в Windows», который вы можете отключить. On desktop, there is an option to «Automatically hide scroll bars in Windows» that can be set to off. Он управляется следующим значением реестра: It is controlled by the following registry entry:

• Этот раздел реестра по умолчанию не существует на устройствах с Windows 10 IoT Базовая. There is no such registry on Windows 10 IoT Core devices by default. Если вам нужен раздел реестра Dynamic Scrollbars, его придется добавить самостоятельно. You will need to add a «Dynamic Scrollbars» register if you want.
• Чтобы автоматически скрывать полосы прокрутки в приложении универсальной платформы Windows, добавьте раздел DynamicScrollbars и присвойте ему значение 1, как показано ниже: To enable hide scroll bars automatically in a UWP application, you can add the «DynamicScrollbars» register and set the value to «1» like this:

• Этот раздел реестра нужно настраивать из учетной записи по умолчанию. The registry key must be set from the Default Account. Если параметр ScrollViewer XAML имеет значение Visible, значение 0 в параметре реестра приведет к отображению полосы прокрутки независимо от того, требуется ли для содержимого отображение полос прокрутки в пользовательском интерфейсе. If the ScrollViewer’s XAML setting is «Visible», the registry setting of 0 will force the scroll bar to appear regardless of whether there is sufficient content to have the scroll appear in the UI. Значение 1 в параметре реестра сохраняет полосу прокрутки скрытой, пока отсутствует содержимое достаточного объема. A registry setting of 1 will keep the scroll bar hidden until there is sufficient content.

• Наконец, если параметр ScrollViewer XAML имеет значение Auto, при значении 0 для параметра реестра полная полоса прокрутки будет отображаться только при наличии содержимого достаточного объема. Lastly, if the ScrollViewer XAML’s setting is «Auto» then the registry setting of 0 will only show the full scroll bar when there is enough content to display the scroll bar. Если параметр реестра имеет значение 1, полоса прокрутки будет отображаться при наличии содержимого или скрываться при отсутствии содержимого. When the registry setting is 1, the scroll bar will appear then when there is enough content or hidden if there is no content.

Поддержка разных команд Different commands supported

• Команда PowerShell Remove-AppxPackage работает в версии Desktop, но не работает в Windows 10 IoT Базовая. The PowerShell Remove-AppxPackage command works on Desktop but not on Windows 10 IoT Core.
• Универсальным приложениям Windows доступны не все папки на устройстве. Not all folders on your device are accessible by Universal Windows Apps. В Windows 10 IoT Базовая вы можете использовать средство FolderPermissions, чтобы предоставить приложениям UWP доступ к папке. On Windows 10 IoT Core, you can use the FolderPermissions tool to make a folder accessible to a UWP app. Например, запустите команду FolderPermissions c:\test -e, чтобы предоставить приложениям универсальной платформы Windows доступ к папке c:\test. For example, run FolderPermissions c:\test -e to give UWP apps access to c:\test folder. В версии Desktop так сделать нельзя. However, this is not available on Desktop.

Упомянутые в этой публикации команды могут со временем измениться, поскольку Windows 10 IoT Базовая совершенствуется. Commands shown in this post may change as time goes on since Windows 10 IoT Core keeps updating.

Поддержка IoT Edge в Windows 10 IoT IoT Edge Support for Windows 10 IoT

Чтобы узнать больше о поддержке IoT Edge в Windows 10 IoT, изучите раздел об операционных системах из этой статьи об Azure IoT Edge. To learn more about IoT Edge support for Windows 10 IoT, please read more about «Operating Systems» in the Azure IoT Edge article here.

Источник