Office 2016 KMS activation on Windows 7

[Matthew Strickland]

Hi all,

Diagnosis time is limited so I'll post here as someone might have an easy answer!

I have Active Directory activation of both Office 2013 and Office 2016 hosted on a 2012r2 server (its actually one of the DC's)

The latest "Microsoft Office 2016 Volume License Pack" is installed (16.0.4324.1002)

Office itself is not installed on the KMS host.

It seems others have this issue but related to a 2008r2 server, and that the volume licence pack corrects this?

Windows 10 clients activate perfectly fine:

Name: Office 16, Office16ProPlusVL_KMS_Client edition

Description: Office 16, VOLUME_KMSCLIENT channel

Activation ID: XXXXXXXXXXXXXXXXXXXXXXXXXXX

Application ID: 0ff1ce15-a989-479d-af46-f275c6370663

Extended PID: 03612-03391-000-000000-03-5129-10240.0000-2792015

Product Key Channel: Volume:GVLK

Installation ID: 488256012477603118511662356137807162125322557790348979739954164

Partial Product Key: WFG99

License Status: Licensed

Volume activation expiration: 257699 minute(s) (179 day(s))

Remaining App rearm count: 3

Remaining SKU rearm count: 3

Trusted time: 19/02/2016 10:41:12 AM

Configured Activation Type: All

Most recent activation information:

AD Activation client information

    Activation Object name: Office 16, VOLUME_KMS channel

    AO DN: CN=00206-437-024113-0,CN=Activation Objects,CN=Microsoft SPP,CN=Services,CN=Configuration,DC=karamu,DC=local

    AO extended PID: 06401-00206-437-024113-03-5129-9600.0000-2782015

    AO activation ID: 98ebfe73-2084-4c97-932c-c0cd1643bea7

However Windows 7 clients:

Installed product key detected - attempting to activate the following product:

SKU ID: d450596f-894d-49e0-966a-fd39ed4c4c64

LICENSE NAME: Office 16, Office16ProPlusVL_KMS_Client edition

LICENSE DESCRIPTION: Office 16, VOLUME_KMSCLIENT channel

Last 5 characters of installed product key: WFG99

ERROR CODE: 0xC004F074

ERROR DESCRIPTION: The Software Licensing Service reported that the product could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information.

To view the activation event history run: cscript OSPP.VBS /dhistorykms

NOTICE: A KB article has been detected for activation failure: 0xC004F074

FOR MORE INFORMATION PLEASE VISIT: http://support.microsoft.com/kb/2870357#Error0xC004F074

---------------------------------------

---------------------------------------

---Exiting-----------------------------

 

 

[Nathan Mercer]

only Windows 8+ operating systems support activation through AD BA. For Windows 7 or older you have to deploy a KMS server.

 

Active Directory Based Activation (AD BA)

https://technet.microsoft.com/en-us/library/hh831477.aspx#BKMK_actdir_adba

 

Today, Volume Licensing for Windows and Office requires Key Management Service (KMS) servers. That solution requires minimal training, and is a turnkey solution that covers about 90% of deployments.

But there is complexity caused by the lack of a graphical administration console. The solution requires RPC traffic on the network, which complicates matters, and it does not support any kind of authentication. The end-user licensing agreement (EULA) prohibits the customer from connecting the KMS server to any external network. For example, connectivity-alone to the service equates to activated.

 

In Windows Server 2012, the Active Directory-based activation provides the following improvements:

·         Uses your existing Active Directory infrastructure to activate your clients

·   No additional machines required

·   No RPC requirement; uses LDAP exclusively

·   Includes RODCs

·         Beyond installation and service-specific requirements, no data is written back to the directory

·   Activating initial CSVLK (customer-specific volume license key) requires:

·         One-time contact with Microsoft Activation Services over the Internet (identical to retail activation)

·         Key entered using volume activation server role or using command line.

·         Repeat the activation process for additional forests up to 6 times by default

·         Activation-object maintained in configuration partition

·   Represents proof of purchase

·   Computers can be member of any domain in the forest

·         All Windows 8 computers will automatically activate

Requirements

·         Only Windows 8 computers can leverage AD BA (and above)

·         KMS and AD BA can coexist

·   You still need KMS if you require down-level volume-licensing

·         Requires Windows Server 2012 Active Directory schema, not Windows Server 2012 domain controllers

---

From: techies-f...@googlegroups.com <techies-f...@googlegroups.com> on behalf of Matthew Strickland <ma...@zebis.co.nz>
Sent: Thursday, February 18, 2016 1:57 PM
To: Techies for schools
Subject: [techies-for-schools] Office 2016 KMS activation on Windows 7

 

--
You received this message because you are subscribed to the Google Groups "Techies for schools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to techies-for-sch...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Matthew Strickland]

Thanks Nathan,

I had found conflicting information as to which clients were supported, some sites included Windows 7, some didn't specifically mention.

I assumed this may have been the case but couldn't find what you have found. Dual KMS/AD BA it is until all clients > Win8.

Cheers!

To unsubscribe from this group and stop receiving emails from it, send an email to techies-for-schools+unsub...@googlegroups.com.

[Tracy Briscoe]

One thing to watch out for with a dual KMS/AD BA is if the number of clients connecting to the KMS server drops below the 25 minimum then I understand that the KMS will stop issuing licences.

I was considering adding AD BA until I saw this gotcha – we still have a few (<25) Win7 machines on the network too.

 

-Tracy

To unsubscribe from this group and stop receiving emails from it, send an email to techies-for-sch...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "Techies for schools" group.

To unsubscribe from this group and stop receiving emails from it, send an email to techies-for-sch...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Note: This communication may contain privileged and confidential information intended only for the addressee named above. Any views or opinions presented are solely those of the author. If you have received this message in error, we request you delete the message and notify the sender. Please do not distribute, copy or disclose any information. This e-mail has been scanned for viruses but all liability for viruses or similar in any attachment or message is excluded.

St Peter's School, Cambridge, New Zealand
Telephone: 647 827 9899 Fax: 647 827 9812
Website: www.stpeters.school.nz

Please consider the environment before printing this email

[Matthew Strickland]

Hi Tracy,

Yes I did consider the 25 OS client limit (5 for office) however KMS was left in place for Windows 7 clients. Office 2016 was the exception and as soon as I added the key to KMS a test client activated immediately.

From what I understand Windows 8/10 will try to activate using ADBA, and fall back to KMS. Since only Win8/10 can use ADBA and I have >300 clients it should be enough to keep both systems happy incase of failure.

Office in KMS wont be an issue with a limit of 5, but the Win7 OS could be in time to come. >24 or nothing I think.

Matt

To unsubscribe from this group and stop receiving emails from it, send an email to techies-for-schools+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Techies for schools" group.

To unsubscribe from this group and stop receiving emails from it, send an email to techies-for-schools+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.