1

I currently have a KMS host server running on a 2019 Server VM. When I run a “cscript slmgr.vbs /dlv” command, I show it’s licensed description of Windows Operating System, Volume_KMS_W22 channel.

I am wanting to transition over to AD based activation, but when I input the same product key I used for KMS that was successful, I am getting an error reporting “The Software Licensing Service reported that the product key is invalid.” This is my CSVLK and not the public global one.

Thoughts?

7 Spice ups
2

You have to enable internet to AD and try again later because KMS server gives activation code from internet.

2 Spice ups
3

Why do you want to move from standalone KMS to AD? What are the benfits you want to achieve?

1 Spice up
4

@francescobianchessibarb875055 So that I’m not bound by the server version of the KMS for licensing newer server OS and built in redundancies instead of relying on one KMS server.

@sadik96 Internet access is already afforded to the AD server in quesion

1 Spice up
5

Good points. Thank you.

1 Spice up
6

Not all CSVLKs are valid for ADBA. Some keys that work for traditional KMS activation may not be accepted when configuring ADBA.
Ensure the key you’re using is specifically supported for ADBA.

Your AD forest schema must be at least Windows Server 2012 R2 level.

Do not use slmgr.vbs /ipk directly on the server for ADBA setup. Instead, use the Volume Activation Tools GUI to input the key and create the activation object in AD.

2 Spice ups
7

[Moderator removed illegal activation bypasses]

8

Don’t post illegal ways to activate systems

3 Spice ups
10

We’re happy you’re here to help, but please keep things legal, don’t promote anything that would be considered ‘shady’ in a business environment, nor for home labs.

You’ve also tagged the wrong person, and I’m not staff.

4 Spice ups
12

Hmmm. Never heard of that before (ABDA appropriate keys). My KMS and MAK keys are shown to me via my O365 admin portal and I don’t see any kind of distinction referred to in that regard as it pertains to ones for ABDA use. I am going through VAT to try and do the activation and it’s what is telling me that the product key is invalid.

1 Spice up
13

You’re not trying to use the CSVLK on the client are you?

If you try to install the CSVLK directly on a client or use it outside the Volume Activation Tools wizard, it will throw the “invalid key” error.

You should use the GVLK on the clients and the CSVLK at the ADBA Wizard.

Any machines not in the domain, for example a DMZ or workgroup machine would need another activation method.

1 Spice up
14

@Rod-IT No, I am attempting to use the CSVLK at the ADBA Wizard that I get from my O365 licensing portal. This same key was used prior at my KMS host server successfully with no issue.

1 Spice up
15

But as noted the KMS key doesn’t always support CSVLK.

You must use a CSVLK that matches the target OS version to create a valid activation object.

Some older or specific CSVLKs are only valid for KMS and not for ADBA.
ADBA requires the key to be explicitly supported for that activation method.

ADBA requires the CSVLK to match or exceed the OS version you’re activating.

If you can share the last 5 characters of the key I can check the type for you.

Also see the last 2 comments here

Unable to add KMS host key (ADBA) : error 0xC004F07E - Microsoft Q&A

1 Spice up