@pugs1501 said in Windows Key Default option:
… 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 2015
if 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.