For people who do not feel comfortable with command line there are two very good tools: Dism Mount Service (DMS) This is a GUI for DISM: http://reboot.pro/files/file/576-dism-mount-service/ wimlib-clc, This is a GUI for wimlib-imagex: http://reboot.pro/files/file/485-wimlib-clc-beta/
Code: rem call :OSPP @abbodi1406 Concerning KMS_VL_ALL-SppExtComObjPatcher-kms-19, if i don't want to test the Windows activation and only want to activate Office 2016 on my Windows 10 system, do you think these modifications to the KMS_VL_ALL.cmd script are ok : Change (statement at line 162) if %office% equ 1 (call :offchk15&exit /b) else (if %gvlk% equ 1 exit /b) to if %office% equ 1 (call :offchk15&exit /b) else (exit /b) and comment (statement 83) Code: rem call :OSPP Thank you.
Once KMS_VL_ALL DID AFFECT my windows 10 retail license. Now, before executing the script, I check the Windows activation status, just in case.
Yes, but activation was lost after a reboot. To correct the issue i changed the key to ...-3V66T after several attempt. But, as i said, this happend only once.
hi @abbodi1406 in w10ui you said ""# Enable .NET Framework 3.5 if available source detected locations to be checked: mounted iso, inserted dvd/usb, sxs folder for distribution target"" what does it mean? i want to install updates to extracted iso folder and want to enable .net 3.5.. how am i suppose to enable .net 3.5 ?? do i need to put somewhere .net 3.5 file mentioned in your 1st post? thank you..
MSMG Toolkit 8.0 supports integration of MS Edge onto LTSB and AFAIK, it is the only script that will also update it. Once OS is installed with Edge, any CU installed will prevent Edge from running because LTSB is not supposed to have Edge. I think MSMG Toolkit uses some hack to update Edge on LTSB. If I integrate Edge using MSMG Toolkit and update the image offline using W10UI, will W10UI be able to update Edge just like MSMG Toolkit? What about onlive/live updating of LTSB with Edge using W10UI?
Yes, MSMG applies a registry fix when integrating Edge into LTSB/Server 2016. The part of integrating updates does not change in LTSB with Edge integrated since the fix is applied before.
I didn't quite understand... Are you saying that once Edge is integrated into LTSB via MSMG Toolkit, updating the resulting image on a live/online install should NOT break Edge functionality?