Remotely Update Windows Product Keys
-
Yep.
-
My guess is that there might be a way to do that with PowerShell.
-
I did find this on technet. Gotta do some testing.
-
We did some testing and this script does work on Windows 7 Professional.
-
Just curious to what end you want to make this change?
-
For VL rights.
-
DISM can do this I think
-
-
We're using fog as our imaging platform. It's just so simple and well tuned. We'll be updating our images to incorporate the key and will be good to go for the foreseeable future.
-
@DustinB3403 said:
For VL rights.
For VL rights you need to use your VLK and volume media (and not OEM or retail) as well, you can't legally use the OEM install converted to an MAK key.
-
@Jason They are the OEM keys or images
-
@DustinB3403 said:
@Jason They are the OEM keys or images
You can't use OEM Keys in images legally either.
-
That's why our images are sysprep'd and OOBE'd
-
@DustinB3403 said:
That's why our images are sysprep'd and OOBE'd
Doesn't make a difference it's still imaging, and what your are doing is against the EULA. To image computers you must use the Volume Licence Media to make the image and use the Volume Key. There's no other way for a company to do it without special system builder agreements with Microsoft.
-
Time out here - Why would you want to change per-existing keys in machines already rolled out? What difference would it make?
Sure, going forward you're going to roll out new images using VLK based images that will have the KMS key preinstalled (you have to do nothing, they are part of the media you download from MS, and the auto register with a KMS server you setup).
So I'm back to my original question, what's the point in changing keys on machines that are already deployed?
-
nevermind....
Jason you're clearly not understanding what we are going to, vs what was had.
-
This post is deleted! -
Ok jason, you're right. I haven't the slightest idea. None.
Have a good day.
I'll have to go suck my thumb..
