Closed jeffreyzarend closed 4 years ago
The above is from running slmgr /ato manually
Contents of logs in \program files\cloudbase\cloud-init\log directory
Hello,
can you set set_kms_product_key=True in the cloudbase-init.conf and try again?
Hello,
can you set set_kms_product_key=True in the cloudbase-init.conf and try again?
I have created a patch which should fix the issue: https://review.opendev.org/#/c/732497/ . Let me know if this fixes your problem. I can provide you a new installer if you needed to test the fix.
Thank you, Adrian Vladu
please, I would like the new installer to test the fix. thank you Jeff Zarend
To give some context on this issue: we usually create images with a valid product key (being it a KMS or a MAK) and this situation never appears. In your case, it seems you created the images by manually pressing next during the product key input step in the image creation process. Let me know if my assumptions are correct so that I can rule out other possible issues.
hmmm, i dont recall seeing the product key input step. you are correct that when i run cloud-init installer, i just do press "next", "next", "next" and take all the defaults.
we have always relied on our KMS to respond and license during the first boot. I create generic templates with no product keys in them currently.
I have built a cloudbase-init installer with the patch using the Github actions. You can find the zipped msi for download at the Artifacts button for this Github actions run: https://github.com/ader1990/cloudbase-init-installer-1/runs/730217531?check_suite_focus=true . You need to be logged in to see it.
ty i shall try this
fyi, it will be several days before I have an answer for you. working from home means I have very slow upload times. thank you
fyi, it will be several days before I have an answer for you. working from home means I have very slow upload times. thank you
Sure, no problem. Will wait for your response before merging.
Good morning/afternoon I tried the private build on a windows 2016 VM and it licensed. This change looks good.
thank you very much
Glad to hear that, I will keep you posted when the patch goes upstream.
again, thank you very very much
Hello @jeffreyzarend ,
The change has been merged: https://github.com/cloudbase/cloudbase-init/commit/1582ebec2c6fe1f6d0c2fc83adfbb36dbcd550d2 and the latest installer contains it. Can you please close the issue, if everything works?
Thank you.
Thank you VERY much. Jeff
ill download it and give it as try as soon as possible. probably within next 7 days
Is the fix in the stable branch or the beta branch? it looks like the stable branch is still 1_1_1?
Is the fix in the stable branch or the beta branch? it looks like the stable branch is still 1_1_1?
The fix is currently in the beta installer: https://www.cloudbase.it/downloads/CloudbaseInitSetup_x64.msi
ty. will test it today
Tested with the beta installer and windows licensed fine. C:\Program Files\Cloudbase Solutions\Cloudbase-Init\log>findstr /i version * cloudbase-init-unattend.log:2020-06-13 05:39:52.316 1460 INFO cloudbaseinit.init [-] Cloudbase-Init version: 1.1.2.dev5 cloudbase-init.log:2020-06-13 05:41:22.666 2884 INFO cloudbaseinit.init [-] Cloudbase-Init version: 1.1.2.dev5
C:\Program Files\Cloudbase Solutions\Cloudbase-Init\log>findstr /i license * cloudbase-init.log:2020-06-13 05:41:47.634 2884 INFO cloudbaseinit.plugins.windows.licensing [-] Microsoft Windows license info: cloudbase-init.log:License Status: Licensed
C:\Program Files\Cloudbase Solutions\Cloudbase-Init\log>
Closing issue, and eagerly awaiting fix to merge from beta to upstream.
thank you very much
Hello.
When creating Windows 2012, Windows 2012R2, Windows 2016, Windows 2019 image templates using cloudbase cloud-init, they do not license correctly when configured to obtain licenses from IBM's KMS servers.
Version 0.9.11 does automatically license with configuration Versions 1.1.0 & 1.1.1 do not license from the IBM KMS servers
Our configuration files Unattend.xml
Cloudbase-init.conf