Give me a script to put it in source ($oem$) and put office in support .... to install with Windows silent ... no auto activation .. I activate it after installation .. ....win x64 thanks
[HOW TO] Step 01. Download Office Select 2013 with SP1. View attachment Office_Select_Edition_2013_SP1_RuEn_MLF-KROKOZ.7z Step 02. Download language pack(s). View attachment MONOVA.ORG Office_Multi-Language_Pack_2013_SP1_Multilingual_-_Volume_Untouched.torrent.7z Step 03. Create a folder "Office". Then Extraxt/Rename and cut/paste into "Office": DVD9_Office_Select_Edition_2013w_SP1_W32(32Bit)_RuEn_MLF-KROKOZ -> 32 DVD9_Office_Select_Edition_2013w_SP1_64Bit_RuEn_MLF-KROKOZ -> 64 Step 04. Delete the following language packs and replace with your language packs. a. dcf.xx-xx b. groove.xx-xx c. office.xx-xx d. office32.xx-xx or office64.xx-xx e. osm.xx-xx f. osmux.xx-xx g. proofing.xx-xx Step 05. Delete unwanted edition and its language pack. (Please refer to [Available editions and Language Packs]) e.g. Office\32\word.ww and Office\32\word.en-us Step 06. Delete edition language pack and replace with your edition language pack. e.g. Office\32\word.en-us -> Office\32\word.fr-fr Step 07. Edit *.ww\config.xml as follows. (Please refer to Note 1) e.g. Word.ww\config.xml Code: <Configuration Product="Word"> <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> <Setting Id="SETUP_REBOOT" Value="Never" /> <Setting Id="REBOOT" Value="ReallySuppress"/> </Configuration> Step 08. Add Office folder in Windows ISO\support. Step 09. Add $OEM$ and EI.CFG in Windows ISO\sources. Step 10. Save as new file. [Available editions and language packs] [Suites] 01. proplus.ww:standard.ww/Standalone (Please refer to Note 3) 02. prjpro.ww:prjstd.ww/project.xx-xx 03. vispro.ww:visstd.ww/visio.xx-xx [Standalone] 01. access.ww/access.xx-xx 02. excel.ww/excel.xx-xx 03. infopath.ww/infopath.xx-xx 04. lync.ww/lync.xx-xx 05. onenote.ww/onenote.-xx-xx 06. outlook.ww/outlook.xx-xx 07. powerpoint.ww/powerpoint.xx-xx 08. publisher.ww/publisher.xx-xx 09. sharepointdesigner.ww/sharepointdesigner.xx-xx 10. word.ww/word.xx-xx Note 1: ATM I can do Single Language only for I do NOT use Office 2013 and NOT familiar with them. You can edit config.xml to suite your own needs if you would. Note 2: I think this is better. Only one set of universal files for all editions. admin catalog dcf.xx-xx groove.xx-xx office.xx-xx office32.xx-xx or office64.xx-xx osm.xx-xx osmux.xx-xx proofing.xx-xx updates autorun.inf readme.htm setup.dll setup.exe Note 3: For Office 2013 suite, if you choose ProPlus or Standard, please delete Standalone editions (.ww), but keep corresponding language packs (.xx-xx). e.g. delete Word edition delete word.ww but keep word.xx-xx
It is exactly what I want, it is perfect, I will be able to create my ISO of installation personalized, I am sad that my pseudonym does not appear in script
Yes I come from seeing that it is in the SINGLE-LANG, thank you very much you are the best !!! And the RTM-Slipstream_2014.05.11 ?
@ xinso: Unbelievable but true: The issue I had / have is truely a (small) bug in your script. Let me explain it to you... 1) as I had some free time today, I wanted to find out the reason of this whole mess, which I successfully have. After fighting through Dependency walker stuff (this revealed the only small issue my system has: it's not finding the ieshims.dll [located under %programfiles%\Internet Explorer\], which seems to be a rather wide / popular issue), various file diffs of a working and a non-working system (including the relevant parts of the windows registry), reinstalling all c++ redistributables I was kind of disappointed that nothing helped in the beginning. Until I deleted the registry key, which qad had pointed out in his post a few pages back: Code: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\SppExtComObj.exe (This made the "The system cannot find the file C:\Windows\system32\SppExtComObj.Exe." thing disappear, where the problem was, that the Debugger executable was simply not present on the system.) 2) Why has this happened? The issue lies in my (probably too) organized folder structure. I've always copied your 7z file to the following folder... Code: D:\My Documents\SIK\Utilities\3 - KMS Activation\ ...extracted it to the name the file already has and executed "Install_and_forget.cmd" - which still results in: Code: Activating Office 15, OfficeProPlusVL_KMS_Client edition (***) ... Error: 0x80070002 The system cannot find the file specified. (SWbemObjectEx) 3) That is when I realized the error: Either the path is too long, contains spaces or what not, but the thing is, that both KMS-QadHooker.* are NOT installed / copied to %SystemRoot%\ when executing the Install*.cmd file from the said path... keep in mind, that we're talking of this folder here where the files are located: Code: D:\My Documents\SIK\Utilities\3 - KMS Activation\KMS-QADhooker_Localhost_V5-V6-O15-RTM-CTRw_RTM-Slipstream_2014.05.11_15.52\$OEM$\$$\Setup\Scripts\KMS-QADhooker\64 Keep also in mind, that this will effectively break SPPExtComObj.Exe from executing, because the registry key was created, but the needed files were not being copied. 4) Last but not least... everything runs and works fine when executing the Install*.cmd file from the path: Code: C:\KMS-QADhooker_Localhost_V5-V6-O15-RTM-CTRw_RTM-Slipstream_2014.05.11_15.52\ Activating Office 15, OfficeProPlusVL_KMS_Client edition (***) ... Product activated successfully. Glad that my system is ok and doesn't need a reinstall. And as I've said before: Keep up the good work!
So! I guessed. I remembered something.... Wait. Let me look it up and tell you. It's of Ratiborus old KMS tool... I forgot where it is now. It's about language. It happened when I run it from a copied folder that is quite long and the language is different with the System Locale. Like Code: KMS-QADhooker_Localhost_V5-V6-O15-RTM-CTRw_RTM-SELECT_Slipstream_2014.05.12_14.36 - Copy -> OK Code: KMS-QADhooker_Localhost_V5-V6-O15-RTM-CTRw_RTM-SELECT_Slipstream_2014.05.12_14.36 - 複製 Run from desktop -> Activating Office 15, OfficeProPlusVL_KMS_Client edition (***) ... Error: 0x80070002 The system cannot find the file specified. (SWbemObjectEx) Run from C:\ -> OK. To conclude: It easily happens when the path is too long with space in between and especially in different System Language circumstances. HelFritz, You have something like me. Not easy to be careless and knocked out. Thank you by a 21-gun salute.
You are right! I always tested before posting. NOT by guessing. (But sometimes result may be different for some unknown reason. It was not my fault.)
Yah, I do remember several months ago with an AIO of mine when that unknown reason affected Single Language sku in Spanish. I will try again tomorrow to see if it happens again...
Ad 1) Good one. I didn't think about language / codepages. But that was not the solution to this problem. Ad 2) Yep, definitely. It drives me crazy when I don't understand such a simple thing... Again: Nothing to thank for. But to finally put an end to the story and to give you already a preview for your next release: Before Code: for /f "tokens=2 delims==- " %%P in ('wmic OS get OSArchitecture /format:list') do (copy /y %~dp0$OEM$\$$\Setup\Scripts\%QAD%\%%P\*.* %SystemRoot%\ >nul 2>&1) After Code: for /f "tokens=2 delims==- " %%P in ('wmic OS get OSArchitecture /format:list') do (copy /y "%~dp0$OEM$\$$\Setup\Scripts\%QAD%\%%P\*.*" %SystemRoot%\ >nul 2>&1) Sometimes things are easier than thought... EDIT: By the way... I'm using an english (en-us) OS.