Greetings for everyone. I an new here and i have one question. Is it possible to create windows 7 x86 x64 all in one ( all editions x86 and x64 ) with Multi-OEM pre-activation?
Yes, but there are different methods of creating multi-arch iso's, MRP isn't architecture dependent. My favorite: You can create the x86 and x64 iso separately and use the multi-arch script by @abbodi1406 (it's in his UUP>ISO and ESD>ISO project folders). When you select option 1, it will create the x86/x64 iso with 1 multi-arch install.wim, put the MRP ready made $OEM$ folder in "ISO:\Sources" and it will run
All @abbodi1406 has to offer: https://forums.mydigitallife.net/threads/abbodi1406s-batch-scripts-repo.74197/#post-1343297
i used tool uup-converter-wimlib-23, and official msdn images windows 7 x86 and x64. i created all in one iso by your instructions, and after that i put $oem$ folder into sources folder by Ultra iso. Then i saved ISO and i made bootable usb drive. I made a test on hp dc 7900 sff brand pc. System installed normaly , i got HP wallpaper but system is not activated. 30 days until activation. p.s i used multi arch script
Correct me if I'm wrong. I can use Windows10x32.iso and Windows10x64 and create a multi arc Windows10.ISO? I don't need to get the ESDs? Thank You.
I understand that creating windows 7 all in one and windows 10 all in one is the same. I used just multi arch script and later ultra iso for adding OEM folder.
If you could post the 'Project.log' file that would help work out why the HP did not activate. The log is found on the the C: drive. HP/Compaq has always been a awkward brand because there are so many variants. It could be a Vista SLIC (v2.0) instead of v2.1 which would not be able to activate Win7. I have a HP Compaq dc7800p SFF which only has a Vista 2.0 SLIC that i use for testing. Thanks
Should not EnterpriseS/SN have special exception to show Long Term Branch? Code: ================================================[ Operating System Info ]================================================ Installation Type : Client {Non Server} Version {SKU} : Windows 10 Enterprise S {LTSC} {125} Edition {Registry} : EnterpriseS {125} Edition {CBS} : EnterpriseS Edition {Composition} : EnterpriseS Architecture : 32 Bit {via AR:4} Build/Update Revision : 17763 {rs5_release} / 194 Release Identifier : 1809 Branch Readiness Level : Semi-Annual Channel [Targeted] {16 Dec / 0x10h} {Ref:U3}
[SCKV7] HP [#08] v2.0 'Vista 6.1 Kernel' SLIC found, it cannot activate Windows 7 {6.1 Kernel}. [NOKCA] Note: OEM SLP Key/Certificate routines will not be processed. Reason: Vista v2.0 SLIC Detected. reason why it not activate No valid v2.1 slic detected.
I too thought that , but i can only show what it has detected, i would of thought for LTSC/Enterprise it be 0x20h (32 Dec) I check 4 places - even: HKLM\Software\Microsoft\PolicyManager\default\Update\BranchReadinessLevel\Value -- which is the default value for that 'Level' set by M$.
IF your system had a valid slic 2.1 then it would of activated, however as your HP system has a 2.0 (vista) one, it will NOT auto-activate windows 7 via MRP. But for any other pc that has a valid slic for win 7 it should auto activate those ok.