Share via

KMS Activation - SCCM Task Sequence

Connor T Owens 0 Reputation points
2026-02-12T01:16:55.4333333+00:00

Hey everyone! New SCCM admin here!

Got a little bit of an interesting one here, got devices imaging to 25H2, we had issues with the the KMS product key being set during the TS, so we took it out, but we are noticing that freshly imaged devices are getting Win11 Education (that is our target) but the product channel is Retail, which is not compatible with Volume Licensing. Anyone else have this happen?

Thanks for all your insight!

Moved from Microsoft System Center | Other

Windows for business | Windows Client for IT Pros | User experience | Other
0 comments No comments

3 answers

Sort by: Most helpful
  1. Brian Huynh 3,045 Reputation points Microsoft External Staff Moderator
    2026-02-12T09:00:51.77+00:00

    Hi Connor T Owens

    Fresh images show Windows 11 Education but the product channel is Retail because the image or task sequence removed/never applied the Volume licensing key during imaging. When no volume key is present the OS falls back to a retail channel/digital license state even though the SKU is Education.

    Please try these following steps:

    1. Apply the correct Volume key for Education during the TS or after imaging:
    slmgr /ipk <GVLK-for-Win11-Education>
    slmgr /ato
    
    1. If you use KMS, ensure the KMS client setup key is applied and the KMS server is reachable from the device (DNS/SRV or direct host).
    2. For MDT/SCCM task sequences, add a step to inject the volume key before first boot completes.
    3. If the image itself contains a retail PID, rebuild the reference image without a retail product key (generalize with sysprep) so it doesn’t bake in a retail channel.
    4. Reimage one test device after making the TS change to confirm the channel becomes Volume and activation succeeds.

    Applying the GVLK/KMS client key forces the OS to register as a volume-licensed client and contact your KMS/MAK for activation; that flips the channel from Retail to Volume and resolves incompatibility with volume licensing.

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

    Was this answer helpful?


  2. Domic Vo 22,765 Reputation points Independent Advisor
    2026-02-12T08:39:13.2133333+00:00

    Hello Connor T Owens,

    What you are seeing is expected behavior when imaging Windows 11 Education without explicitly applying the correct Volume License channel key. By default, if no KMS/MAK key is injected during the Task Sequence, Windows Setup will fall back to a Retail channel key embedded in the media. That’s why your freshly imaged devices show “Windows 11 Education” but the activation channel is Retail, which is not compatible with your Volume Licensing agreements.

    To align the channel correctly, you need to ensure that the Task Sequence applies the proper GVLK (Generic Volume License Key) for Education edition. For Windows 11 Education, the current GVLK is:

    YNMGQ-8RYV3-4PGQ3-C8XTP-7CFBY

    This key does not activate the system by itself, but it switches the licensing channel to Volume. Once the channel is set, the machine will activate against your KMS host or Azure AD‑based activation service. Without this step, the OS defaults to Retail and activation fails.

    The cleanest way to handle this in SCCM is to add a “Set Product Key” step in your Task Sequence using the Education GVLK. Alternatively, you can run:

    slmgr /ipk YNMGQ-8RYV3-4PGQ3-C8XTP-7CFBY

    slmgr /ato

    after imaging. This forces the edition into the Volume channel and triggers activation.

    In short, the issue is not with the edition itself but with the licensing channel. You must apply the correct Volume GVLK during or immediately after imaging to avoid Retail fallback.

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

    Domic Vo.

    Was this answer helpful?


  3. AI answer

    2026-02-12T01:17:04.3633333+00:00

    It sounds like you're encountering an issue where the newly imaged devices are being activated with a Retail channel instead of the expected Volume Licensing channel. This can happen if the installation media used for imaging the devices was not the correct version or if the KMS product key was not properly set during the task sequence (TS).

    To resolve this, ensure that you specify the KMS client setup keys in the locations where the OEM product key is typically set during the TS. This includes the Apply Windows Settings or Upgrade Operating System steps. If you need to use the OEM product key, you can add a Run Command Line step after the relevant setup steps to specify the OEM key using changepk.exe or slmgr.vbs commands.

    Additionally, verify that the installation media you are using is a Volume License version and not a Retail version. If the media is incorrect, you may need to obtain the proper Volume License ISO to ensure that the devices are activated correctly with the Volume Licensing channel.

    If you continue to face issues, consider checking the activation status of the devices using the slmgr /dlv command to see what channel they are currently using and troubleshoot from there.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.