Server Product Keys not appearing correctly

Mackey_Info_Tech
Mackey_Info_Tech Member Posts: 18 ✭
edited December 2023 in Reporting

Anyone have this issue? We have recently upgraded a few servers to 2022. We have multiple individual product keys for each server. When I run a report in Atera, they only show as all B's with the exception of one server that came with 2022. Anyone ever seen this? When I look on the server itself, it displays the keys properly. Again, these servers were upgraded from 2016, so not fresh installs. Sucks if I have to manually look at each server to get the keys instead of Atera.

2022Servers.png

Comments

  • tanderson
    tanderson Member Posts: 279 ✭✭✭✭

    @Mackey_Info_Tech My servers are showing fine, even the ones that have been upgraded. I would reach out for support.

  • tanderson
    tanderson Member Posts: 279 ✭✭✭✭

    Actually some are showing all B's

  • mbudke
    mbudke Member Posts: 137 ✭✭✭

    Very interesting. I can confirm the same problem.
    In my case it impacts new installed server (not upgraded!) and just Win 2022.

  • tanderson
    tanderson Member Posts: 279 ✭✭✭✭

    My Server 2022 and 2019 are fine. Everything bellow that is just BBBB

  • Sarah_from_Atera
    Sarah_from_Atera Member Posts: 93 ✭✭✭

    Hi @Mackey_Info_Tech, @tanderson and @Matthias , Sarah from Atera here.

    I have opened support tickets for all of you, and I am also checking to see if there is a known issue with this.

  • mbudke
    mbudke Member Posts: 137 ✭✭✭

    Hi all,

    Atera seems to run the following command to get the license key:

    wmic path softwarelicensingservice get OA3xOriginalProductKey

    When I run it on my impacted server then there is no result which maybe explains the behavior.
    I did some research on google and it seems there could be at least 2 reasons.

    Reason 1)
    There are many reports on google that no result is presented when you are running a digital license (license from Mainboard)
    You can check this when you open the windows settings → Update → Activation. Either you see a message that the windows is activated or activated via digital license.

    Reason 2)
    In my case I am not using a digital license for my Windows Server 2022 Std but still impacted. A WIM repository repair did not help.
    Reason unknown.

  • mbudke
    mbudke Member Posts: 137 ✭✭✭

    @tanderson @Mackey_Info_Tech

    Do you still experience this issue? Unfortunately for me the issue is still existing and I am working with Support on a solution.
    To isolate if this is a "me-issue" 😁 I would like to know if you still see the problem.

    Thanks!

  • tanderson
    tanderson Member Posts: 279 ✭✭✭✭

    @Matthias Yes, some of our servers still show that. I worked with support on it a little while back when the thread was opened, and it didn't seem to fix anything. Good luck!

  • cjeffers
    cjeffers Member Posts: 28 ✭✭✭

    Was the original OS part of a Volume Licensing? If so, I believe that is a common issue on Windows after upgrading keys.

  • mbudke
    mbudke Member Posts: 137 ✭✭✭

    Thank you both for your quick feedback! Much appreciated!

    No, it is not a volume license. I have provided the feedback back to Atera support.

Topics