"setup.exe" from Office Deployment Tool prohibits installation of non standard channels. Therefore new method using "OfficeClick2Run.exe" will stay. You can edit "start_setup.cmd" to set Office products to add and to exclude. Read post from abbodi1406. He described method in great detail.
that's not true, I use the old method all the time and it works. Nothing follows from this post, a great unnecessary haos. The old method is better, you can easily personalize the installation, through an xml file that works with each version. New method = too many combinations and unnecessary burying, Forcing each time to set up the entire installation for each version. Change to a big minus
Surely NOT with newest setup.exe from current ODT. I can live with it. Last statement from me in this case.
when creating the office 2019 installer for some reason, visio installs as 2016: / and visio i project no activated
in the post you gave a silent word about what to do to exclude something from the installation or how to choose to install, for example, as 2019
A new OfficeRTool version (2018/June/22) was released today Function "(I) INSTALL OFFICE SUITES OR SINGLE APPS" - Bugfix - - Install of mixed, multiple products now possible - Office 2019 Preview install fixed - setup on 32bit/x86 Windows fixed No other changes were made. Download-links and checksums in OP were updated.
Select different setups and instead installing, let OfficeRTool (C) create file "start_setup.cmd". Then you can inspect batchfiles for how to setup products and excludes. If you rename each file to something more meaningful, you can build a collection of individual setups. Important "OfficeClickToRun.exe" command line parameters to look for: productstoadd= excludedapps= Additional infos, see post from abbodi1406.
you did not understand. The cmd file does not contain any information that was contained in the xml file. there is only given where to run the installer file. It will be a better idea that the script will continue to use the xml file - easier to configure and everyone will understand. From my friend's post, nothing follows, no meaningful content, one great haos, I have read several times and I still do not understand it. There is no information on how to configure and where what contained xml, and creating something for every build from scratch is idiocy
Security Essentials detected a trojan "Skeeyah" at file:E:\OfficeRTool2018Jun22\OfficeRTool\OfficeFixes\win_x32\SppExtComObjPatcher.exe Is this expected? Downloaded 7z checksum is fine
YES, it's to be expected. All AV ("wrongly") present false! positives. Creators of Antivirusprograms are urged by Microsoft to check for and declare all these 'little KMS-Helpers' such as the one used by OfficeRTool (= SppExtComObjPatcher.exe) as Virus/Trojan/Hacktool. Goal: To confuse all who use them. If downloaded from links presented here at MDL it's safe. If downloaded from other sources it's wise to look for checksums.
Bugs However, it has important remarks that I think can be introduced: - the installer should detect automatically which location is running, because for example I have it on the F: \ drive and somebody else will have to edit this path manually again. - line 46 is unreadable because everything is in one line. It would be more convenient to give everything one under the other, it will be easier and easier to read - and it is important that the version also changes itself in version = and there is still an error that visio and project pro 2019 installs as 2016: /
OK, makes sense. Will think about it. Sorry, not changeable. All command line parameters must be together in one line. For better reading set your texteditor to autowrap the text. ?? The version/build changes already. version=%officebuild% variable is used to install correct version. Blame Microsoft for not changing brand name. Visio 2019 and Project 2019 were definitely installed! Maybe they will change naming in a later version. What helper?
this is the fault of the new method, because the old method correctly installs visio and project as 2019, the new installs twice for existing installations and two as new ones appearing as 2016
the error is already visible at the beginning I choose office 2019 installations and visio and project in the script is proposed as 2016 ProjectPro2019Retail VisioPro2019Retail yes it should be, using xml installs correctly
First: Please collect your error reports and write 1 post. I still didn't get where's your problem. Please elaborate. An example showing all steps you take and what result you expect would be nice. Again I didn't get it. What is this "Helper"? Where can I find it? Script shows all possible options based on the selected distribution channel. It starts with standard Visio 2016 and Project 2016 versions. Afterwards (using valid distribution channel and if Visio 2016/Project 2016 were not selected) it shows Visio 2019 and Project 2019 versions for selection. That's all fully described in the readme.pdf file. I've tested and 32bit install is working. If you have problems, then help me to reproduce them. But I need more info than your one line "not working" report. At all others out there: Anyone else having such problems and want to contribute?