I don't understand all that hassle to have automatic renewal of activation, 180d is half year, and your computers won't explode if activation expires, it only notices about it when you start office products, just double click [your preferred kms activator here] and all is good!
ratzlefatz & qwelpal Thank you both for the O2016RTool and the KMS_VL_ALL tools respectively - I've managed to get Microsoft Office 2016 activated successfully (Microsoft Office 2016 MSDN EN-US x86/64 ISO) but unfortunately not without having huge problems at first, as I could not get it to work on an "execute anywhere" basis whilst assuming that was the case (yes, silly me), so after an hour or so of pulling my hair out as to trying to figure out why the programs have failed to work, I then decided to move the KMS_VL_ALL and the O2016RTool files to the following directories: Code: C:\Program Files\Microsoft Office C:\Program Files (x86)\Microsoft Office ...and what do you know? It worked, and I managed to get it set up for auto-renewal when the Microsoft Toolkit application by CODYQX4 failed to recognise the Microsoft Office 2016 installation, and thus I could not use the Microsoft Toolkit application to activate the office suite.
anyone have issues with that there are no shortcuts in start menu? on win 10 64bit. the shortcuts are there in C:\ProgramData\Microsoft\Windows\Start Menu\Programs, but does not show up in start menu
KMS VL All (in my sig) doesn't need a scheduled task. It uses qad's SppExtComObjPatcher and KMS renewal will occur as per normal KMS behaviour, every seven days. Also it uses Smart Activation, whereby it performs a lot of checking routines to detect how installed Win/Office is activated, and will skip Retail/MAK activation etc. I'm not sure if some may be confusing KMS VL All by abbodi and KMS VL All by qewlpal. qewlpal's solution uses a scheduled task to run the script at each logon. Indeed KMS VL All (abbodi) had a big update yesterday, specifically addressing Office 2016 C2R issues. KMS VL All (abbodi) is a great install and forget KMS solution, see usage and brief explanation links in my sig.
I have installed 32Bit Office fur sure, but if I use that code, I get a message: (I have checked path, and file is there, but I get these message anyhow. And yes, I have start command prompt with admin rights.) Where is my fault? ****************************************************** Edit: I have done it now, by manual changing dir and type: Code: cscript /nologo ospp.vbs /unpkey:BTDRB ****************************************************** Before I installed complete Offife 2016 preview suite, I have installed single components and activated by KMS. Could you please post the product key characters for single components to uninstall those product keys, too? Thank you.
And whatever you don't request or post them at MDL. Against forum rules. And what is wrong with the default KMS behavior (as designed by MS) of renewal every seven days anyway?
Product Name ----------- KMS VL - Partial Key "Office 2016 Professional-Plus" - WFG99 ---------------------------------------- "Project 2016 Professional" ----- G83KT "Visio 2016 Professional" ------- RJRJK ---------------------------------------- "Access 2016" ------------------- QPFDW "Excel 2016" -------------------- 7FTBF "OneNote 2016 For Business" ----- XW3J6 "Outlook 2016" ------------------ 6MT9B "PowerPoint 2016" --------------- BY6C6 "Publisher 2016" ---------------- 8K837 "Skype For Business 2016" ------- DDBV6 "Word 2016" --------------------- 3PFJ6
RTM Versions: C2R 16.0.4229.1024 and MSDN-ISO 16.0.4266.1003 . In case someone is unsure, if downloaded Click2Run-version 16.0.4229.1024 is less worth or older than MSDN-ISO 16.0.4266.1003 or even this C2R is still a preview and MSDN-ISO can be only the correct RTM version: VNEXT 16.0.4229.1024 is RTM and will be updated in the future, so it is only a difference in numbers, not in functionality
There is only a difference if you installed from MSDN-ISO. Here Trial-key is used. After converting to VL you need to un-install KMS_VL keys and these are in the above list. You can check with "cscript /nologo ospp.vbs /dstatusall" for yourself what was installed and is found by Office Software Protection Platform. Watch status report for found products and their partial keys.
But no one has told you really why is not allowed to request for MAKs. And it is due to they are STOLEN keys. Any place on the Internet where you could find MAKs they were stolen somehow. Those MAKs were stolen from enterprises and/or individuals who already payed for those. Now you have the main reason why they are not allowed here in MDL.
The O2016RTool always downloads the non 365 version, how do I download the "OFFICE 365 Pro Plus" Click to run or Full Offline setup through the O2016RTool ???
YES, that's correct. No need to change this. Office Professional Plus has full functionality. No difference to O365. And without Abo, Office 365 is useless and having an Abo, you can download Office from your Office useraccount. So I didn't get what you mean by requesting O365.
Very good and useful hint - thanks! Now I see many older Office-Suites (15) but unlicensed and no product key available. Only that, for the current Off2016 Pro. plus. So for that all is okay. But where are stored that older Office Suites and how to delete them ? I think, you know for sure
UPDATE: Since O2016RTool version Sep, 27 the procedure below is not needed anymore. Not needed Office 2016 licenses will be removed during Retail2VL conversion process. ===================================================================== Each Office installation and activation is stored in the following files and is always added but NEVER removed: (ask MS why these dumbo's didn't include remove in the un-install routines) "tokens.dat", "cache.dat" and "data.dat" (data.dat may exist from Windows 8 onward). Stored location: Windows 7 -> "C:\Users\All Users\Microsoft\OfficeSoftwareProtectionPlatform" and "Cache"-subfolder Windows 8.0 -> "C:\Windows\System32\spp\store\1.0" and "Cache"-subfolder Windows 8.1/10 -> "C:\Windows\System32\spp\store\2.0" and "Cache"-subfolder Now comes the dangerous part! To remove all the references of old Office installations you can only delete these files. Doing this invalidates your Windows, Office and Store Apps activation. You must redo Office conversion to VL to insert certification license files and then you must activate Windows, Store Apps and Office again. This can (but won't in most cases) lead to a unactivated System. Then you must clear all the mess and do a new, fresh system setup. There is no other solution to get rid of old Office references. If it's too dangerous then leave all as it is. I will give no warranty that this will work on your system. A full backup is recommended in case you want to go back. As little safety procedure you can rename the *.dat files to *.dat.old and revert back if it didn't succeed. You are doing that all on your own risk.