Given: Microsoft Windows Server 2008 R2 Enterprise 64-bit, all the latest security updates applied.
Office 2016 Retail-VL MAK Keys Office 2016 Pro Retail Keys: Office 2016 Pro Plus Phone Activation Retail Key BN346-KPVRG-HHQG3-6YDPV-8HV7H 4KNF6-BY4QB-QFDW8-MCCJH-94TDV NT782-4R9JW-JYHG9-VVY8C-JB6DV B7WV8-K4NYK-QM8BD-YGFQT-6F4HH ------------------------------- Office 2016 Visio Pro Phone Activation Retail Key Not available right now.! ------------------------------- Office 2016 Project Pro Phone Activation Retail Key Not available right now.! ------------------------------- [Tested working on VM3 07 March 2016] Office 2016 Volume License MAK Keys Office 2016 Pro Plus Volume License MAK Key(s): Product Key(s)------------------Remaining Activation Counts Not available right now.! ------------------------------------------------------------------------------- Office 2016 Visio Pro Volume License MAK Key(s): Product Key(s)------------------Remaining Activation Counts Not available right now.! ------------------------------------------------------------------------------- Office 2016 Project Pro Volume License MAK Key(s): Product Key(s)------------------Remaining Activation Counts Not available right now.! ------------------------------------------------------------------------------- Office 2016 Standard Volume License MAK Keys(s): Product Key(s)------------------Remaining Activation Counts Not available right now.! Office 2016 Pro Plus Retail MSDN Edition Direct Download ISO Links [MULTI]: http://bit.ly/1XvVV3m Office 2016 Pro Plus VL VLSC Edition Direct Download ISO Links [MULTI]: http://bit.ly/1VJI8os How to Activate Office 2016 Via Phone: http://bit.ly/1LCAwOH WebAct By Ratiborus - MS Online Retail Keys Activation Application Alternative To Skype Call: http://bit.ly/1Q7xVxm Notice: **If Remaining Activation Count (+) you can activate the Office 2016 Directly ONLINE [Internet ON] **If Remaining Activation Count (0) you can activate the Office 2016 VIA Skype OFFLINE [Internet OFF] http://www.nsaneforums.com/topic/252378-office-2016-rtm-activation-via-phone-or-kms/ Office 2016 Phone Activation Via Command Line Instruction: 1. Open any Office 2016 Application first time and close it. 2. Right click the start menu and choose 'command prompt (admin)' 3. Type this script and hit Enter: --------------------------------------------------------------------- For 32-bit versions of Office on 32-bit versions of Windows or 64-bit versions of Office 2016 on 64-bit versions of Windows the script is: cscript 'C:Program FilesMicrosoft OfficeOffice16OSPP.VBS' /inpkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx --------------------------------------------------------------------- If you are installing the 32-bit version of Office on 64-bit versions of Windows the script is: cscript 'C:Program Files (x86)Microsoft OfficeOffice16OSPP.VBS' /inpkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx (Note:Where xxxxx-xxxxx-xxxxx-xxxxx-xxxxx is the Product Key.) --------------------------------------------------------------------- 4. Open any Office Component such as Word 2016 5. When MS Office activation wizard then hit Activate by Phone option 6. You will get Installation ID in this step 7. Call Microsoft Free Call Center and get the Confirmation ID Read carefully details about how to deal with robot speaker By Skype: You will see some toll-free phone numbers which you can call. UK Free Call Skype Dial Number [+448000188354] l USA Free Call Skype Dial Number [+18007548300] l Worldwide telephone numbers: https://www.microsoft.com/en-us/licensing/existing-customer/activation-centers.aspx * Make sure have a microphone plugged into your PC in order for the dial pad to work ! * # If you don't have microphone plug in any JACK into your motherboard headphone port & use your soundbox to hear voice or use Android Phone with Skype installed on phone.# Full Skype conversation & respond the right answer to order to get successfully verification: Verification Numbers: For security reason please enter the following number using your touch-tone pad. Dial the numbers using touch-tone pad robot speaker has given to you. --------------------------------------------------------------------- Press one as a home user and two if you are a business customer with a volume license agreement. DIAL 1 using touch-tone pad Press one if you have your Installation ID available if not press 2 DIAL 1 using touch-tone pad If you want to to activate Microsoft Product press one now if you activate office for Mac press two DIAL 2 using touch-tone pad --------------------------------------------------------------------- In this stage robot Speaker will ask your 9 group of Installation ID dial one by one using touch-tone pad Finally speaker will ask you last question: On how many computer is your product currently installed? *** DIAL 1 using your touch-tone pad.. *** In the end you will get Confirmation ID just type the ID in the activation wizard confirmation ID sectiction. november_ra1n
KMS service set up and running, all the recommended updates applied (to handle possible activation issues for Windows 8 etc)
Microsoft Office 2013 Standard deployed on the server mentioned above and on workstations on intranet, volume licensing in effect (proper KMS key for activation of Microsoft Ofice 2013 has been entered).
Problem: I can't activate MS Office 2013 installation running on the same server where KMS service is being run.
There are no entries in KMS event log related to this failure.
Everything was restarted, reinstalled etc several times already (including installing 32-bit and 64-bit versions of the Office).
Note that KMS service works fine. All the workstations activate their MS Office 2013 without a single glitch. However, the installation on the server itself refuses to use KMS.
Firewall is set up correctly. Host name is provided correctly (via 'cscript ospp.vbs /sethst:hostname', I tried all the hostnames relevant, starting with that working for activating from workstations). All the other documented required checks/actions are performed as well prior to activating.
Judging by what I include below, ospp.vbs hints the above can't be activated via KMS. Is it indeed the case (i.e., I should use MAK activation instead), or I am still missing something?
I followed the KMS troubleshooting hints and related articles, and currently on Technet there are no advice pieces whether the above is at all possible.
Output of slmgr.vbs /dlv 2E28138A-847F-42BC-9752-61B03FFF33CD:
Output of cscript ospp.vbs /act
Output of cscript ospp.vbs /dstatus
Konstantin Boyandin
Konstantin BoyandinKonstantin Boyandin
3 AnswersProduct Key For Microsoft Office
Installing the Hotfix from KB2885698 worked for me. Do give it a try.
Michael Hampton♦
Produkey
181k2828 gold badges337337 silver badges668668 bronze badges
KnaveTKnaveT
Office 2013 seems to use DNS lookups exclusively for identifying its KMS server. That was not the case with earlier KMS-activated versions of Office. What that means is that you cannot use names like localhost or 127.0.0.1 as your KMS server. You actually have to use the full ActiveDirectory/DNS name of your KMS server even if it happens to be the same machine. Oddly enough the Windows 7 activation script does not exhibit this behaviour.. I haven't tested Windows 8 or 8.1 yet.
Before you attempt Office 2013 activation, please make sure that you can DNS look up your KMS host (even if it's the same machine!) with the nslookup command on the host where you're trying to activate Office 2013 (yes, even if it's all on the same machine).
Finally, do not specify the port number with cscript ospp.vbs /sethst. The command isn't smart enough to understand that ':1688' is a port number reference and will literally use 'hostname:1688' as the hostname, instead of 'hostname' as the hostname and 1688 as the port number. I believe there's a separate command-line switch that sets the port, but you don't need to set it explicitly unless you actually attach the KMS service to a TCP port other than the default 1688.
RoubenRouben
I had to open the firewall on the kms server. The default port is 1688 tcp, but i found an inactive application available in the firewall settings.After enabling this option the kms worked as expected and armed the office installations after 5 successfull connections.
user201424user201424
protected by Michael Hampton♦May 23 '15 at 21:54Partial Product Key Khgm9 Kmspico 7
Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead? Not the answer you're looking for? Browse other questions tagged windowsmicrosoft-officekms or ask your own question.
Azure uses the following KMS endpoints for Windows product activation of Azure Virtual Machines:
Azure VMs will activate using the Azure KMS service if all of the following are true:
Windows activation works the same way regardless if the VM is using Azure Hybrid Use Benefit (HUB) or not.
Note that while using an Automatic Virtual Machine Activation (AVMA) key may work on some Azure VMs, the use of AVMA keys is not supported because not all Azure hosts are guaranteed to support it. So while it may work initially, when the VM moves to a different Azure host when deallocated and started, when the Redeploy option is used, or when planned maintenance occurs, it may end up on an Azure host that does not support AVMA.
Run slmgr.vbs /dlv from within the VM to check #1 and #2 above. In the example below, VOLUME_KMSCLIENT is what tells you a KMS client setup key was used, and Registered KMS machine name: kms.core.windows.net:1688 is what confirms that it is configured to activate against the Azure KMS service. Note that the KMS endpoint differs for public versus national cloud regions as listed at the beginning of this article.
If slmgr.vbs /dlv shows RETAIL channel, run the following commands to set the KMS client setup key for the version of Windows Server 2016 being used, and force it to retry activation.
For example, for Windows Server 2016 Datacenter, you would run:
Stalker shadow of chernobyl console co…. This step is not necessary for VMs created from the Windows Server 2016 gallery image, as the gallery image has the appropriate KMS client setup key already configured.
For activation issues involving Windows Server 2016 VMs failing to activate despite having the KMS client setup key configured, or for activation issues with Azure VMs using other versions of Windows, please review the remaining steps below.
Windows VMs should be configured with the KMS client setup key for the version of Windows being used, and have connectivity to port 1688 at kms.core.windows.net in order to activate successfully.
If you are using site-to-site VPN with forced tunneling, please see Use Azure custom routes to enable KMS activation with forced tunneling.
If you are using ExpressRoute with a default route published, please see Azure VM may fail to activate over ExpressRoute.
If your Azure VM experiences Windows activation failures, please try the following steps to resolve the issue. An example of an error message you may see is:
Note that when the grace period has expired and Windows is still not activated, Windows Server 2008 R2 and later versions of Windows will show additional notifications about activating, the desktop wallpaper remains black, and Windows Update will install security and critical updates only, but not optional updates. See also the Notifications section at the bottom of the Licensing Conditions TechNet page.
Steps to Troubleshoot Activation
If you are still unable to activate after attempting the above steps, let us know in the comments or contact Azure support.
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |