I gave it a whirl as it seemed to be straightforward to use. My aim is getting Word 2019, Excel 2019 and Powerpoint 2019 installed for Windows 8.1 x64. I mounted ProPlus2019Retail.iso (german) to the virtual drive F:\ and ran both YAOCTRI_Configurator.cmd and YAOCTRI_Installer.cmd. That's what I got: Spoiler ============================================================= Source : "F:\" Version : 16.0.10730.20102 / Arch: x64 / Lang: de-DE Channel : Monthly CDN : 492350f6-3a01-4f97-b9c0-c7c6ddf67d60 SKUs : Excel2019Volume,PowerPoint2019Volume,Word2019Volume Excluded: OneDrive Updates : True / AcceptEULA : True / Display : True PinIcons: False / AppShutdown: True / Activate: False ============================================================= 1. Install Now 2. Exit ============================================================= Choose a menu option: 1 ============================================================= Preparing... ============================================================= ============================================================= Running installation... ============================================================= ============================================================= Installation failed. ============================================================= Press any key to exit. I assume YAOCTRI doesn't work for my Windows 8.1 x64 or I need to do an additional step prior to running it. (Microsoft Office 2010 had been on this machine before, however I removed it thoroughly.) Any suggestions? Thanks in advance.
@2zyz2x: The problem is that you are trying to install 2019 SKUs on Windows 8.1: Code: SKUs : Excel2019Volume,PowerPoint2019Volume,Word2019Volume
No, it's not those 2019Volume SKUs are for licensing, the actual installed SKUs are 2016 Retail equivalents
There are two Click-To-Run Non Task Errors: ErrorCode": 0 "ErrorMessage": "", "ErrorDetails": "", "ContextData": "{\"message\":\"Unexpected parameter format: baseurl.16=J:\\\" version.16=16.0.10730.20102 productstoadd=ExcelRetail.16_en-US_x-none|PowerPointRetail.16_en-US_x-none|WordRetail.16_en-US_x-none ExcelRetail.excludedapps.16=onedrive PowerPointRetail.excludedapps.16=onedrive WordRetail.excludedapps.16=onedrive flt.useexptransportinplacepl=disabled flt.useofficehelperaddon=disabled flt.useoutlookshareaddon=disabled \"}"} ErrorCode": 17100, "ErrorType": "", "AppVErrorSource": "", "ErrorMessage": "", "ErrorDetails": "", "ContextData": "FillScenarioParameter returned failure."} Five Experiment Liblet errors: Office Experimentation failed to get endpoint URL Registry value not found {"Path": "Microsoft.Office.Experimentation.Registry", "Key": "PerpetualLicenseInfo"} Registry value not found {"Path": "Microsoft.Office.Experimentation.Registry", "Key": "PerpetualLicenseInfo"} Registry value not found {"Path": "Microsoft.Office.Experimentation.TasPersistentStore", "Key": "ProviderId"} Registry value not found {"Path": "Microsoft.Office.Experimentation.TasPersistentStore", "Key": "ProviderId"}
@2zyz2x @sidjames45 Fixed, thank you it was a last minute change to support source path with spaces, but i didn't verify it against mounted .img drive letter
Unfortunately, I'm not allowed to post the log yet. P.S.: It works with the revised YAOCTRI bundle, fantastic!
...YATYAP... (yet another thank you abbodi1406 post) First up, after reading dozens of detailed technical posts by you in this thread, I have to say that little bold part made me laugh so freakin' hard, I nearly fell out of my chair... So thanks for that in the first place. Well, for somebody who doesn't use Office much, you certainly cared enough for people who do use it, and made a very fine tool with "YAOCTRI" !!! So nice in fact, that I now have to look for something else to do on this rainy day, that I had actually reserved for "testing and reading up on what this Office 2019 is all about", which was actually overdue since around September (been a bit busy). Downloading the .img from the excellent first post and running YAOCTRI worked flawlessly, I think I was done in 10 minutes (which was around 1% of the allotted time). Well, reading the nearly 1500 posts here nibbled away another 5 hours, but now what am I going to do... Seriously, a big thanks to all kind people that have provided the very clear info and tools in this thread, it has been a lot of fun!
@oliverjia Sorry about that, this change was just a one line fix in the scripts, i didn't feel the need to give it new version number i do intend to use versioning in the future @chlynx all installed products are Volume you can install Project or Visio from either of the menus: 1. Install Product Suite press 5 to turn Project Pro ON, then 1 to turn Office 365 OFF, then press 0 to proceed 2. Install Single Apps press 5 to turn Project Pro ON, then turn OFF all other apps, then press 0 to proceed
Downloading img and installing old version of Office 2019 from img is not the best way to install Office 2019. The best way is to install online or download the latest version and install the latest version offline (both ways supports wotok cmd on windows 10 for several months). The best way install using YAOCTRI, do not download img, but download the latest version of Office 2019 using ODT or wotok or manual.
Is it possible to convert a 2019 Retail img/iso to VL img/iso or do you have install first to convert? C2R-R2V wants an installed version. I would like to automate installing 2019 including the latest patch Tuesday updates and activation via KMS. With Office 2007 Professional Plus, I use a shared folder that has the SP3 base + the latest updates for the current month. The install runs unattended via a config.msp. I would like to do something similar with 2019 or with a version of Office that isn't EOL.
OfficeRTool is (and will always remain) the mother of all Office customization scripts and tools possessing online and offline installation features. All other Office deployment scripts are based on this tool and ratzlefatz was the first to implement Click-to-Run technology research work in practical use, providing us the way to install Office 2019 on Windows 7 & 8.1. The amount of hard-work that has been implemented in this script makes OfficeRTool a rare gem in the scripting world.