1. I have my own lightweight and configured *.wim Server 2019, I am constantly finishing it, fixing bugs and deploying again Now I am changing the edition of Server 2019 to LTSC after deployment, with the replacement of Branding and System32\spp\tokens and entering slmgr.vbs /rilc and the license key Tell me what I need to do for this change of Server 2019 to LTSC immediately in win, before deployment? This operation is part of the Reconstruction topic, so I am asking the question to the masters here. Understanding the script 25398.1_Neutral_to_Client_amd64_38in1_26100_License I realized that System32\spp\tokens\skus\ is also copied What other key points of the script are necessary to accomplish my task? 2. I am studying the topic, many want to get Starter versions. I suppose it is because of sporting interest? It is cut down in functionality and hardware requirements. What is the beauty of Starter, maybe I don’t know something? Thanks.
Who do you think you are idiot. If i were the moderator you are the number one to ban from here to get this forum healthy as it should be. Probably they try to get along well with you because you get this topic trend topic. But they are false beacuse you get this topic to full garbage as much as you can. Probably you are z tennager full of free spare time to full here. You are not owner of the topic. Let people to share a frelly and do not full the topic with your garbage.
I must say that I do not agree with you - xinso is a true master You must be able to read between the lines to be able to fully grasp what he is saying. I believe he is a very mature person because of the way he expresses himself quite unlike you as you demonstrated above. Because of your level - I don't believe the Moderators or Microsoft would like if everything is spelled out in detail for every tom, dick and harry to make isos
I want to add 24H2 LTSC edition to 24H2 Enterprise edition install.wim without removing Enterprise edition. I am succeded mostly but i have update problem. What i have tried until now are below. The difference package list is below. Code: Microsoft-Onecore-Identity-TenantRestrictions-Package-amd64-10.0.26100.1-tr-TR.cab Microsoft-Onecore-Identity-TenantRestrictions-Package-amd64-10.0.26100.1.cab Microsoft-Onecore-Identity-TenantRestrictions-WOW64-Package-amd64-10.0.26100.1-tr-TR.cab Microsoft-Onecore-Identity-TenantRestrictions-WOW64-Package-amd64-10.0.26100.1.cab Microsoft-Windows-Branding-EnterpriseS-Package-amd64-10.0.26100.1.cab Microsoft-Windows-Editions-EnterpriseS-Package-amd64-10.0.26100.1-tr-TR.cab Microsoft-Windows-Editions-EnterpriseS-Package-amd64-10.0.26100.1.cab ********** Microsoft-Windows-EditionSpecific-EnterpriseS-Package-amd64-10.0.26100.1-tr-TR.cab Microsoft-Windows-EditionSpecific-EnterpriseS-Package-amd64-10.0.26100.1.cab Microsoft-Windows-EditionSpecific-EnterpriseS-removable-Package-amd64-10.0.26100.1-tr-TR.cab Microsoft-Windows-EditionSpecific-EnterpriseS-removable-Package-amd64-10.0.26100.1.cab Microsoft-Windows-EditionSpecific-EnterpriseS-WOW64-Package-amd64-10.0.26100.1-tr-TR.cab Microsoft-Windows-EditionSpecific-EnterpriseS-WOW64-Package-amd64-10.0.26100.1.cab Microsoft-Windows-EditionSpecific-EnterpriseS-WOW64-removable-Package-amd64-10.0.26100.1-tr-TR.cab Microsoft-Windows-EditionSpecific-EnterpriseS-WOW64-removable-Package-amd64-10.0.26100.1.cab Microsoft-Windows-EnterpriseS-SPP-Components-Package-amd64-10.0.26100.1.cab Microsoft-Windows-Licenses-EnterpriseS-Package-amd64-10.0.26100.1-tr-TR.cab Microsoft-Windows-Licenses-EnterpriseS-Package-amd64-10.0.26100.1.cab Microsoft-Windows-Licenses-IoTEnterpriseS-Package-amd64-10.0.26100.1-tr-TR.cab Microsoft-Windows-Licenses-IoTEnterpriseS-Package-amd64-10.0.26100.1.cab Microsoft-Windows-Licenses-IoTEnterpriseSK-Package-amd64-10.0.26100.1-tr-TR.cab Microsoft-Windows-Licenses-IoTEnterpriseSK-Package-amd64-10.0.26100.1.cab ********** Microsoft-Windows-Management-SecureAssessment-Package-amd64-10.0.26100.1-tr-TR.cab Microsoft-Windows-Management-SecureAssessment-Package-amd64-10.0.26100.1.cab Microsoft-Windows-Management-SecureAssessment-WOW64-Package-amd64-10.0.26100.1-tr-TR.cab Microsoft-Windows-Management-SecureAssessment-WOW64-Package-amd64-10.0.26100.1.cab Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Default-Package-amd64-10.0.26100.1.cab Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-License-Package-amd64-10.0.26100.1.cab Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Package-amd64-10.0.26100.1.cab Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseS-License-Package-amd64-10.0.26100.1.cab Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseSK-License-Package-amd64-10.0.26100.1.cab Microsoft-Windows-Shell32-OEMDefaultAssociations-Legacy-Package-amd64-10.0.26100.1-tr-TR.cab Microsoft-Windows-Shell32-OEMDefaultAssociations-Legacy-Package-amd64-10.0.26100.1.cab I extracted theese packages from original iso with SxSv1. Packages that has ********** asterix right side gives error at etraction process. They says "vbscript.vbs could not find the path" something like that. Inspite of SxSv1 gives error it succesfully creates the packages. Also packages can successfully integrated with dism without errors. The problem is that after integration if i check install.wim structure i see that fallowing files in folders are missing Windows\servicing\Packages folder Microsoft-Windows-Editions-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.26100.1.cat Microsoft-Windows-Editions-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.26100.1.mum \Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} Microsoft-Windows-Editions-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.26100.1.cat Maybe the packages that could not be found by SxSv1 are theese files. Anyway. I also tried to integrate theese files by 1.xml method. Dism says successfull but related files are not copied to that folders again. I manually copied the files to that folders because dism gives error that it can not find the files. The problem is not only the missing files also at registry there is EnterpriseS editioning and license and product key missing so dism /image:xx /gettargeteditions gives error. I can successfully fix that error by manual registry editing. I compare both editions with all registry until there is not any difference. Created intsall.wim installs and works ok with everything but when i try to integrate this install.wim updates offline or online it says component store is corrupted. /restore health not helps.
I succesfully combined 24H2 Enterprise LTSC on 24H2 Enterprise install.wim. All packages of all editions inside the wim. All operations made by dism succesfully. As dism and microsoft does not want that, i arranged install.wim as it feel itself 24H2 Enterprise LTSC. And the result wim is unupdatable. So i believe it is imposibble to update when there is two edition group same time inside install.wim. I have seen some editions that has all editions inside an install.wim at chineese sites. Probaby galliums modifications. If they works as expected and updatable i do not know. Could not download that wims. So i wanted to remove one of the two editions and keep only one edition. Started from zero again. I tried to remove 24H2 Enterprise edition from clean 24H2 Enterprise edition install.wim. As i understand dism complains install.wim can not be editionless and gives error. But i have seen here people change editions of install.wim. !!! I faked dism think there is no editions at 24H2 Enterprise edition install.wim. Added 24H2 Enterprise LTSC package. Removed 24H2 Enterprise package. This works but resulting wim again unupdatable. Maybe i need a editionless uupdump install.wim so i can add any edition i want but i do not know how to get it.
@xinso always reminds me at @heldigard the Broom Boy™ (always deleting his posts after due time). Love both .
script, common to all architectures. Just differ in packages. The problem is: My 26100 scripts are using 76 full install.wim in 38 languages. And the install.wim is customized for specific purpose. To share? Too big. To elaborate? Too complicated.