Is there a way to find updates specific to one's version, like LTSB? I was reading NTLite Guide and it mentioned that Cumulative Updates can break the OS if integrated into image. It makes sense because the latest Cumulative Update for LTSB includes registry entries meant for Store-related AppX's like MS Photo, Bing Weather, Xbox, etc, and LTSB is not meant to have those AppX's... I was also curious if languages take a lot of space and if it was possible to slim it down to En-US only??
No. For several reasons. Firstly because I do not want to have to worry about remembering to plug a USB stick if I have a DVD or copying xml to it I want to simply install Windows in the simplest and most automated way possible. Furthermore I always test ISO in a VM before installing on any machine so it eases quite a lot of things for my needs. But nobody is forced to do so. My intention was not to create a tutorial with all the possibilities I just posted the way that I believe to be more practical in my point of view and that gives less problems.
Now when I try to edit my Printer to share it through the network it says that it can't locate ImagingDevices.exe and closes itself so I cant change its settings... EDIT: I tried again and now I could access its settings so that I could share it through the network, which is weird. I don't know if it is working and the printer has a strange icon.
when i try integrate .net 3.5 rs2 the toolkit says there's nothing in the folder even though the file has been downloaded and extracted to the folder correctly
With the answer file I posted nothing from OOBE is shown to me in Win 10 LTSB 2016 x64. I have not used MachineOOBE and UserOOBE just because they are depreciated and I'm not sure if they would work fine or if in some circumstance or version of Windows they would stop working. Besides, I was not sure what they were doing. So is there any advantage or does it make any difference if I use MachineOOBE and UserOOBE? It looks like they were de-deprecated with Win10 ver 1703 And the <HideOEMRegistrationScreen> field does exactly what? I do not use it and no OOBE screen appears to me. ComputerName is also not required for Windows 10 (this does not appear in Windows SIM with Win10 Image) but I believe that in Windows 7 it is necessary.
As I said, WSIM says they're depreciated but they are not. They are "supposed" to be used for testing and development and Microsoft does not want people to use them, without knowing exactly what they do, and then be unable to proceed with the installation at the very end. I use them regularly, both in single USB autounattend installations on a single system, as well as on my deployment server in unattend universal installations. Let me load my LTSB 2016 into WSIM to see what you're talking about.
As I said, WSIM says they're depreciated but they are not. They are "supposed" to be used for testing and development and Microsoft does not want people to use them, without knowing exactly what they do, and then be unable to proceed with the installation at the very end. I use them regularly, both in single USB autounattend installations on a single system, as well as on my deployment server in unattend universal installations. Let me load my LTSB 2016 into WSIM to see what you're talking about. <HideOEMRegistrationScreen> allows you to hide the OOBE OEM registration screen, which is for systems that have OEM installation media. It registers the OEM system with the OEM installation. **EDIT** All options for OOBE - and everything else - are there for LTSB 2016 with the latest CU. You by no means have to use OOBE passes, but I'd say most people do when they add actual user accounts (local accounts, not domain) to the answer file and it's not an OEM installation image for a single specific computer.
The updates are the same for all editions of version 1607 (Pro, Enterprise, LTSB, Server, etc ...) at the time of installation only the components present in the image are updated. Since the update is cumulative it is not possible to separate component updates specific to LTSB. I integrated KB4019472 (CU of May) into LTSB without any problem. I integrated Servicing Stack KB4013418 first then Cumulative Update KB4019472. Yes Servicing Stack makes it easy to integrate other updates.
The recent CU has started changing the Image ServicePackBuild version and due to this it's not able to find the required file, I have added the fix for this issue in the upcoming version.
You need to extract the whole CU Cab to find out the update applicable for LTSB edition and then use the corresponding .mum file to install the update. the .mum file clearly specifics which update is applicable to which edition and it updates only based on this info. xniso was the who was doing these kind of manual updating, he knows it better.
Thanks @MSMG it was more or less what I imagined to work on x86/x64 (include components of both in xml) but would have to test yet to be sure. With this I come to the conclusion that the answer file is something very special each one prefers to use in a certain way, now I understand why it is difficult to see people sharing unattend.xml or autounattend.xml ready on the internet. The best thing to do is to study and understand how this works, do it yourself and then try to fit your own needs For example for ComputerName I would use a random name because my PC does not use any network resources. <ComputerName>*</ComputerName>