Share via

Server Core 2025 Volume Activation Error

Kevin Foster 1 Reputation point
2025-12-09T16:37:14.97+00:00

KMS Host is running Server 2025 (Core) and has all current patches/updates.

When attempting to activate the KMS host key for Office 2024, I get an error in Server Manager:

User's image I attempted the phone option, but that has apparently been discontinued and no longer functions from within the United States.

Server 2025 firewall rules allow TCP ports 80/443 and 1688 outbound.

Has anyone else encountered this issue trying to do remote VA management of a Server Core system?

Windows for business | Windows Server | Devices and deployment | Licensing and activation
0 comments
Answer accepted by question author
  1. VPHAN 10,560 Reputation points Independent Advisor
    2025-12-10T17:23:54.51+00:00

    Hi there,

    The "Unlicensed" status and the missing firewall rule confirm two specific things:

    Firewall: The "Remote Volume Activation Management" rule doesn't exist because the Volume Activation Services server role hasn't actually been installed or initialized yet via PowerShell; the firewall rule is created by the role installation.

    Unlicensed Status: Your slmgr /ato command likely failed to target the Office 2024 license specifically. By default, slmgr /ato attempts to activate the Windows OS only. Since your Windows OS is likely already activated, it reports success, but the specific Office KMS Host identity remains untouched and "Unlicensed."

    To fix this on Server Core, you must manually target the Activation ID of the Office 2024 license.

    Step 1: Force Activation for the Office Identity

    You need the specific Activation ID (GUID) associated with that "Office 24" entry you found.

    Run slmgr /dlv all again.

    Scroll to the section: Name: Office 24, Office24KMSHost2024VL_KMS_Host edition

    Look for the line: Activation ID: (It will be a long GUID, e.g., e17e...).

    Run the activation command targeting that specific ID: slmgr /ato <Activation-ID-GUID>

    If you receive a "Success" message, run /dlv all again to confirm the status is now "Licensed."

    Step 2: Bypass for Phone Activation (If Online Fails)

    If Step 1 fails with a network error (like 0x80072EE7 or 0xC004C008), and since the slui 4 GUI is dead on Server 2025 Core, you must perform the "Phone Activation" via command line.

    Generate the Installation ID (IID): slmgr /dti <Activation-ID-GUID> (Note: You MUST include the GUID from Step 1, or it will generate an ID for Windows instead).

    Call the Center: You mentioned the number doesn't work, but the Microsoft Licensing Activation Center numbers are still active for Volume Licensing. You cant use the consumer numbers. Call (888) 352-7140 (US Volume Licensing).

    Enter the IID: When prompted, enter the huge number sequence generated in step 1.

    Apply the Confirmation ID (CID): slmgr /atp <Confirmation-ID> <Activation-ID-GUID>

    Step 3: Install the Role (To fix the Firewall Rule)

    To fix your original firewall error (so you can manage this remotely in the future), install the role properly via PowerShell: Install-WindowsFeature -Name VolumeActivation -IncludeManagementTools Once this finishes, the Remote Volume Activation Management firewall rule will appear, and you can enable it.

    VPHAN

    1 person found this answer helpful.

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. VPHAN 10,560 Reputation points Independent Advisor
    2025-12-09T21:26:35.51+00:00

    Hi Kevin Foster,

    The error you are seeing in the Volume Activation Tools (VAT) wizard, "The firewall rules could not be accessed", is misleading. It does not mean the server can't talk to Microsoft (outbound); it means your management console can't talk to the server's firewall service (inbound) via WMI/RPC to configure the exceptions.

    You are running Server Core, which blocks the incoming Windows Management Instrumentation (WMI) and Remote Volume Activation traffic by default. Opening ports 80/443/1688 outbound handles the activation itself, but it does not allow the remote VAT tool to connect and apply the key.

    There are two ways to resolve this:

    First, fix the Firewall for Remote Management (To use the GUI)

    You need to permit the WMI traffic inbound on the Server 2025 Core box so the VAT tool can connect. Run this command in an administrative PowerShell session on the Server Core machine:

    Enable-NetFirewallRule -DisplayGroup "Windows Management Instrumentation (WMI)"

    Enable-NetFirewallRule -DisplayGroup "Remote Volume Activation Management"

    If the "Remote Volume Activation Management" group does not exist yet (because the role isn't fully active), the WMI rule is usually sufficient for the tool to perform its initial handshake.

    The second option is the "Server Core" Native Method (Recommended)

    Since you are on Core, it is often cleaner to bypass the remote GUI connection issues entirely and install the key using the native slmgr command line directly on the console.

    Install the License Pack: Ensure you have run the Office2024VolumeLicensePack_x64.exe on the server. This installs the necessary CSVLK license files into the Software Protection Platform.

    Install the Key: slmgr.vbs /ipk <Your-Office-2024-KMS-Host-Key>

    Activate: slmgr.vbs /ato (This attempts to activate all installed licenses. If it activates Windows but not Office, you may need the specific Activation ID, but usually /ato catches the pending Office key automatically).

    Verify: slmgr.vbs /dlv all Look for the section saying "Office 24, VOLUME_KMS_channel" to confirm it is "Licensed".

    I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to ACCEPT ANSWER. Should you have more questions, feel free to leave a message. Have a nice day!

    VPHAN

  2. VPHAN 10,560 Reputation points Independent Advisor
    2025-12-10T15:43:48.0733333+00:00

    Hi, I'm writing to follow up and see if enabling the "Windows Management Instrumentation (WMI)" firewall group allowed your remote Volume Activation Tools console to successfully connect to the Server Core instance.

    If either of these solutions helped you get the Office 2024 KMS key installed and the host active, please consider accepting the answer. This confirmation helps other sharing the same question. Thank you!

    VP

    0 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.