i had ever seen such straight short guide like that,you saved me a lot of time at least 80%........many thanks
Yup, I found that out recently with 8.1 Pro w/WMC. I needed to inject a non-OEM key into the .wim to get SetupComplete to run. You could always inject a non-OEM key into the wim to force it to initiate SetupComplete.cmd and then in the same cmd inject the key that you want to use for the install.
post #23 "You could always inject a non-OEM key into the wim to force it to initiate SetupComplete.cmd and then in the same cmd inject the key that you want to use for the install".......2 keys in the same script how to? or i had misunderstanding
sounds like good: i just already tried "unattended windows 7 install" first integrate all updates about 151 updates,IE 11,its updates,security updates for .net 3.5 using NTlite create silent installers for .net 4.5.2and its updates here is my setupcomplete.cmd: @echo off pushd %~dp0 start /wait %systemdrive%\Apps\NDP45-KB2979578-v2-x86_silent.exe start /wait %systemdrive%\Apps\NDP452-KB2901907-x86-x64-AllOS-ENU_silent.exe start /wait %systemdrive%\Apps\NDP45-KB2972107-x86_silent.exe start /wait %systemdrive%\Apps\NDP45-KB2972216-x86_silent.exe start /wait %systemdrive%\Apps\NDP45-KB2978128-x86_silent.exe start /wait %systemdrive%\Apps\NDP45-KB3023224-x86_silent.exe start /wait %systemdrive%\Apps\NDP45-KB3035490-x86_silent.exe start /wait %systemdrive%\Apps\NDP45-KB3037581-x86_silent.exe start /wait %systemdrive%\Apps\NDP45-KB3074230-x86_silent.exe start /wait %systemdrive%\Apps\NDP45-KB3074550-x86_silent.exe start /wait %systemdrive%\Apps\NDP45-KB3098781-x86_silent.exe start /wait %systemdrive%\Apps\NDP45-KB3122656-x86_silent.exe start /wait %systemdrive%\Apps\NDP45-KB3127229-x86_silent.exe ECHO. ECHO Deleting Temp Installation Files... RD /S /Q %systemdrive%\Apps del /q /f "%WINDIR%\Setup\Scripts\SetupComplete.cmd" EXIT put it in $oem$ $$ setup scripts folder"with OOBE.cmd all went smoothly my activation is ok exactly setupcomplete.cmd was running in"windows finalizing........."time now i'll preparing unattended windows 10 pro feedback latter thanks all
Wow, that's a big reroute to accomplish it The installation will take a while doing all that in setupcomplete phase. If you did it in audit mode the installation wouldn't take much longer than a clean msdn install. ps, dotnet461 is available.
that's right but audit mode confuse me in capture image"install.wim,size" further .net 4.5.2 very suitable for my needs
I mentioned that there was 461 available because when you used that (simply followed by "/quiet /norestart" in setupcomplete) you only have to do 2 or 4 updates instead of 10 for 452. @Iamthedude, what OEM key are you talking about? Is it an official key you own?
Sorry for the delay. I was referring to the situation where SetupComplete wouldn't run if an OEM key was present in the WIM. You mount the wim with the OEM key in and change it to something that isn't OEM to get SetupComplete to run. Then during SetupComplete you replace the key with one that you want to use. You could also just insert the key you want to use from the start. I was using a certain members AIO at the time with 8.1 Pro w/WMC which had a OEM present and SetupComplete wasn't running so had to change it.
That's what gVLK's are meant for. Your situation is a bit specific, aio releasers should also put in indexes without pre-installed keys so people with original (retail/oem non slp, payed for) keys also can use the aio
gVLK's! Knew it was a particular kind of key but couldn't for life of me remember when I was posting before That's what I had to insert into the wim to get SetupComplete to run on this particular Pro w/WMC index. I think it was an oversight on the releasers part for that particular release as I havn't come across it since. I remember asking in the MultiOEM thread about it as at the time i thought it was something to do with the script but turned out it was the key
Afaik there aren't any "oem" keys for 8.x prowmc (the multi-oem project also doesn't support 8.x Professional-WMC, only core and pro), 10 doesn't even have official prowmc versions anymore.