Skip to main content

Change Windows 7 Product Key

After imaging a Windows 7 machine so as to clone to multiple others I came across a slight hassle: how to change the product key on the newly cloned PC?


Previously under XP I would have used a key changer tool such as WinKeyFinder but I had thought that the "Change Product Key" option in System Properties would do the trick in Windows 7.


Unfortunately the "Change Product Key" link wasn't showing in System Properties.  Perhaps this is because this was an OEM version of Windows 7?  I'm not sure.  But here's how to do it:

  1. Open a Command Prompt
  2. Type "slmgr.vbs -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx" where the xxxxx characters are your product key.
  3. Give it a minute and you should get a message saying that the product key has been updated.
  4. Then type "slmgr.vbs -ato" to active Windows with this new product key.
  5. You should then get a message saying that Windows has been successfully activate.
Hope this helps.

Comments

Unknown said…
This comment has been removed by a blog administrator.
Unknown said…
I have seen your blog and read your content i think it's fantastic and i need for us to getting for knowledge.

Useful link- Linksys Router Setup
Unknown said…
Thank you for sharing your blog. And i also recommend a site to you, hope to help you.www.vanskeys.com

Popular posts from this blog

Resolve WSUS Server issue that gives "Cannot save configuration because the server is still processing"

This is a pretty infuriating error and can sometimes crop up as a result of running a "wsusutil reset" command. First of all, give the server some time, and then a bit more...  but you've probably already done this. These steps may help to resolve the situation: - Install Microsoft SQL Management Studio (free download) - Run SQL Management Studio and start to connect to the WSUS database - Enter this in the "Server Name" box:  \\.\pipe\MICROSOFT##WID\tsql\query - Expand the "Databases" tree - Right-click on "SUSDB" and choose "New Query" - Paste this query in:     UPDATE tbSingletonData     SET ResetStateMachineNeeded = 0 - You should see a message like "1 row affected", which is good - Quit SQL Management Studio - Open "Services" and restart the "WSUS Service" - Now, open WSUS

Convert Ruckus AP from Unleashed to ZoneDirector-managed

Here is the method to convert a Ruckus Unleashed AP to one which can be managed by a Ruckus ZoneDirector controller: - Login to https://support.ruckuswireless.com/ - Click "Downloads" - Choose the correct product, e.g. Ruckus R550 - Choose a "standalone" version along the lines of 118.2.0.0.875.bl7 or something similar - Agree to terms and download the software - Connect to the AP's IP address - It should open the setup wizard, showing "Unleashed Installation" - Click "Local Upgrade" - Choose the firmware image file you just downloaded - It will upload, process, and then be ready for upgrade when you click "Yes" - After this, the ZD should detect the new AP - The new AP will then need to be approved - The new AP will then be upgraded to the correct software by the ZD - The new AP will then reboot and should be ready to use - Don't forget that, for the ZD to even detect, let alone manage the new AP, it must have enough licenses

Logon Scripts in Group Policy not running

Problem  Was having difficulty with a logon script I had created and was deploying to users via Group Policy. The script was to customise printer settings for certain users. But it just wasn't running when the users would logon to their PCs. The GPO was applying properly, and I could run the script manually without issue. Cause It turns out that it was happening because, by default, logon scripts don't run for 5 mins after logon occurs on a Windows client PC. Solution This can be adjusted by setting the "Configure Logon Script Delay policy" to "Enabled" and then configuring a better delay. Note: if this policy is set to disabled or not configured, the default delay of 5 mins will apply. I initially set this delay to "0" but found that wasn't successful.  Perhaps the script needed a small delay. So I set it to "1" (1 minute) and it worked nicely. I must also note that during the troubleshooting process, I read many recommendations to e...