I don't understand, why do you ask for double confirmation? In the case of v1809, I've listed all the necessary updates for both possible cases(integrating .net 4.8 or not) based on the Updates Overview post.
MAS doesn't support IoTEnterpriseS SKU, only IoTEnterprise SKU AFAIK. Edit: I read the script on GitHub and it indeed doesn't have the required code to work on IoTEnterpriseS. But the support can probably be added.
The HWID for the IoT version is the same as for the normal version, it picks up the previously established hwid for normal enterprise.
Ok. But MAS will falsely report that the SKU doesn't support HWID activation. But I will add code to support it out of the box in my secret project.
Do you know if it supports adding an ime language at least? I'm curious about this version come the next LTSC release. I did an in-place "downgrade" on one of my machines from LTSC to regular Enterprise (202H), and I hate it - awaiting next LTSC release to do a fresh install.
If they both accept the exact same product keys, why did M$ even bother in the first place? Atleast IoT Enterprise had its own keys
@emet Ent and Ent LTSC are two editions with different life cycles. There's a reason it says they're chopping off Ent but continuing to support Ent LTSC. The L T S C part is what you're missing, even though you say yourself "i'm using Ent LTSC".