Hi, Just to clarify the use of the O2016RTOOL: After activating Office 2016 Proplus with KMS Server (Internal O2016RTool-KMS server - VLMCSD from hotbird64), is there any need to reactivate it again after 30 days? Or is the process automatic?
- Every KMS-activation always has a valid duration of 180 days ( = 6 months). - At upcoming license ending your Office will show a reminder to renew. - Then you should renew for another 180 days. - But you don't have to wait for Office to remind you, you can renew at any time. O2016RTool doesn't have an automatism to renew. You have to manually take care for yourself.
I don't know of any possibility to do only a single backup (and restore) of an Office 2016 activation. At the present moment, only a full system Image Backup (such as done with Acronis TrueImage) can save the activation.
Office 2016 16.0.6366.2062 activation Hi, Ratzlefatz I downloaded and installed Office 2016 16.0.6366.2062 by O2016RTool (Dec 20 version) in Windows 10 Insider Preview Build 11102, but KMS failed to activate (everything OK in Windows 10586). Am I wrong ?
What I did: - Use O2016RTool to install Office 16.0.6366.2062; - Don't convert to Volume, delete token file in C:\Windows\System32\spp\store_test\2.0 (shutdown service Software Protection first); - Convert to Volume version; - Activate with KMS; - Re-activate Windows (using commands: slmgr /upk; slmgr /ipk ...; slmgr /atp ...)
It is definitely "cleanospp.exe" from MS-Office 2016 FixIt-Tool which changes an existing "tokens.dat" in a way, that KMS activation on Win10 versions >= 10586 fails. For sure it worked with former Win10 versions, so something in Windows has changed here. "cleanospp.exe" is dated year 2014 and there exists no newer version. I modified O2016RTool in my internal test just to bypass/not run "cleanospp.exe" and guess what happened? KMS activation succeeded! To help yourself, you can modify O2016RTool lines 855 / 859. Place "::" at the beginning to deactivate. Code: ::=============================================================================================================== echo: echo Cleanup - Removing Current Office 2016 - Licenses echo: :: "%o2016rtoolpath%\OfficeFixes\%winx%\cleanospp.exe" -PKey echo __________________________________________________________________ echo: echo: :: "%o2016rtoolpath%\OfficeFixes\%winx%\cleanospp.exe" -Licenses ::=============================================================================================================== "cleanospp.exe" is used for removing all the retail-/trial-product-keys and -licenses during Retail2VL conversion. It doesn't harm if all the retail traces remain in the system. So a quick - but not so elegant - solution will be to simply skip the cleanup and remove only any existing retail-/trial-/grace-keys. But I don't like this idea. I will try to find a solution to get cleanup working again.
--2016-02-03 22:24:25-- (try:87028) h t t p : / / officecdn.microsoft.com/pr/492350f6-3a01-4f97-b9c0-c7c6ddf67d60/Office/Data/16.0.6366.2062/stream.x86. x-none.dat.cobra Connecting to officecdn.microsoft.com (officecdn.microsoft.com)|212.205.126.17|:80... failed: Bad file descriptor. Connecting to officecdn.microsoft.com (officecdn.microsoft.com)|212.205.126.9|:80... failed: Bad file descriptor. Retrying. Is it a bug?? (or a future..)