mesmer

And keep in mind, that the OEM key from the sticker may be a "one-time only" key - as in using it, the activation will be bound to the hardware it is used on (I am mostly using SystemBuilder Variants(*1) for my system (as I build 'em myself or buy 'em without OS) and there thats not a problem (in short: I simply lack the Win7 OEM experience)), but as far as my knowledge has grown on the subject a vital change in hardware may or may not be activatable via phone or strictly license termin speaking may simply be rejected - so I see a reason to the "why someone will stick to autoactivation as long as possible", because then the OEM key could def. be used on changed hardware (if it is the first time this key is used - so why waste it on the OEM Hardware where its not needed) with just using the online activation. I am really not sure on this one, the MS specific sides (technet, etc.) are AFAIK strict on this one-time bound between key and hardware, other sides claim that an activation via phone is still possible.
 
P.S.: with Win8 this whole OEM/Preactivation Discussion is Void - the new scheme where the "to be activated" key for OEM Systems is kept in the BIOS is a total different matter
 
*1: Ok, from a German Point of view and an old Sentence about the resale of OEM licenses, MS SB variants where (AFAIK) the result of that verdict (as a different model to pure OEM license (like from Dell or such);  SB (OEM) license is nowadays what is nearly 100% of the time sold to the customer here in germany (and I know only a few (real minority) shops who are actually offering the real retail)... And I am not sure what that means for reactivation on different hardware or such, but according to magazines like the C't (not talking Win8+ here) SB licenses under our law should be reactivatable under new hardware (but that may well be just an urban legend).

In addition, and as a final remark on my behalf (it is time to get back to my real studies, though it was fun and reminded me to the time of 2005 where I was one of the minorities who bought xp x64 and where often forced to get used to modify .msi's with Orca) - I tried it again with the (official technet) sysprep way... the reason why WinToolkit recognized my first preped image as being corrupt was that I have chosen a custom name for the image.... still now, and after I've named it right, and though simply building a .iso via WT from the syspreped .wim worked like a charm (the get-package information afterwards was the same as for a real sp1 install-media), it failed when I tried to integrate IE11 and its prerequisites. That doesn't worked out well - WT integrated fine, the install resulted in failures which may well be searched in this forum for the early times of IE11 and its integration. So i am not sure if I missed some KB or if it ain't be possible to use WT on a syspreped .wim (which makes no sense IMHO, so my guess would still be a fault in my procedures - and that one may include that I where using a WinPE.iso handed over to the VM that where build with the current ADK release for Win8+; I used that because it is much easier to apply the dism commands (/capture-image) to build the .wim then using the old variant with imageX). 
 
As said, I still think that it is possible (else all technet sysprep how to build an oem/multilingual media, how to deploy sp1, etc. descriptions wouldn't make sense; At least for the sysprep way).  In the meantime where the vm(s) where occupied with their install I checked the MD5 sums of the KB976902 files with their corresponding parts of KB976932 (SP1) and there where no differences to be found (haven't checked all of the files), so it should - in theory be possible - to get along that way to a working (and future proof) image... But as the OPs question (OEM based Win 7) and my curiosity about Dreamsparks PreSP1 Server 2008 R2 .img are just a minority in cases that may be neglected in the development of WT (or the Foolproof assignments/modules therein (which in my experiences make up 3/4 the time in the development of a GUI based project)) I just give up with trying any further (and will continue with my real work/study again    ). 

Integrating SP1 require manual method and some steps
 
if you can handle those steps, then i can provide you with tutorial

With Windows 7 you provide the key after Windows Installation if you need. Just make sure to select the right version the key is for.

You're beyond my knowledge level now, I know just enough to be dangerous, so hopefully someone else will offer you more information.  Good luck.
 
NOTE:  You'll probably need to know exactly what the differences are between the OEM and a "standard" install disc so you will be able to tell someone else what exactly you need to move over.
 
Cheers and Regards

Download an ISO via Win Toolkit then following the following link:
 
https://www.sctxca.org/suncity/clubs-groups/sites/computer/sigs/win7/articles/Win7_Retail-to-OEM.htm
 
In the sources folder open ei.cfg with notepad
 
 
Change retail to OEM: I'm pretty sure you can just delete the ei.cfg either way
 
You made need to change 'Ultimate' to 'HomeBasic', 'HomePremium' or whatever version you have.

..creo que con sysprep lo puedes hacer...en eso que te ayude rick ...o alguien con experiencia en sysprep

..pues utiliza tu licencia en la nueva iso y ya...

por que no te descargas la iso oficial con el SP1 ya integrado? ...es mejor y recomendable que estar integrando el sp1:
 
Links Oficiales de Microsoft - Descarga Directa y Alta Velocidad!:
 
Windows 7 Home Premium x86 SP1-U Español
Nombre: X17-58857.iso
Tamaño: 2.32 GB
MD5: 1C945414B78DC4552C75C3A9A25972EF
 
Windows 7 Home Premium x64 SP1-U Español
Nombre: X17-58859.iso
Tamaño: 3.02 GB
MD5: 31E02907D82851C9870D5B5BF40ABFB2
 
...para desbloquear las demas opciones mira aqui:
 
Saludos!
http://www.wincert.net/forum/topic/11986-desbloquea-todas-las-versiones-de-windows-7-sp1-de-3264-bits-autom%C3%A1ticamente/

Don't try.  Instead download an ISO with SP1 already integrated.  See here.  Use that as the source for your builds.
 
Cheers and Regards

Y sources\setup.exe (puedes eliminar el setup.exe de la raíz)
Si no incluyes a el setup.exe en \sources te dará un error durante instalación
http://www.msfn.org/board/topic/147213-what-folders-can-safetly-deleted-from-windows-7-dvd/#entry943854

Los unicos que necesitas en el DVD son
\boot
\efi
bootmgr
bootmgr.efi
\sources\boot.wim, install.wim, setup.exe

Yes, I hadn't ​​any additional software integration, only updates. In section ISO MAKER (Wintoolkit) I activated the option Rebuild image and 4.87 Gb is the final iso size.
 
I didn't delete anything from the original Vista SP2 DVD. I only added sp2 updates pack

Estos son los LP individuales
http://www.microsoft.com/en-us/download/details.aspx?id=2104
Use estos enlaces para descargar el mas reciente IE9 para Vista
Vista enu:
x86: http://go.microsoft.com/fwlink/?LinkId=198935
x64: http://go.microsoft.com/fwlink/?LinkId=198934

We can also vLite - describe the moment in time.

Don't use WinToolkit then.
See this topic: http://www.wincert.net/forum/topic/1468-batch-files-for-integrating-vista-updates-and-hotfixes/

WinToolkit in Vista sometimes causes problems. Unfortunately, I do not know why and I do not know the solution.
 
 

Doesn't matter, updates are language neutral (except language pack of course).