New
#1
Validation of OEM Win7/64 installed on new hard drive--have OLD one
I have a custom AMD-powered system that is about 18 months old (since OEM Win7 was installed on a new drive). The core WDC 2500KS HD slowed down and showed other errors which made the system unusable about 60 days ago. Best I can remember I never entered a product key when Win7 was originally installed and but the copy/system was validated according to MSFT (I could be wrong). I've kept up with updates and have SR-1 installed. Due to the problems with the system (30+ days ago), I purchased a larger WDC drive and reinstalled my OEM copy of Win7 onto it. Although I was again able to do this w/out a product key (don't have one with the OEM copy?), MSFT is now complaining that the system is NOT GENUINE and step one requires a product key (never provided to me?).
Today I used the Magic Jellybean program to obtain the Product & CD keys--validity currently unknown.
I also have the original hard drive running and accessible via USB? (also backed up separately).
What should I do in what order?
1. Can I /should I officially uninstall my copy of Win7 on the "remote/original drive" ?
SLMGR.vbs refers to remote "systems" not drives--AFAIK.
2. Is #1 possible?? and is it necessary or advised?
3. Should I simply proceed with validation and deal with the potential conflict(s) later?
4. Is MSFT still willing to speak with people on the phone about these things on their nickel?
I am aware of the excellent documentation available (referenced from this site) on SLMGR.vbs. I am also overwhelmed with the options it offers and their sheer complexity. I am an old computer programmer who is quite handy, but I rarely deal with MSFT licensing issues and much of the terminology in the help for SLMGR.vbs is foriegn to me.
I would be very grateful for feedback on my problem. I would like to get this system officially validated without spending money on purchasing another copy of Win 7 (which I view as unnessary).
Thanks in Advance