I have noticed an odd issue with a new Windows 10 ENT LTSB build that I have been trying to streamline via NTLite.
Using a clean VL ISO from Microsoft - I load this into NT Lite and make some minor settings changes, a few REG tweaks (NO removal of any apps or features) and then I am integrating the latest CU (KB4346877). NTLite does everything correctly - including creating an ISO. Looks like everything is good.
However once I do a deployment to a VM (via MDT Build 8450) - the build number of the Windows version (Settings->System-About) still reads OS Build 14393.0 instead of OS Build 14393.2396 (which it should be after the application of this CU).
Not only does it look like this install is the very first release "build" of the OS - but I am now doubting whether or not the CU was actually integrated correctly or not.
Do I need to be worried about the CU integration? Anyone else notice the same?
Sonic.
Using a clean VL ISO from Microsoft - I load this into NT Lite and make some minor settings changes, a few REG tweaks (NO removal of any apps or features) and then I am integrating the latest CU (KB4346877). NTLite does everything correctly - including creating an ISO. Looks like everything is good.
However once I do a deployment to a VM (via MDT Build 8450) - the build number of the Windows version (Settings->System-About) still reads OS Build 14393.0 instead of OS Build 14393.2396 (which it should be after the application of this CU).
Not only does it look like this install is the very first release "build" of the OS - but I am now doubting whether or not the CU was actually integrated correctly or not.
Do I need to be worried about the CU integration? Anyone else notice the same?
Sonic.