KMS Issue

[farmeunit]

I added Server 2016, Office 2016, and Office 2013 keys to KMS.  I also added Server 2016 KMS to AD, also for AD activation.  When trying to add both KMS keys for Office to do AD Activation, I get "Invalid product key or license mismatch.  Please confirm this product key is entered correctly and is valid for this application or Windows edition."

 

Server 2012R2 - AD at that functional level

[starman3344]

Don't talk about illegal things here, they don't like it...

[xendrome]

  On 20/12/2016 at 18:22, starman3344 said:

Don't talk about illegal things here, they don't like it...

Expand  

Bro, who said anything about illegal? KMS is the proper way to register/activate over AD for large deployments.

 

[starman3344]

Ok, sorry

[sc302 Veteran]

Can you verifiy what kms keys are installed? 

 

Server will activate both workstation and server of current and previous versions.

 

office is per version of office.  Please verify your kms keys to make sure that they aren't duplicated and to make sure that you have them installed. 

 

That is the first thing I would do, verify.

 

It almost sounds like you are attempting to install a previous version of windows kms host key onto your kms server...don't bother with that. 

[ThePhoenix]

Hmm, have you installed the Office KMS Packs?  KMS won't recognise Office keys without them.  (There's a pack for each office version)

[Seahorsepip Veteran]

Are you sure you got the kms version of office installed? (non-retail)

As far I remember retail office installs don't activate with kms.

[TPreston]

us the VAMT to change the keys of the products you are trying to activate to the ones found here

 

https://technet.microsoft.com/en-us/library/jj612867(v=ws.11).aspx

[farmeunit]

@starman3344 This is a completely legit scenario

 

I thought about trying VAMT.  I'm using the Volume Activation Tools built into Server 2012R2 and the RSAT for Windows 10.  Both give me the same error.  I will try VAMT next.

 

@ThePhoenix I installed both Office 2013 and 2016 packs

 

@sc302 I had the 2012R2/Win10 KMS key installed, but changed it to the Server 2016 KMS key today.  It works fine with the AD Activation.

 

Office 2016 activated fine today through DNS and the Server 2016 key installed fine on the KMS Server AND AD Activation, as well.  The Office keys installed fine to KMS, but neither one install for AD Activation.

 

I decided to start doing AD Activation because once it's activated, it doesn't require check-ins and there is no quota to meet for a minimum.  We're WAY over the minimum, anyway, but I would like to not have to activate laptops when they're off-site for long periods of time.

[sc302 Veteran]

for windows, you don't need any thing other than the 2016 key due to the availability of downgrade rights (you don't need to install the 10 key, 2008 key, 7, or 8 keys).  It won't even accept them (the issue you are running into) if you attempt to install them. 

 

for office, you need to install the kms key for each version of office....if you have 2013 you should be good with ad activation. 

[farmeunit]

Thanks for the information.  I understand how the versioning works for the Windows KMS keys.  I just use use the newest OS available. (didn't mean this to sound pretentious, BTW)

 

I just don't understand why the AD Activation won't work for the Office keys.  I even tried running the packs a second time and letting it bring the VAT window up.  I'm installing VAMT 3.1 now.

Edited December 20, 2016 by farmeunit

[farmeunit]

With VAMT, I'm getting "VAMT was unable to enumerate the AD Activation objects in this forest due to the following error:  The server is not operational.  Either the domain controller was not reachable or it is not properly configured for AD Forest Activation."

 

So obviously something is amiss, but I'm not sure where to start.  I didn't have to extend the schema, because we started on Server 2012R2 for this domain.  The AD Activation completed in VAT.

[farmeunit]

I might have found it, but it is causing another issue.  We moved from a workgroup (Novell) to domain this summer.  I joined the server to the domain, but the suffix still had our old domain when clicking the MORE button under Change for the computer name.  I removed that and now it's showing the AD Activation in VAMT, but the AD Activation option is greyed out in VAT.  I did activate the keys in VAMT for AD, though, so assuming.

 

It said that the Office keys for activated for AD Activation using VAMT, so we'll see what happens, lol.

 

Thanks for input.

 

 

[starman3344]

  On 20/12/2016 at 20:41, farmeunit said:

@starman3344 This is a completely legit scenario

 

I thought about trying VAMT.  I'm using the Volume Activation Tools built into Server 2012R2 and the RSAT for Windows 10.  Both give me the same error.  I will try VAMT next.

 

@ThePhoenix I installed both Office 2013 and 2016 packs

 

@sc302 I had the 2012R2/Win10 KMS key installed, but changed it to the Server 2016 KMS key today.  It works fine with the AD Activation.

 

Office 2016 activated fine today through DNS and the Server 2016 key installed fine on the KMS Server AND AD Activation, as well.  The Office keys installed fine to KMS, but neither one install for AD Activation.

 

I decided to start doing AD Activation because once it's activated, it doesn't require check-ins and there is no quota to meet for a minimum.  We're WAY over the minimum, anyway, but I would like to not have to activate laptops when they're off-site for long periods of time.

Expand  

Cool