Share via

Activate My key for Windows Server standard 2022

Zouaoui, Amine 0 Reputation points
2026-03-05T10:03:25.5766667+00:00

Hi Microsoft:

I have an issue with a server DellEmc purchased during last summer and installed Microsoft Windows Server 2022 in July. The key was inserted properly and activated by Internet.

Now Windows is saying Activate Key and the error message displayed is 0x8007232B.

Please assist on the activation of my key.

Best regards,

Amine.

Windows for business | Windows Server | Devices and deployment | Licensing and activation
{count} votes

2 answers

Sort by: Most helpful
  1. Zouaoui, Amine 0 Reputation points
    2026-03-05T10:05:02.4133333+00:00

    How to contact Microsoft Licensing Activation Centers?

    0 comments No comments

  2. Q&A Assist
    2026-03-05T10:03:37.0166667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Error 0x8007232B means “DNS name does not exist” and typically occurs when Windows is trying to activate as a KMS client but cannot find a KMS server in DNS.

    To resolve this on Windows Server 2022 Standard:

    1. Confirm how the server should be activated:
      • If it should use a Multiple Activation Key (MAK) or a Retail key from Dell/Microsoft, install that key directly.
      • If it should use a Key Management Service (KMS) in the organization, ensure the KMS host and DNS records are correctly configured.
    2. If using a MAK/Retail key (most OEM/Dell scenarios):
      1. Open an elevated Command Prompt (Run as administrator).
      2. Install the correct key:
              slmgr.vbs /ipk <your-25-character-product-key>
        
      3. Then activate online:
              slmgr.vbs /ato
        
      This forces the server to use the installed key instead of trying KMS, bypassing the 0x8007232B DNS/KMS error.
    3. If using KMS activation:
      • The error indicates the KMS client cannot find KMS SRV records in DNS.
      • Ensure:
        • A KMS host is installed and publishing SRV records to DNS.
        • DNS is reachable and healthy from this server.
      • If DNS auto-discovery is not available, manually point the client to the KMS host from an elevated Command Prompt:
             slmgr.vbs /skms <kms_host_name>
             slmgr.vbs /ato
        
      • If there is no KMS host in the environment, obtain and install a MAK instead, then activate as in step 2.
    4. If DNS/network issues persist:
      • Troubleshoot network connectivity and DNS resolution as per the KMS/DNS troubleshooting guidance referenced in the documentation.

    If these steps do not resolve activation and the key is valid, contact the Microsoft Licensing Activation Centers for further assistance with the key and activation history.


    References:

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.