This kmspico is helpful to cheat that activation technology to activate the Microsoft Products specially office 2016 very easily. Kmspico is a technology in which a KMS device activates Microsoft products also making a call to a KMSpico for Windows 10 and MS Office 2016 Final Activator server online while connecting to internet to avoid piracy. Hey guys in this video i will show you how to install and activate office 2016 KMS Activator link - Link 2 - http://festyy.com/wXMOMC.
We recently setup a new Windows Server 2016 server for our church office. We replaced a handful of workstations with new Windows 10 workstations. The rest are still Windows 7. We acquired a KMS volume license for MS Office 2016 Standard from TechSoup for all of the computers.
Following instructions online, we setup KMS Volume Activation on the server, manually configured DNS, and installed the license key. We then installed Office on all the workstations. The Windows 10 machines seem to activate fine. But, none of the Windows 7 machines' MS Office will activate. I tried doing it manually from the command prompt but get an error saying something to the effect that a volume activation server cannot be located. I ran the command to specify the server manually, but they still will not activate. Is there a way to get MS Office 2016 on Windows 7 workstations to activate with a Windows Server 2016 server with KMS?
Please note, there is no dual activation involved with any older versions of Office, so some of the usual fixes online aren't affecting this. Ok, so, just so I'm clear; you have successfully activated several OFF2016 installations, but those are on Win10 computers. You haven't successfully activated any OFF2016 installation upon Win7 computers. Your KMShost, is showing that it has not activated any OFF2016 clients (not even the Win10 computers). So, I'm thinking that your OFF2016 activations are occurring via another channel, maybe ADBA. ADBA can occur only on modern Windows OS versions - Win7 cannot service ADBA.
If that is true, it would explain why your Win10 scenarios are fine, and your Win7 scenarios are failing. Your KMShost seems to be setup ok but it isn't receiving any activation traffic from your clients (other than itself). Your KMSclients are sending requests, but it's not clear where they are going, only that they aren't received at your KMShost. You've found an old error which may help. 0xC0020017 = 'The RPC server is not available'. This is the lower-level reason for 'KMSclient could not activate/KMShost could not be contacted'.
This could be due to multiple reasons. Is server.skd.local the correct hostname for your KMShost?
From a Win7 KMSclient machine, can you ping server.skd.local and do you get a successful response? Since we seem to have determined that the counted requests @ KMShost are coming internally from the server itself, maybe we haven't properly ruled out a firewall constraint. Check the Windows Firewall configuration on the server. You should be able to confirm if TCP:1688 is allowed by a rule or not. Normally, when enabling the VA features, the wizard will do the firewall rule for you, or tell you that it's needed.
You could temporarily disable the windows firewall on the server, as a test, to try a KMSclient activation. But you only need to permit TCP:1688 inbound and you're done. There's a template in the firewall wizard for it on older OS versions, it's presumably still there in WS2016. Don doesn't work for MSFT, and they're probably glad about that;. But, none of the Windows 7 machines' MS Office will activate.
I tried doing it manually from the command prompt but get an error saying something to the effect that a volume activation server cannot be located Seems it's something on the client side. Please first try to run to analyze the client, which will quickly identify your KMS trouble spots. If the Office Client KMS activation diagnostic tool indicates you have KMS host issues, you should then run the Office KMS Host Activation diagnostic tool, to troubleshoot on the server side.
More reference: Regards, Ethan Hua Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact.
Hi, Thanks for the further clarification. I was about to share the following Office 2016 version of TechNet article: The Windows 10 machines seem to activate fine. You mean the Windows 10 system itself, or the Office 2016 client installed on Windows 10 platform? Try to examine the Windows event logs, on the KMS client machine, and also on the KMS host machine, to see if requests are being sent/received. (By the way, I hope you have installed this Office 2016 Volume License Pack which is required to setup a KMS configuration: ) Regards, Ethan Hua Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact.
See, that's just the thing. I run this diagnostic tool on one of the client machines, as instructed, but the tool gives me me an error message titled 'Office 2010 or Office 2013 not installed'. It further states 'If you are troubleshooting a KMS Host issue for Office, please click Cancel and then re-run this diagnostic package on a client machine in your organization with either Office 2010 or Office 2013 installed. The report generated by this KMS client diagnostic is a good place to start for many KMS host issues.
If you are not troubleshooting a KMS host issue, then you will need to have either Office 2010 or Office 2013 installed in order to troubleshoot a client issue with KMS activation.' The diagnostic report that gets created says to fix our issue we should install Office 2010 or Office 2013. We are running neither of these suites.
These are fresh installs of Office 2016. Yes, I meant the Office 2016 clients installed on Windows 10 platforms activate just fine. It's the Office 2016 installation on the Windows 7 platform that are not activating. I cannot find anything conclusive in the event logs.
Yes, I had installed the Office 2016 Volume License Pack as instructed. Thanks for your further assistance. Yes, I had installed the Office 2016 Volume License Pack as instructed. I wonder if you installed the OFF2016 VLpack in ADBA mode, or installed it in KMS mode? Windows 8 and Windows10 can use ADBA mode which would allow OFF2016 on those modern OS's to also use ADBA mode. But Windows7 can't use ADBA mode, so OFF2016 when deployed on Win7 computers, can only use KMS mode.
Check on your KMShost, the current status of the KMShost itself and also the status of ADBA, by using: cscript slmgr.vbs /dlv all somefilename.txt Open somefilename.txt, and you will see lots of 'license types', most will be 'unlicensed', but you are looking to see that the types you need are (or are not) licensed/activated, for your scenario. Reference doc for that: Don doesn't work for MSFT, and they're probably glad about that;. I have run this before. Essentially, there are two different sections pertaining to MS Office specifically that show licensed.
(There's a lot of trimmed content, but here's the gist.) Name: Office 16, Office16KMSHostVLKMSHost edition Description: Office 16, VOLUMEKMS channel Product Key Channel: Volume:CSVLK License Status: Licensed Key Management Service is enabled on this machine Listening on Port: 1688 DNS publishing enabled KMS priority: Normal It is my understanding that this CSVLK license represents the KMS Host and that the KMS management service is running. Name: Office 16, Office16StandardVLKMSClient edition Description: Office 16, VOLUMEKMSCLIENT channel Product Key Channel: Volume:GVLK License Status: Licensed It is my understanding that the GVLK represents the KMS client volume licenses. I have tried installing this in both Active Directory Authentication Mode and in KMS mode. Only the Windows 10 machines appear to activate. The Windows 7 machines do not.
I have run this before. Essentially, there are two different sections pertaining to MS Office specifically that show licensed. (There's a lot of trimmed content, but here's the gist.) Name: Office 16, Office16KMSHostVLKMSHost edition Description: Office 16, VOLUMEKMS channel Product Key Channel: Volume:CSVLK License Status: Licensed Key Management Service is enabled on this machine Listening on Port: 1688 DNS publishing enabled KMS priority: Normal It is my understanding that this CSVLK license represents the KMS Host and that the KMS management service is running. Name: Office 16, Office16StandardVLKMSClient edition Description: Office 16, VOLUMEKMSCLIENT channel Product Key Channel: Volume:GVLK License Status: Licensed It is my understanding that the GVLK represents the KMS client volume licenses. I have tried installing this in both Active Directory Authentication Mode and in KMS mode. Only the Windows 10 machines appear to activate.
The Windows 7 machines do not. Yes, that information confirms the KMShost feature is installed and activated for OFF2016. Next step is to examine the (redacted) CurrentCount information for this specific VL pkey. The currentCount for.each. VL pkey has to be 5 or greater, else KMSclients will simply not be able to activate to this KMShost.
Also check the event logs on both KMSclient and KMShost, you should be seeing the KMSclient issue an activation request (logged at client), followed by receipt of that same request at KMShost (logged at host), followed by response from KMShost (logged at host) and receipt of that response at KMSclient (logged at client). If the request/response is not logged, check firewall at KMShost is allowing TCP:1688 inbound to KMShost. You should see the counters incrementing on KMShost (shown in the slmgr output when you use the /dli or /dlv parameters) Don doesn't work for MSFT, and they're probably glad about that;. Next step is to examine the (redacted) CurrentCount information for this specific VL pkey. The currentCount for.each. VL pkey has to be 5 or greater, else KMSclients will simply not be able to activate to this KMShost. Also check the event logs on both KMSclient and KMShost, you should be seeing the KMSclient issue an activation request (logged at client), followed by receipt of that same request at KMShost (logged at host), followed by response from KMShost (logged at host) and receipt of that response at KMSclient (logged at client).
If the request/response is not logged, check firewall at KMShost is allowing TCP:1688 inbound to KMShost. Next step is to examine the (redacted) CurrentCount information for this specific VL pkey. The currentCount for.each. VL pkey has to be 5 or greater, else KMSclients will simply not be able to activate to this KMShost. Also check the event logs on both KMSclient and KMShost, you should be seeing the KMSclient issue an activation request (logged at client), followed by receipt of that same request at KMShost (logged at host), followed by response from KMShost (logged at host) and receipt of that response at KMSclient (logged at client). If the request/response is not logged, check firewall at KMShost is allowing TCP:1688 inbound to KMShost.
Currencount=1, this means that only one single unique clientcomputer has contacted this KMShost for this product (OFF2016). The KMShost may well be madly communicating with lots of other computers for.other. products, but that isn't reflected for OFF2016 at all.
This KMShost has one client for OFF2016, and one client is not enough, there has to be 5 clients or.nothing. will activate for OFF2016.
You should be able to identify the one client that has contacted, by looking in the event logs on the kmshost for security-spp events with eventid's in the range of 2. Since the currentcount is 0, unless that is coming from the host itself having office installed, there's no firewall issue here. If the other products on this kmshost are handling activation traffic, it all runs on TCP:1688 so no firewall issue locally on the kmshost computer.
If you have OFF2016 activated happily on.any. computers, it wasn't done via this kmshost at all - you've activated those OFF2016 installs via some other method/channel. This kmshost has not activated.any. OFF2016 kmsclients - there is simply not enough count for it to have done so (unless you've reset counters?) every kmsclient will converse with kmshost daily, in typical scenarios. If the kmshost is serving windows activation.and. office activation, there will be a readily visible amount of counter increase and log traffic. If you've only got around 10 computers, the traffic will be harder to find because there's less of it around.
Kmsclients may come and go over time e.g. Laptops which are in and out of the office. The currentcount is maintained on a rolling 30day basis, of unique client hardware identity (CMID) contacting kmshost (either to renew activation or request activation). So sine you've only had 5 requests, that's likely to be that single unit has contacted your kmshost 5 times.
Wich gives you a currentcount=1. The same guy contacted kmshost 5 times. Why only that guy? Where are the other guys? Check the logs on host and client to find out why. Don doesn't work for MSFT, and they're probably glad about that; This makes more sense. I checked Windows Event Viewer on the server, sorting by the Event ID column, and as you pointed out it appears that the SERVER itself must be the computer.
I did install Office on it as well and it's the only one I can see showing up in the event logs about 5-6 times in a row. This is a small church office. There is only the one server, which the KMS Host is installed on, and about 11 workstations. I installed Office 2016 on all the computers.
So, if the firewall isn't blocking anything, why is it the Windows 10 workstations show up as activated and the Windows 7 machines don't? This is the first time we've done volume license activation so we're not activating Windows OS or any other software in this fashion - only Office 2016. Just in case a previous office admin tried fiddling with this stuff, is there a way to search the network for the existence of other KMS Hosts? I found out how to search the network for other KMS Hosts and there aren't any.
I also checked the event logs on a couple workstations and they are sending multiple activation requests to the KMS Host. I just cannot fathom why the requests aren't being received. I tried to follow some other instructions I found for activating one of the workstations manually. This also failed with the following error: C: Program Files Microsoft Office Office16cscript OSPP.VBS /act Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved.Processing- - Installed product key detected - attempting to activate the following product: SKU ID: dedfa23d-6ed1-45a6-85dc-63cae0546de6 LICENSE NAME: Office 16, Office16StandardVLKMSClient edition LICENSE DESCRIPTION: Office 16, VOLUMEKMSCLIENT channel Last 5 characters of installed product key: DRTFM ERROR CODE: 0xC004F074 ERROR DESCRIPTION: The Software Licensing Service reported that the product could not be activated.
No Key Management Se rvice (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: When I ran the suggested command 'cscript ospp.vbs /dhistorykms' I got a laundry list of errors with many dates. Here's an example of one of them: - Coordinated Universal Time Written: 8/25/2017 4:09:23 PM ERROR/HOST: 0xC0020017, 0x00000000, SERVER.skd.local ERROR DESCRIPTION: Run the following: cscript ospp.vbs /ddescr:0xC0020017 - If I run the command 'cscript ospp.vbs /ddescr:0xc0020017' as suggested I get a popup window titled 'Windows Activation' with a generic message 'An Error Has Occurred' and button to 'Close'. Ok, so, just so I'm clear; you have successfully activated several OFF2016 installations, but those are on Win10 computers. You haven't successfully activated any OFF2016 installation upon Win7 computers.
Your KMShost, is showing that it has not activated any OFF2016 clients (not even the Win10 computers). So, I'm thinking that your OFF2016 activations are occurring via another channel, maybe ADBA. ADBA can occur only on modern Windows OS versions - Win7 cannot service ADBA. If that is true, it would explain why your Win10 scenarios are fine, and your Win7 scenarios are failing.
Your KMShost seems to be setup ok but it isn't receiving any activation traffic from your clients (other than itself). Your KMSclients are sending requests, but it's not clear where they are going, only that they aren't received at your KMShost. You've found an old error which may help. 0xC0020017 = 'The RPC server is not available'. This is the lower-level reason for 'KMSclient could not activate/KMShost could not be contacted'.
This could be due to multiple reasons. Is server.skd.local the correct hostname for your KMShost? From a Win7 KMSclient machine, can you ping server.skd.local and do you get a successful response? Since we seem to have determined that the counted requests @ KMShost are coming internally from the server itself, maybe we haven't properly ruled out a firewall constraint.
Check the Windows Firewall configuration on the server. You should be able to confirm if TCP:1688 is allowed by a rule or not. Normally, when enabling the VA features, the wizard will do the firewall rule for you, or tell you that it's needed.
You could temporarily disable the windows firewall on the server, as a test, to try a KMSclient activation. But you only need to permit TCP:1688 inbound and you're done.
There's a template in the firewall wizard for it on older OS versions, it's presumably still there in WS2016. Don doesn't work for MSFT, and they're probably glad about that;.
Ok, so, just so I'm clear; you have successfully activated several OFF2016 installations, but those are on Win10 computers. You haven't successfully activated any OFF2016 installation upon Win7 computers. Your KMShost, is showing that it has not activated any OFF2016 clients (not even the Win10 computers). Correct So, I'm thinking that your OFF2016 activations are occurring via another channel, maybe ADBA. ADBA can occur only on modern Windows OS versions - Win7 cannot service ADBA.
If that is true, it would explain why your Win10 scenarios are fine, and your Win7 scenarios are failing. Your KMShost seems to be setup ok but it isn't receiving any activation traffic from your clients (other than itself). So, is there a way I can check whether or not this is being done by ADBA? Where do I go to look for that? Is server.skd.local the correct hostname for your KMShost?
From a Win7 KMSclient machine, can you ping server.skd.local and do you get a successful response? Since we seem to have determined that the counted requests @ KMShost are coming internally from the server itself, maybe we haven't properly ruled out a firewall constraint. Check the Windows Firewall configuration on the server. You should be able to confirm if TCP:1688 is allowed by a rule or not.
Normally, when enabling the VA features, the wizard will do the firewall rule for you, or tell you that it's needed. You could temporarily disable the windows firewall on the server, as a test, to try a KMSclient activation. But you only need to permit TCP:1688 inbound and you're done. There's a template in the firewall wizard for it on older OS versions, it's presumably still there in WS2016. I have tried doing this with the firewall turned off with the same results. I did check the firewall and it looks like the rules were created during installation and that port is open.
Contents. Download original Office 2016 ISO You can get the latest version of Microsoft Office 2016 if you don’t have it. Once your download is complete, you need to extract the original ISO image from the zip file. You will be left with a file named “SWDVD5OfficeProfessionalPlus2016W32English” (W32 here in the filename refers to the 32-bit version, if you download the 64-bit version, the filename will contain 64Bit instead). Although an ISO file is used to burn CD or DVD, you can install Office 2016 without burning it using 7-zip or similar archive software utility. Here is what you get after extracting the ISO file. Installing Microsoft Office 2016 Simply run the setup file (named setup.exe) to install Office on your Windows.
Note: By default, Office will be installed in C: Program Files. Activate all versions of Office 2016 for FREE permanently. Supported products: – Microsoft Office Standard 2016 – Microsoft Office Professional Plus 2016 Step 1: Copy the following code into a new text document.
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |