I found a small error: If you change the name of the directory with the downloaded name and it does not have a number at the beginning, the script will not detect this directory. Earlier, I remember that it detected the directory.
I'm sorry, but you remembered wrong. Directory name always has to start with "16.0.." This check (line 1122) was in "OfficeRTool.cmd" script right from the beginning: Code: for /F "tokens=*" %%a in ('dir "%downpath%\" /ad /b 2^>nul ^| findstr /i "16.0"') do... It's used to filter Office download-folders in a bunch of others and create available downloads-list in OfficeRTool Install-section. Or do you mean "start_setup.cmd" ? But "start_setup.cmd" should work in every folder, regardless the naming.
No, I mean the main script. Can be done to detect a folder with a changed name that does not contain numbers? - of course, after entering the path to the folder with the new name
Next OfficeRTool will allow to enter a individual textpattern (not only fixed "16.0") to search for when package foldername is not found in download-directory.
A new OfficeRTool version (2018/July/29) was released today Function "(I) INSTALL OFFICE SUITES OR SINGLE APPS" -Enhancement- Implemented simple search function in input routine for downloaded packages. (requested by Winclub-pl) Any string/character can be entered and this will be used to search for matching package folder-names. This allows you to rename the default 16.0_xxxxx.yyyyy_ OfficeRTool foldername-structure to match your personal preferred storagename. Requirement: All package foldernames must be located in the download-path which is saved in OfficeRTool.ini. No other changes were made. Download-links and checksums in OP were updated.
Unfortunately, the implemented function does not work at all. It does not look for the downloaded folder with the changed name even though it is in the download place included in the .ini file - and here too a small suggestion to get rid of this requirement, and make it so that the script will find the downloaded files from anywhere - if the script will not be able to detect automatically then you will just need to enter the path to the folder Of course, we're still talking about detection under the "I" option
And it does this only in your special environment. Not true. If a package folder is saved in downpath retrieved from OfficeRTool.ini then it is found (if it has default name beginning with/containing "16.0"). If you are renaming this existing folder in downpath to somewhat else, then you must change search filter pattern before it is shown. Choose some string or character which is definitely in the changed folder-name and you will see the package. If you always save the packages in downpath from OfficeRTool.ini then no "super- special-searching-AI" is necessary. And if you always rename package-folder- name following the same structure, then you only need to enter one short search filter pattern to show.
Not sure if I should ask such question here, but can I KMS activate Office 365, or does it have some weird stuff behind it, that would make it difficult? Last time I tried to get 365 instead of 2016, it didn't go too well (been a while).
I do not know what to enter or modify. Anyway, the changes introduced are unintuitive, embarrassing, and that's not what I meant. Certainly you did not introduce anything from my suggestion, only a prosthesis from which no one but you will be able to use. According to my proposal: the script should itself find the package with the changed name after giving it a path with a folder containing the downloaded content. - no need to modify the script from the user's side
After you get this: Code: Download-path = "c:\test" List of available installation packages # Package No install packages found You press any key. You are not changing the script itself, but you must enter a search string here: Code: Download-path = "c:\test" Enter search pattern or enter x to abort >test Then you will get all packages which have "test" (non case sensitive) in their names: Code: List of available installation packages # Package 1 TEST#1 2 TEST-no.2 3 99Test 4 WinClub_test Enter package number # or enter 0 for new search pattern > For searching other package-names, just enter 0 and use another search pattern string (single character or single number or any 1 word combination) which is part of the package foldername. To get a little comfort, I can add "default search pattern" to OfficeRTool.ini. This will instantly give the package list if the folder-naming has a certain structure.
Retail2VL conversion tool by abbodi1406 and OfficeRTool can add KMS capabilities to Office 365 during conversion. Afterwards KMS activation is possible. Most Office 365 functions (e.g. Morph in PowerPoint, Black-theme) are available. Other paid functions which need online sign-in using Microsoft account (such as Onedrive with 1TB space) may fail. Some functions (such as Insights in Excel) need a trick to get it work.
the filtering method actually works and it's more convenient than giving the path to the folder The lack of information in the script may be misleading: Selecting 0 will search the folder immediately without having to filter. You can add information in the script that entering part of the name also helps
There is something missing in the OP. Install method... (Also there should be a space, the words are together) What is the difference between OfficeClickToRun.exe and ODT Setup.exe ? Which is better? Cons, Pros? Thanks! Nice Tool. Edit: Answer here too, i want to know the main difference... OfficeClickToRun or ODT Setup.
ODT Setup.exe = intermediate tool that read configuration.xml and verify all prerequisites, then launch OfficeClickToRun with the proper commandline parameters easier to handle OfficeClickToRun can be launch manually too, with the proper commandline parameters this allow to bypass "marketing" blocks, such as blocking Volume Office 2016 SKUs, or Office 2019 SKUs on Windows 7/8.1
@ratzlefatz I just wanted to take a moment and thank you for all the work, time, and effort you have been putting into this development. It has not gone unnoticed and you have made my life and the lives of so many here on MDL, so much easier when it comes to pertaining Microsoft Office.