[EditionID] [Channel] Retail [VL] 1 Does anyone know if setting the EI.CG like the above will allow you to choose any edition and still skip asking for a key?
Yep, it works (verified) I used it like this for a OEM, as it still shows OEM EULA this way and on the other side you can choose the edition you like Code: [EditionID] [Channel] OEM [VL] 0
Im making the iso now to test in vmware, Hope your right. If it does work Do you know of a similar way to make Vista stop asking for a key and still let you choose edition?
I allready have a way of installing my product key. Im just trying to skip that one step. Can I inject a fake/trial key to just skip the step?
Are the keys injected into the product ini of the wim. I would like to figure out how to enter the key to the wims without the DISM tool if possible, as I have the wims mounted anyway for additional mods... Is this what the DISM does or were does it place the serial key....do you know??? I am less than proficient with these tech...
Apparently DISM does some voodoo and uses a command line to install the key. I just did it and it doesnt ask me for a key so its integrated into the wim file. Im testing it again to see if it doesnt matter what key you give it. (Doesnt matter to me as i got my own vb.net app i made that lists my keys and i can click what one to install.
You can always create an answer file that will enter the key for you. This way at least you'll still have the original untouched image to work from if you wanna make another custom DVD for someone else. The trouble with using DISM to slipstream the key and/or the cert is that you can't really extract them for future reference without installing the whole thing, either on a host machine or in a virtual environment. I guess either way works perfectly well. I'm sure that modifying the original image is what the OEM's have done for their own custom recovery disks. The answer file method is most likely used by IT pro's because the original images can be reused in future scenarios and a custom installation made only by editing the answer file.
can we remove the word 'Retail or Oem' from the ei.cfg then again i dont suppose it will change anything will it
OEM/Retail wont really matter. Id use a answer file but i cant set a answer file for each edition id only want it to affect the key part not the entire process.
I just use a batch file, the key is installed by time the OS boots up, I just want to not see the enter your key prompt while installing. I also do not want the DISM thingy. It isnt difficult, I just want to know how it does it..
i did compare the mounted install before and after adding the key with DISM, I see files got changed, but can not find any references to used product key, so it looks like it is encrypted inside the WIM file
Same here. Ended up using a CMD in the Setup\Scripts folder to auto-install Cert&PK because i got no answer either when i asked where DISM puts the key. But this would still be good to know. So if anyone knows exactly where the key goes, please tell. After all, altering or adding a file on/to an USB Stick would certainly be a thousand times faster than this ridiculous indexing, cataloging, unpacking and repacking of the entire darn image...
Im 99% sure it embedds it into the install.wim and from there the install.wim skips the step thats all and auto inserts it.
Duh! off course it does it is install.wim that's been mounted isn't? File added/changes in install.wim after the key has been inserted: Code: Users\Default\NTUSER.DAT Users\Default\NTUSER.DAT.LOG1 Windows\System32\config\COMPONENTS Windows\System32\config\COMPONENTS.LOG1 Windows\System32\config\DEFAULT Windows\System32\config\DEFAULT.LOG1 Windows\System32\config\DEFAULT{016888b5-6c6f-11de-8d1d-001e0bcde3ec}.TM.blf Windows\System32\config\DEFAULT{016888b5-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000001.regtrans-ms Windows\System32\config\DEFAULT{016888b5-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000002.regtrans-ms Windows\System32\config\SAM Windows\System32\config\SAM.LOG1 Windows\System32\config\SAM{016888c1-6c6f-11de-8d1d-001e0bcde3ec}.TM.blf Windows\System32\config\SAM{016888c1-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000001.regtrans-ms Windows\System32\config\SAM{016888c1-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000002.regtrans-ms Windows\System32\config\SECURITY Windows\System32\config\SECURITY.LOG1 Windows\System32\config\SECURITY{016888c5-6c6f-11de-8d1d-001e0bcde3ec}.TM.blf Windows\System32\config\SECURITY{016888c5-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000001.regtrans-ms Windows\System32\config\SECURITY{016888c5-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000002.regtrans-ms Windows\System32\config\SOFTWARE Windows\System32\config\SOFTWARE.LOG1 Windows\System32\config\SOFTWARE{016888c9-6c6f-11de-8d1d-001e0bcde3ec}.TM.blf Windows\System32\config\SOFTWARE{016888c9-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000001.regtrans-ms Windows\System32\config\SOFTWARE{016888c9-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000002.regtrans-ms Windows\System32\config\SYSTEM Windows\System32\config\SYSTEM.LOG1 Windows\System32\config\SYSTEM{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TM.blf Windows\System32\config\SYSTEM{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000001.regtrans-ms Windows\System32\config\SYSTEM{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000002.regtrans-ms Windows\System32\SMI\Store\Machine\SCHEMA.DAT Windows\System32\SMI\Store\Machine\schema.dat.LOG Windows\System32\SMI\Store\Machine\SCHEMA.DAT.LOG1 I searched all above entries for the product Key inserted, nothing found
Right I know that but what im saying is the install.wim has to contain a embedded settings file that is modified on the actuall install.wim not its content. Kind of the same way it is able to hold seperate versions of it and contain there name. There has to be a settings file i dont think it is just a container. Dism probally hex's it into the actual file some way.
mmm, nah I don't think so lets assume it uses your theory, why should you have to mount the install.wim image before you are able to insert the key?
you mount the install.wim because in order to edit the install.wim dism sees the invisible settings file just like the boot.wim sees it as well. Also It would ensure it is applied to the correct image in the wim file.