Hi 冕 张 Your plan to use Volume Licensing for standard Windows Enterprise LTSC to provision bare-metal PCs for resale is not legally compliant. Microsoft defines Volume Licensing strictly as an upgrade. This requires the hardware to already possess a qualifying base license, such as Windows Pro, injected directly into the motherboard's ACPI MSDM tables at the factory. Using Key Management Service or Multiple Activation Keys as the primary license on new devices violates the Microsoft OEM Code of Conduct. If you execute the slmgr.vbs /dlv script via the command prompt, the resulting output will distinctly identify the licensing channel; utilizing a volume activation channel for initial retail distribution is explicitly prohibited. The only compliant route for preinstalling an operating system on new devices for sale is through the OEM licensing channel.
Historically, standard Windows 10 Enterprise LTSC 2019 was strictly a Commercial Volume Licensing product and was never available as an OEM SKU. Its authorized OEM equivalent was Windows 10 IoT Enterprise LTSC 2019. This structural division remains active today. For Windows 10 LTSC 2021 and all Windows 11 LTSC releases, Windows IoT Enterprise LTSC is the sole legally compliant option available through authorized OEM distributors for device builders.
Standard Enterprise LTSC and IoT Enterprise share the same core codebase but differ significantly in legal terms, lifecycles, and embedded capabilities. The IoT Enterprise End User License Agreement limits its use to fixed-function, specialized devices, prohibiting general-purpose computing. Furthermore, standard Enterprise LTSC now carries a five-year support lifecycle, whereas IoT Enterprise LTSC retains a full ten-year lifecycle. Technically, IoT editions include robust lockdown capabilities like the Unified Write Filter to protect the physical storage from unauthorized changes. Systems engineers typically configure these hardware restrictions by modifying the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Embedded\UWF registry key or by executing the C:\Windows\System32\uwfmgr.exe command-line utility to intercept and redirect disk writes to a virtual overlay.
Domic