UNSOLVED Windows Key Default option
- FOG Version: 1.2.0 7797
- OS: Ubuntu 14.04
- Service Version:
- OS: Windows 8.1
I was wondering if there was a way to set a default Windows Product Key Kinda like we set the default AD creds. That way when I am registering a computer I could see a list and choose the id # of the proper windows Key. I know I am behind in versions a little so if this is a feature in 1.3.0 than I am sorry for wasting your time.
How I currently register a computer is load up through the network and perform a full inventory registration and then once the imaging begins I log into the web interface and copy the windows key from a prior computer to the new computer.
Thank you for your time and any and all Help you may be able to give me.
Wayne Workman last edited by Wayne Workman
What this thread is asking, I think, is a plugin for Key Management. I understand the desire - but here’s how I dealt with your problem.
I made sure during registration that I entered the correct host-name and assigned the correct image and told the system to join the domain, and made sure I picked to image it right then.
Then after I did a lab or a hallway or whatever a good stopping point is, I used the fog web interface and used Group Management to assign the right key to the systems I just imaged, along with snapins too.
https://forums.fogproject.org/category/11/feature-request is the place to start
@george1421 So I am guessing I need to submit this as a feature request some where, I am not sure where to do that. Should I click solved button just saying that it was submitted as a feature request for a later release.
@george1421 I agree with you and I am thinking your way would be better in the long run when we start to support multiple OS versions at the same time.
… so that when you are using the PXE boot and registering the host when the program asks if you want to set the product key that you would be able to enter ? to get the list of Product keys and then be able to choose one, instead of finding in your documentation and hand entering each time.
The only issue I can see with this is if FOG displayed a list of keys
W269N-WFGWX-YVC9B-4J6C9-T83GX MH37W-N47XK-V7XM9-C7227-GCQG9 NPPR9-FWDCX-D2C8J-H872K-2YT43 DPH2V-TTNVB-4X9Q3-TJR4H-KHJW4 NW6C2-QMPVW-D7KKK-3GKT6-VCFB2 2WH4N-8QGBV-H22JP-CT43Q-MDWWJ WNMTR-4C88C-JK8YV-HQ7T2-76DF9
How would you know which one was for
Windows 10 Enterprise LTSB 2015if that is what you are deploying? (Hint it is:
WNMTR-4C88C-JK8YV-HQ7T2-76DF9). Whereas if the key was associated with the image, you would know the image and the proper key to activate that image.
Understand this is all spec talk since that field or the code to activate it doesn’t exist in FOG 1.3.x. If its of value to you, you might want to submit a feature request.
I can say I do this via the sysprep file that contains the proper key when we sysprep the image. I personally don’t use the fog cleint to connect the target to AD either.
@george1421 This would be an ok method of doing this also. I had not thought of this.
I know both of those but what I was wondering if you could setup the MAK key in fog configuration like you do with AD settings, so that when you are using the PXE boot and registering the host when the program asks if you want to set the product key that you would be able to enter ? to get the list of Product keys and then be able to choose one, instead of finding in your documentation and hand entering each time.
@Wayne-Workman I was just looking to see if there was a default field for these keys.
It would be handy to have that license key field associated with the image. That way when the
deployment techselected a specific image the license key would be copied from the image to the host record at the start of imaging. I understand this would work for both mak and kms keys, but not OEM keys which are hardware specific. The group that would be left out is the users that use OEM keys to activate windows. But again OEM keys are do not have redistribution rights.
Wayne Workman last edited by
FOG + the new FOG Client can activate windows for you automatically. You can assign MAKs individually to hosts or via groups.