So we have the ISO which contains all needed files to do a install. Sometimes they don't differ much from the different Editions right? Does that ISO simply contain some sort of configuration file that differs for each Edition? I see you can create ISOs with multiple editions, by that logic is there already simply multiple configuration files included in the ISO that normally go unused? Could we for example, take a LTSB "config file" and place it into a updated Feb 2016 ISO? Would the installer then try and install LTSB with the more recent Feb 2016 files? I know we can remove things from a (Pro etc) ISO to make it LTSB*ish*, but I'm wondering if there is another way to go about it. LTSB is appealing because of the lack of various components, the major downside is lack of bug fixes and such. I guess the core of this question is what makes a Pro edition installer Pro and what makes it Education etc.
LTSB receives all the bug fixes as needed just like all the other versions. What it does not get is feature updates as regularly as the others.
yes it receives all bug and security fixes, no features. You cannot do like Win7 and remove the ei.cfg to get all editions though. Those days are pretty much over.
You wouldn't get Enterprise though, while in win10 it's enough to have single language to get other 4 editions
For all those of us that missed the memo, can you please explain? Thanks again for all your contributions!
For the countries who have singlelanguage you can set-edition the basic index to (home), pro, education and enterprise (you have to collect all eula's from the licenses folder and insert it to every index). For other countries it starts from home > pro > edu > enterprise.
Excellent thank you for the information. So do you think it might be feasible to transplant the LTSB ("EnterpriseS"?) XML configs/package files into a 2016 ISO and have a successful install? Even if this is pointless, which is the vibe I am getting from some I am still curious if nothing else.