- #CANNOT FIND MY OFFICE 2016 ACTIVATION KEY WINDOWS 10#
- #CANNOT FIND MY OFFICE 2016 ACTIVATION KEY SOFTWARE#
- #CANNOT FIND MY OFFICE 2016 ACTIVATION KEY LICENSE#
- #CANNOT FIND MY OFFICE 2016 ACTIVATION KEY WINDOWS 7#
If you have any updates, feel free to post back to let us know. Local administratorĪccess is not required, but read/write access to the activation object container in the root domain of the forest is required. You can use the slmgr.vbs /ad-activation-online command to collect Active Directory data and initiates Active Directory forest activation using the credentials that the command prompt is running. Office\Office16\"ospp.vbs /dstatus /unpkey:DRTFM or cscript "%ProgramFiles%\Microsoft Office\Office16\"ospp.vbs /dstatus /unpkey:DRTFM to remove the GLVK(product key). You can run cscript "%ProgramFiles(x86)%\Microsoft KB 938450, this error 0XC004F042 means a mismatch between the client and server KMS keys. A thread that suggested removing the key, rebooting, installing the key, activating and rebooting again to resolve a similar issue. Please mark sure you have join these computers to the domain. Of your command, the GLVK was successfully added already. You should use slmgr.vbs /ipk JNRGM-WHDWX-FJJG3-K47QV-DRTFM. The blog to check if Active Directory Based Activation was configured correctly.Īfter you configure Active Directory-based activation, in client, run the slmgr.vbs /ipk command and specifying the GLVK as the new product key for Office 2016(VL). Please refer to Activate volume licensed versions of Office by using Active Directory or I've called the VLSC but they won't even talk to me without a credit card.Īny ideas would be great, and thanks for the help. However, it won't let me add that one at all. Office Standard 2016 - JNRGM-WHDWX-FJJG3-K47QV-DRTFM So, I went and grabbed a generic public key from Microsoft: The only thing I can come up with is the KMS key I'm pulling from the VLSC isn't any good even though it successfully added as an object to AD just fine through the wizard.
#CANNOT FIND MY OFFICE 2016 ACTIVATION KEY WINDOWS 10#
Now maybe it just doesn't log it? But I know ADBA is functioning because my Windows 10 Enterprise machines are getting a GVLK key. As I understand it, it should be checking ADBA first, then trying KMS. It should be using the Active Directory Based Activation server
#CANNOT FIND MY OFFICE 2016 ACTIVATION KEY WINDOWS 7#
What I don't understand is why it's trying to activate with my old KMS server () that I still have in place because of all the Windows 7 and Office 2010 instances I still have.
*NOTE - The KB article referenced above doesn't exist. NOTICE: A KB article has been detected for activation failure: 0xC004F042Ĭoordinated Universal Time Written: 2:48:20 PMĮRROR/HOST: 0x00000000, 0x00000000, Key Management Service (KMS) cannot be used.
#CANNOT FIND MY OFFICE 2016 ACTIVATION KEY SOFTWARE#
Searching for KMS activation events on machine: ERIC-TESTĬoordinated Universal Time Written: 2:48:21 PMĮRROR/HOST: 0xC004F042, 0x00000000, ĮRROR DESCRIPTION: The Software Licensing Service determined that the specified When I run "cscript ospp.vbs /dhistorykms" I see this: NOTICE: A KB article has been detected for activation failure: 0xC004F074 To view the activation event history run: cscript ospp.vbs /dhistorykms Please sĮe the Application Event Log for additional information. No Key Management Service (KMS) could be contacted. Last 5 characters of installed product key: DRTFMĮRROR DESCRIPTION: The Software Licensing Service reported that the product coulĭ not be activated.
#CANNOT FIND MY OFFICE 2016 ACTIVATION KEY LICENSE#
LICENSE DESCRIPTION: Office 16, VOLUME_KMSCLIENT channel LICENSE NAME: Office 16, Office16StandardVL_KMS_Client edition Installed product key detected - attempting to activate the following product: However, when I run "ospp.vbs /act" I get the following: -Processing. On my workstations I'm installing the x86 Volume license version of Office 2016 Standard that I also pulled from the VLSC.
Successfully Added the Active director Object KMS key from the Volume Licensing Service Center (VLSC) I've installed the Office2016 Volume License Pack () A 2019 Standard server with ADBA installed