- Error 0xc004f074 Server 2016
- Windows Server 2016 Update Error 0x8024…
- Office 2016 Activation Error 0xc004f074
- 0xc004f069 Error Windows Server 2016 Essentials
- Error 0xc004f069 Windows Server 2016
Posted by4 years ago
Archived
Activating Windows. Open a command prompt with elevation. Install default product key (bellow is example for Windows Server 2016 datacenter) cscript.exe c: windows system32 slmgr.vbs /ipk WC2BQ-8NRM3-FDDYY-2BFGV-KHKQY. For other keys refer to this link. Run the following command to point Windows to the KMS server. Windows 2012 is based on the same core as Windows 8 - and doesn't use the same licensing protection system as Windows 7 I don't have a Win 8/Server 2012 system handy, but if you run the licensingdiag tool, it will produce a report similar to the MGADiag one.
So we're running a Windows 2008R2 server as our KMS server.
Techyv is one of the leading solution providers covering different aspects of Computers and Information Technology. We have a hardworking team of professionals in different areas that can provide you with guaranteed solutions to a blend of your problems. I am kind of stuck atm.I have done this process 100 times, no issues before.Bought a Dell server with 2016 Standard server.Host is activated, only item installed is hyper-v mana. 2016 VMs not activating? Windows 2012 R2 activation 0xC004F069 Today I tryed to activate my Virtual Machine on Windows 2012 R2 Datacenter with AVMA key. Here under are key to automatic activate windows 2012 R2 that are running on Datacenter edition HyperV.
I've installed the Microsoft Office 2016 Volume License Pack from here
I've inputted my kms key , that for some reason I had to call MS to get?
Now on my workstation I initially upgraded my Office 2013 to 2016, since then i've also uninstalled everything and reinstalled and it will not automatically activate?
So on my machine I run cscript ospp.vbs /act and receive the following error
Installed product key detected - attempting to activate the following product:SKU ID:LICENSE NAME: Office 15, OfficeProPlusVL_KMS_Client editionLICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channelLast 5 characters of installed product key: [LETTERS]<Product activation successful>
Installed product key detected - attempting to activate the following product:SKU ID:LICENSE NAME: Office 16, Office16ProPlusVL_KMS_Client editionLICENSE DESCRIPTION: Office 16, VOLUME_KMSCLIENT channelLast 5 characters of installed product key: [LETTERS]ERROR CODE: 0xC004F074ERROR 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 /dhistorykmsNOTICE: A KB article has been detected for activation failure: 0xC004F074FOR MORE INFORMATION PLEASE VISIT: http://support.microsoft.com/kb/2870357#Error0xC004F074
---Exiting-----------------------------
I've even tried forcing activation through VAMT and receive a error:
The Software Licensing Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information
and when i look in event viewer i see:
Error operating on product: Application Name: Office . Exception System.Runtime.InteropServices.COMException (0xC004F074) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options) at Microsoft.Licensing.VolumeActivation.WmiConnection.ExecuteMethod(String queryString, String actionValue, Dictionary`2 wmiParameter) at Microsoft.Licensing.VolumeActivation.SoftwareLicensingProvider.ActivateProduct(Product product) at Microsoft.Licensing.VolumeActivation.SoftwareLicensingProvider.VolumeActivate(Product product) at Microsoft.Licensing.VolumeActivation.VolumeActivationWorker.OnDoWork(Product product) at Microsoft.Licensing.VolumeActivation.WmiProviderWorker.Work()
Not sure if i missing something? if anyone knows how a can resolve this i would be greatly appreciated.
Thanks
49 comments
If you try to activate Windows 10 on a KMS host running on Windows 8, Windows 8.1, Windows Server 2012, and Windows Server 2012 R2 KMS hosts, you might receive an error message (Error: 0xC004F050). In this post, I show you how to solve the problem.
Tim Buntrock
Tim Buntrock is one of three enterprise administrators for the Active Directory service of a 'global player' in the contact center business. He is a certified engineer for MCTS, MCITP, MCSA and MCPS.
Latest posts by Tim Buntrock (see all)
- Create a self-signed certificate with PowerShell - Thu, Aug 9 2018
- Prevent copying of an Active Directory attribute when duplicating a user account - Thu, Mar 29 2018
- Find and delete unlinked (orphaned) GPOs with PowerShell - Thu, Mar 15 2018
If you are trying to install your KMS key on a server with one of the above operating systems, you might run into the following error:
Error: 0xC004F050 The Software Licensing Service reported that the product key is invalid
Error 0xc004f074 Server 2016
The prerequisites ^
Windows Server 2016 Update Error 0x8024…
My guide assumes that your environment meets the following requirements:
- TCP port 1688 is open on the computer running the KMS host.
- At least 25 clients or 5 servers have contacted the KMS.
- An SRV record for your KMS exists on your DNS server.
- You have domain admin rights.
To activate Windows 10 on a KMS host running a previous Windows version, you can now follow the procedure below.
The fix ^
- Install update KB3058168.
This update enables the KMS for Windows 8, Windows 8.1, Windows Server 2012, and Windows Server 2012 R2 to activate Windows 10 clients. - Get the right Windows 10 KMS key.
- Sign in to the Volume Licensing Service Center.
- On the top menu, click License– Relationship Summary.
- Click the Licensing ID for your active agreement.
- Select Product Keys and go to Agreement Details.
- For Windows Server 2012/R2, you have to use the Windows Srv 2012R2 DataCtr/Std KMS for Windows 10 key. For Windows 8/8.1, use the Windows 10 KMSkey.
- Install the KMS key on your KMS host.
- Open a command prompt and type the following command to install the key:
slmgr.vbs /ipk <KmsSetupKey> - Verify the key installation:
slmgr.vbs /dlv - Uninstall old keys:
slmgr.vbs /upk - Activate Windows:
slmgr.vbs /ato
- Open a command prompt and type the following command to install the key:
See this article to get more information about slmgr.vbs.
Other errors ^
Error 0xc004f038, KMS count is below 25 for Windows client computers or less than five for Windows Server machines
Solution:
Not enough KMS clients exist for the KMS host. You can check if the client uses a non-VL key by typing the command slmgr.vbs /dlv. If no client reported to the KMS host, check if port TCP 1688 is open.
You can also check whether another KMS host exists on the network. Microsoft word 2013 macros. To get a list, type the following command:
Error 0xc004e003, The Software Licensing Service reports that the license evaluation failed
Solution:
Rename the tokens.dat file on the KMS host and create a new one with this command:
Office 2016 Activation Error 0xc004f074
Error: 0xC004F015 On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0xC004F015' to display the error text
0xc004f069 Error Windows Server 2016 Essentials
Solution:
Error 0xc004f069 Windows Server 2016
You used a Windows 10 KMS key on a server OS. Use the Windows Srv 2012R2 DataCtr/Std KMS for Windows 10 key.