I am managing to download and successfully run the VL conversion on the different builds but I am having problems with activation on the 365 variants. Using KMS Auto Net 1.4.3 (Ratiborus) the status is reported as activated okay (180 days) but when I start WORD for example it states that activation is required (functionality will be reduced in 1 day). The build is the correct 365 as specified and the PowerPoint morph feature is there. Just activation seems to be the issue for me? Thanks
Yes. On each test I ran both the "Force Remove Office C2R / MSI" utility in "Office 2016 C2R Install v5.3" (Ratiborus) as well as the MS "o15ctrremove.diagcab" utility. I imagine this should be a pretty comprehensive clean-up? Reboot performed also. I will have another go though and report back.
OK, "o15ctrremove.diagcab" is the MS-FixIt tool I meant. Just another -unvalidated- assumption / wild guessing: Did you use a local Windows user on that system or did you logon with a online MS-account? Using MS-account 'could' interfere with KMS activated Office 365 ProPlus because this version is a online subscription and is normally designed to get activated by MS online accounts. I always logon and work as local user (who has admin rights) on my systems.
In my case: I try ONLINE C2R installer ProductreleaseID=ProPlusRetail from your program and I can use Morph and Designer, same in the version ProfessionalRetail (version 16.0.6965.2063).
@ratzlefatz, Initially I thought it was like Ratiborus' where you decide what to download then install it, but only after the full download I realized that it downloads everything and you install what you want. The explanation you provided in post 987 makes it clear. However, you may wish to add a comment that the downloaded package includes both MS Office 16 and 365 releases. All in all, excellent work, thank you.. P.S. - I created a simple presentation using the "Morph" function. But as I expected, it did not work when I tried to play it on an other computer that has Office 2016!! I hope MS will release this nice functionality for all office releases.. - The installation reported Office 365 Ver: 16.0.7070.2022 and refused to install second language proofing tools, then (while trying various office 16/365 proofing tools) it went trough Office installation process and now it reports the "removed" Office 2016 version but it has the Morph function!!??
Thanks all and to Ratzlefatz in particular. I now have the Morph feature too in a successfully VL converted and activated version (using the O2016RTool July Beta for ALL steps.) I am somewhat confused though that the configure32.xml states... <Configuration> <Add OfficeClientEdition="32"> <Product ID="O365ProPlusRetail"> <Language ID="en-US"/> </Product> <Product ID="ProjectProRetail"> <Language ID="en-US"/> </Product> <Product ID="VisioProRetail"> <Language ID="en-US"/> </Product> </Add> <Display Level="Full" AcceptEULA="TRUE" /> <Updates Enabled="TRUE" UpdatePath="h.t.t.p://officecdn.microsoft.com/pr/492350f6-3a01-4f97-b9c0-c7c6ddf67d60" /> </Configuration> yet the installed version shows "Microsoft Professional Plus - 2016 16.0.6965.2063" i.e. the xml refers to O365 as opposed to Office? I'm not complaining inasmuch as I have what i was looking for although still not convinced I fully understand this complex build / deployment mechanism incorporating C2R, 365, Office, Retail, Current, Insider, Preview, Deferred, Business as so on. If anyone can post a link to a simple document that unpacks this in simple terms I would be very grateful.
Very helpful.One further question if I may and hopefully can be answered easily given my limited knowledge of some of this stuff! I have used both Codyqx4 toolkit and Ratiborus before and note that a task is scheduled that runs ensuring that the expiry of the activation is constantly reset. in case of Codyqx4 it is at every logon on so the activation is typically always at 179 or 180 days for a regularly used computer. The Ratiborus tool seems to do this every 10 days. How is this managed with O2016RTool? Or do we need to managed this with separately somehow? Sorry if this is just a basic gap in my understanding but I could not see anything in your otherwise easy to follow documentation, which talked about this.(PDF) Thanks again.
@ratzlefatz ..Referring to your earlier post explaining the fact that the 365 builds (current and 1st release) will be reported as "365" if one of the apps is opened BEFORE VL conversion and then subsequently appears as Office perpetual, although still retaining the features of the 365 build (e.g. Morph in PPT), i have a question. On subsequent updates, will the 365 product ID be respected and updated as such or will the MSO2016 perpetual staus be recognised and thus subsequent updates will be limited to security / bug fixes only. i.e,. the new feature element of the 365 buils model will be lost? Many thanks.
Configuration and entries in the Registry are O365ProPlusRetail. I assume you still will have all Office 365 ProfessionalPlus features active after the next update, which I expect this week at Patch-Tuesday. So will will know real soon.
Excellent! Have just online updated VL Converted 16.0.7070.2022 (O365) to 16.0.7070.2026 and all seems fine. The update was flawless and the individual Program Application IDs have updated from 16.0.7030.1012 to 16.0.7030.1016. Build specific functionalitity e.g. Morph in PPT is still there and functioning normally. All things being equal the tool looks sound going forward with the 365 builds. The test was with Current but I would imagine Insider will be fine also.
Hi! I would like to ask how can I enable the morph transition in PowerPoint 2016. I am using First Release for Current Channel (Office Insiders) to the latest version 16.0.7070.2026. Do I still need to register as an Office 365 subscription account? Thanks.