Thanks. Actually, changing the machine name is another issue. Although windows offers a UI to do that, apparently it does not actually change the network name, which involves hacking the registry. I think there is another forum article about that somewhere.
If using redeploy on the paid version of Macrium Reflect, do not enter the license code on the original installation of Win 7 until after you have made an image of the installation. Then, just enter the individual license codes after "restoring" to the subsequent PCs.
Windows installations are ties to the MOBO serial number so you either have to use a new license on each new installation or, deactivate the license on the old PC then reactivate it on the new PC (assuming the license is retail). If you only have an OEM license and you are moving from a dead PC to a new one or a dead MOBO to a new MOBO on the same PC, you will need to call MS and beg, grovel, whatever to allow the transfer (you may need to call more than once to get a sympathetic operator).
I have transplanted win 7 pro system disks from one laptop to another of same hardware (but presumably different mobo s/n) without any complaint about licensing. However, I am not sure of the exact licensing of the OS; may even have been OEM. I suspect MS allows you some number of such changes before they will force you to call, despite what their official policy might be.
You could try OODiskImage, it has few functions under Tools>Change Computer Properties. You can point it at a resored image, before booting into the restored version.
There is a giveaway of 11 pro
registration
Registrieren Sie sich hier kostenlose Vollversion von OO DiskImage 11
Download Archive
Thanks! That is really stressing my German fluency. However, they end up sending a link to the German locale version. Do you know offhand if the license codes will work with the English locale version you posted a link to? Yeah, I know... try it. But, do you know the answer before I do all that?
--p.
It probably is illegal unless you can get an MS phone representative to agree to it.
The licensing is described here and you appear to be using the OEM:SLP which uses a license embedded in the BIOS SLIC table.
https://www.mydigitallife.net/differ...-product-keys/
Last edited by mjf; 15 Sep 2017 at 20:03. Reason: typo
Reading that page, seems to me that in my case it was probably a OEM:NONSLP, or OEM:COA since the COA stickers attached to the machines were Vista licenses, as confirmed by talking to a MS agent. The win 7 OS was acquired later, possibly oem, possibly retail. Since I'm an individual, not working for a corporation, I can't consult a lawyer before moving a disk from one computer to another. (...and not dozens of computers.) If MS's own license validation does not complain, I assume they do not object.
BTW, I would hesitate to call something that violates MS's license to be "illegal." It would definitely be a contract (eula) violation, but whether it breaks a law is more subtle.
Quote