1. Yes, you can install 83 SKUs of same source 2. Not directly, O365ProPlus has no volume licenses, MondoVolume licenses are needed to activate it, which will give partial features of Office 365 Pro Plus
@adric Office source files itself is not retail, but the setup exe files are only available for Retail SKUs you can use Office Deployment Tool to install Office 2019 Volume SKUs or use OfficeClickToRun.exe method to install any Volume SKU directly
True. The learning curve is rather steep, it's like reverting to vim instead of Notepad or pico (I mean, I adore vim, but that's just me). I really appreciate the work done for the impressing OfficeR tool. However, as far as user-friendliness is concerned, it's confusing. (The given readme.pdf adds little to it.) It might be just perfect for experts who know what they aim for, but for me I'm a bit of a loss. That's why I like YAOCTRI, I quickly arrive at a satisfactory result. I don't have to cope with distribution channels, build numbers... and will still get the desired result.
YAOCTRI worked flawlessly. Clear instructions. I chose 'install single apps' 1. apps are listed separately, and not as a single MS Office suite. does it affect functionality in any way? Will they activate using a single license? 2. what about uninstallation? individual control?
MS likes to boss around a lot; forced Windows update, forcing installation of all the Office Apps etc etc. Lets see what they are going to do in future.
1. I don't know, mostly yes but comparing ProPlus2019VL_KMS_Client_AE-ppd.xrm-ms with PowerPoint2019VL_KMS_Client_AE-ppd.xrm-ms as example, it seems that both have same feature policies for PowePoint 2. Separate controls
YAOCTRI is really nice. Just a thought: In the past one could choose a different path for the installation, instead of %ProgramFiles%\Microsoft Office\ something like %ProgramFiles%\Office2019\ for instance. Any chance of having that in YAOCTRI, too?
Two questions about yaoctri: When installing with a pre-made .ini file, will the installer script itself be unattended or menu based? It would be nice to be able to make an .ini file with unattended options set, but the installer.cmd itself has to run unattended also. The readme states that it is not possible to make a x86 .ini file on a x64 system. But is it possible to make the x86 .ini on a x86 system and use it for deployment on other x86 computers? In other words, does "system specific" mean "architecture specific" or do I misread it? And finally, I see people writing about downloading an "updated image". The links on the first page are static, it's still the same image as when it was released. I may assume you guys mean downloading by means of the several tools like ODT? Cheers.
No, it will be attended will see if i can add option for auto install Yes, as long as you use it on same Windows level (Win 10 or Win 7/8.1) so, system specific means same architecture and level You can use ODT, or OfficeRTool