Menu
Hello all,I am hoping to gain some knowledge on this problem I have been working on for a few weeks. I have a lab of 32 Windows 7 machines that previously had Microsoft Office 2013 installed and activated.
In preparation for the coming school year, I removed Microsoft Office 2013 and installed Microsoft Office 2016. I am unable to activate the Microsoft Office 2016 to our KMs server.
The KMS server is Windows 2012 R2 and is patched. The KMS server has activated Windows 10 machines and Office 2016 on Windows 10. The issue seems to be only with activating Office 2016 on Windows 7. The Event Viewer has event Id 12288 listed with the code of 0xC004F042. I had to rearm Office 2016 in order for the students not to see the activation window.
Currently, the ospp /dstatus shows the license status to be -OOBGRACE- with the error code: 0x4004F00C. I have been all over the net through forums and TechNet articles trying to fix this. Does anyone have any thoughts, hints, suggestions for what I can try next? Thank you for you time.Andy. My server guy and I have been looking at the firewalls on the server and on the clients.
Kms Server Installation Windows 2016 Version
There do not seem to be any rules preventing communication. When I run the activation via command line, I get the 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.I have tried activating with and without specifying the KMS server FQDN, but to no avail.
The application log has an event 12288 for the Office Software Protection Platform Service stating the client has sent an activation request to the key management service machine with the code of 0xc004F042, 0x00000000, kms2.x.x.x.
What is a KMS? Microsoft’s KMS allows you to automate license activation for Windows servers and/or applications. In my case, I am using KMS for Windows 2012R2 license activation. ( Oh, KMS stands for Key Management Server) The setup is simple, it took me no more than 15 minutes. Below are the steps I took to set this up.
Some pieces of information, I decided to dedicate a server for KMS. Also, when adding the Windows server key, double check and ensure you are using a valid Volume License key, and a KMS key — not MAK! (Yes, there is a difference)For starters I am going to assume you already made note of the license key from your Microsoft Volume License Servicing Center portal.As mentioned, I decided to stand up a server dedicated for KMS.From the Windows Server Manager, install the “ Volume Activation Services” role either via the GUI, or via PowerShell.
If via PowerShell, here is that command, “ Install-WindowsFeature -Name VolumeActivation -IncludeAllSubFeature”Once the role has been installed, launch the Volume Activation Tool console, and essentially next, next, finish!. Browse/Select the server that will be hosting the KMS (service):. Paste in your KMS Host/License Key:. Choose “ Active online“Here, you have some options, how often would you like KMS to check-in, how often would like KMS to apply the key, etc. I left my settings at default, but (assuming) your environment is domain based, check mark Domain for KMS firewall exceptions. Also, by default, KMS listens on TCP port 1688.And that is is!
Install Kms Server 2016 Step By Step
Now your existing/new Windows 2012R2 servers will have their licence automatically activated within 2 hours.For more information on Microsoft’s Key Management Server (KMS), please visit the following link.Cheers!
Install and configure Windows Server RoleWith Windows Server 2012 R2, it is necessary to install the Volume Activation Services role from the Server Manager consoleFollowing the installation, a new event is present in the consoleCheck the server name and click Next without making any changes.Enter the KMS key for Windows Server 2012 R2 or your operating system version and click on Validate.In the Product Key Management windows, leave the default choice and click Activate Product.Validate the following windows without making any changes. In the Add Firewall Exceptions windows, check the listening port and click Validate.On the KMS server, open a DOS command prompt and enter the following commands.Slmgr /ipk “KMSKey”.
A message appears, click OK and enter slmgr /ato. A message appears to warn you that the server has been successfully activated.It is now necessary to have a minimum of 5 activation requests for Office to start activation. Windows 10 transformation pack 7.0.exe.
For Windows Server he need 5 activation and 25 for Windows Client.Install and configure VAMTIn order to manage activation on workstations and servers, the VAMT console is installed. To do this, it is necessary to install SQL Server. SQL Server 2016 Express has been installed on the KMS server.In the database, click Database Engine Services and click Next.Click Next in the Configure instance windows without making any changes.Add the desired members as SYSADMIN of the database. Start installing SQL Server. VAMT can now be installed. This operation requires downloading ADK for Windows 10.The setup file can be retrieved from the Microsoft website.Once downloaded, the installation setup can be run.
In the Specify Location windows, click Next without making any changes.Click No in the Windows Kit Privacy Windows and accept the license agreement by clicking Accept. In the feature selection windows to be installed, check the following features:. Volume Activation Management Tool (VAMT)Lauch the installation by clicking Install.Once installed, it is necessary to launch the console from the KMS server.In the windows enter the name of the instance and select Create new database from the drop-down list. In the database name field, type KMS.
![2016 2016](https://image.slidesharecdn.com/configuringkmsenvironmentforwindows2016server-170228111648/95/configuring-kms-environment-for-windows-2016-server-windows-10and-office-2016-activations-3-638.jpg?cb=1488280791)
![Kms Server Installation Windows 2016 Kms Server Installation Windows 2016](https://www.computertechblog.com/wp-content/uploads/2019/02/image-20.png)
Click Connect to proceed with the connection.The console is displayed. Select Products and click Discover Products.In the windows that appears, click Search. Computers and servers present in AD appear.OFFICE 2013 Activation by KMSIn order to support KMS Office 2013 versions, it is first necessary to download Microsoft Office 2013 Volume License Pack.After downloading it, execute the file. Select the check box to accept the license terms and click Continue.A windows appears, click Next. Visual basic 6 portable download.
Enter the KMS server name and click Next.Enter the KMS key automatically and click on validate.
I’m and you may remember me from previous articles such as. Today’s installment will coincide with a new Windows Server release. I’m going to focus on getting you to enable AD Based Activation for those of you who have not yet done so.The location for the KMS Host Key is the same as Windows Server 2016. You need to find the key on the Microsoft Volume License Service Center.KMS Activation for Windows Server 2019 can be run from the following Operating Systems with the appropriate prerequisites:Windows Server 2012 R2July 2016 Servicing Stack Update:September 11, 2018 Cumulative Update:.Note. – If you’re reading this after a subsequent Patch Tuesday, the most recent Cumulative Update will include these changes as well. They were originally introduced in KB4343891.Windows Server 2016May 2018 Servicing Stack Update:August 30, 2018 Cumulative Update:.Note.
– You can install any future Windows Server 2016 Cumulative update and get these fixes. Most Organizations would have installed as part of their patching process.