Discussion in 'Microsoft Office' started by s1ave77, Jul 19, 2015.
No, RTM of office 2016 is said to be released this Fall.
Yeah, you mean via OSPP /unpkey: i guess.
Problem is the Professional Non-Plus online version is shipped without it for instance and it needs to now the install path.
SLMGR handles it perfectly . So it's foolproof, at least on Win 8 up.
Not sure about office 2016, but Win 10240 does look like it's RTM by traditional meaning. It's said to be the one that OEM and gold partners got a few days ago.
ratzlefatz and mine hopes are also with a proper Volume Version, not that dreaded and sometimes simply refusing C2R CRAP!!!!!
Please add a hint in How-To regarding Office 16 on Win 7 playing 'Extrawurst' .
Since it uses the fallback path it can't be handled by the auto-routine (SLMGR doesn't know it) and needs the manual Uninstall via OSPP.
People should make sure to not install Professional Non-Plus there, or they need to be guinea pigs for the project .
Nice and informative thread, it should be made sticky!
You need to login to view this posts content.
No change unfortunately: every 2 hrs event 8233.
Edit: On running the command "slmgr /sai 43200" I get a warning. See attachment. It's in Dutch and means something like "KMS interval can only be set on a KMS computer that is activated".
Downloaded latest office 2016 converted and activated under 10240.
I read all your posts again and just summarize what I have understand:
You un-installed Office 2013 32bit Volume License Version
You installed Office 2016 Professional 64bit Preview not ProPlus, right?
-> What installation method did you use?
-> Download from MS-Office-Preview-Homepage?
-> Or WEB-INSTALL using JATDevice?
You successfully activated using KMSpico and de-installed KMSpico afterwards
-> Why KMSpico de-install?
You noticed that "event 8233" appeared in event log. Prior this event entry was not there, right?
-> Possible reason: KMSpico de-install. Now you have no KMS server service active.
Entering "slmgr /sai 43200" gives error
-> ok my bad, this is for KMS server too and not for a client. Please ignore this.
But I didn't take notice to this text in event log:
AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = b322da9c-a2e2-4058-9e4e-f59a6970bd69
These ID's in the event belong to: Office 2013, not Office 2016
So during de-installation of Office 2013 something went wrong.
I suggest you de-install your Office 2016 and remaining traces of 2013 using info in post #4 and start a fresh install.
Here you should "upgrade" and install Office 2016 ProPlus (see post #2).
Better create a system image backup. Just in case you might need it.
Or you live with the situation and use the system as is. If I were you, I would start from scratch.
But you decide...
It already was installed, but I did'nt use it on the Preview.
Can't I remove all Office 2013 traces manually?
I only installed Project and Visio, any hopes of a successful conversion & activation?
I tried with both the manual cscript slmgr scripts (resulting in a "product key not found") as well as with the tool itself (it doesn't find office 16 since it's not installed - only visio+project).
Any ideas? If you tell me to simply dig deeper into the scripts of your tool I will, of course.
PS: I have (on Win81pro en-us x64) Office 2010 x86 Outlook and Office 2013 x86 rest-of-Office (Excel etc) installed and only wanted to add Visio+Project from 2016 to that mix.
Tested the KMS_VL_All script and the convert script. Both worked perfectly on my two machines. Previously I used the retail trial key to get 120 days, and now product activated with your solutions
thanks ratzlefatz and S1ave77
Edit: this is for office 2016 pro plus latest preview on Windows 10 build 10240.
Huih, the hardest possible mix available ... even MS refuses to support this .
JATD by design checks every installed Office 14, 15 and 16 generally for Office, Project and Visio and in my tests recognized the Project installed without Office.
Biggest problem is always when different Office versions get used. Additionally the Office 16 C2R crap is more difficult to handle.
In my tests Office 16 refused to install when it detects Office 15 . So i couldn't test this scenario.
Need a moment to check ideas.
Can confirm, in my tests to get a working paralel install of 14 and 15 there was a 70:30 chance to FUBAR the firstly installed .
Athough it might work it's never recommended.