Master beauty all cool what you did there in these comparisons. cool, but here is a comparison in codes, but here after you do it, you have to identify the serials of these two editions right at boot how to do this done the xml to bar with the condition? Here, I made an example but it's not right, and just so you can see how I want it to appear in the xml to identify one of the two cores or both echo <SkuItem editionid="CoreSingleLanguage" /> echo <SkuItem editionid="CoreConnectedSingleLanguage " /> I did some tests here with aio I made an ei.cfg, it passes but after I do the setupcomplete with these two editions, they do not activate, so stop that and only with these serials even in the response file Code: [Channel] OEM [VL] 0 Code: :IntKey1 echo <SkuItem editionid="CoreSingleLanguage" /> echo. ^<UserData^> echo. ^<AcceptEula^>true^</AcceptEula^> echo. ^<ProductKey^> echo. ^<Key^>%~1^</Key^> echo. ^<WillShowUI^>OnError^</WillShowUI^> echo. ^</ProductKey^> echo. ^</UserData^> echo. ^</component^> echo. ^</settings^> echo.^</unattend^> goto :eof :IntKey2 echo. ^<UserData^> echo. ^<AcceptEula^>true^</AcceptEula^> echo. ^</UserData^> echo. ^</component^> echo. ^</settings^> echo.^</unattend^> goto :eof
here it is, I'll have to put OEM if it's 1 image, or an oem aio if there are two editions, if I put it as a volume, and I'm going to install, the CoreConnectedSingleLanguage, it will ask for the serial, and that's why the autounnatended, have to have this comparison code to make only the core of the two editions if that's the case, otherwise proceed without serial and also with ei,cfg, it will also require this here here you have to have already done the xml, to block the other editions so as not to get the serial, is there a way for the boot to recognize editions? Code: :IntKey1 echo. ^<UserData^> echo. ^<AcceptEula^>true^</AcceptEula^> echo. ^<ProductKey^> echo .^<SkuItem editionid="CoreSingleLanguage"^ > echo. ^<Key^>%~1^</Key^> echo .^<SkuItem editionid="CoreConnectedSingleLanguage"^ > echo. ^<Key^>%~1^</Key^> echo. ^<WillShowUI^>OnError^</WillShowUI^> echo. ^</ProductKey^> echo. ^</UserData^> echo. ^</component^> echo. ^</settings^> echo.^</unattend^> goto :eof :IntKey2 echo. ^<UserData^> echo. ^<AcceptEula^>true^</AcceptEula^> echo. ^</UserData^> echo. ^</component^> echo. ^</settings^> echo.^</unattend^> goto :eof
Look, I did it like ei.cfg volume, passed the serial, ok, but see that it even pulls the setupcomplete, to the setup\script folder, but it's not active, I even did it with an original image es-ES, that's why I have to go with the serial
Tai master with the serial, it activates, so you have to put it in the answer file, and use setupcomplete, then delete the folder, then I did it with an image just the coreconnectedsinglelanguage, if I put the coresinglelanguage together, and put the two serials, the edition will not know which one is yours so there has to be a condition