I'm curious about whether MSO 365 offers significantly more improvements than MSO 2016 and whether updates to any version of Office impose more invasive telemetry routines. I ask because I've stuck with MSO 2016 now for nearly a decade. I did not upgrade from MSO after 2016 because while Microsoft Office 2016 and 2019 appear nearly identical at the surface level, the transition between them as well as more recent versions marked a significant shift in how Microsoft handles data collection and cloud dependency. In Office 2016 Telemetry was largely governed by the Customer Experience Improvement Program (CEIP). In this version, you could often disable data sharing via a single checkbox in the "Trust Center." It used a simpler telemetry agent that primarily reported crashes and basic usage stats to a local dashboard for IT admins rather than directly to Microsoft. In Office 2019 and later versions, Microsoft replaced the CEIP checkbox with three distinct levels of data collection: Required: Minimum data to keep the app secure and working. Optional: Additional info about how you use features. Neither: Historically harder to achieve without Group Policy or Registry edits. So in Office 2019, telemetry is more "baked-in." While it still supports the Office Telemetry Dashboard (an on-premises tool for IT admins), the background diagnostic data sent to Microsoft became more persistent and harder for an average user to fully opt-out of through the standard UI. Since then, Microsoft has gone further with telemetry , introducing "Connected Experiences" and other cloud services that weren't present in 2016. So while I comfortable using MSO 2016 for as long as I can, I'm weighing whether to install "security" updates since the software is no longer supported. However, I'm curious about other users experience with these "updates." Do they deprecate any Office features and/or impose more telemetry. Sorry for the long post....
So, how to add ohook to this? I am asking because I want to build an ISO containing all updates for 2016 so far and use that under Wine, and also take care of activation this way. Thanks.
@abbodi1406 Update 2: Hi, I did more testing with the installer created with the new script and everything worked fine. I tested it on a couple of virtual machines, as well as a couple of physical computers. No pending updates appear on any of them now. On the computer where the KB2880463 update initially appeared as pending, I used Office Scrubber, and after restarting, I reinstalled, and nothing pending appeared. So, if there's an old installation or previous installation attempts, it's best to remove that old/erroneous installation with Scrubber and do a clean install. I believe that a final installer is now created, which will no longer have any pending updates; at least according to my tests. I think you could update the .7z file of Office 2013 MSI Upsourcer to add this latest modification to your script. Thank you very much for your support.
With regard to Office 2010: What is the slipstream procedure for the separate language pack install DVDs? For example, let's say I have a fully slipstreamed install disc... Now I want to install "en_office_language_pack_2010_x86_x64_dvd_516538.iso" over my fully updated existing install, how do I update that ISO before doing so (for example, I see that the language packs have a Service Pack 2). Thanks
@mockingbird Update the language_pack iso the same you update Office iso however, if you want to update all langs, then you would need to download and extract languagepacksp2010-kb2687449-fullfile-*.exe for all langs otherwise, if you need one or few langs, then you delete the following folders for unneeded langs after extracting the iso OMUI.* PMUI.* VisMUI.* XMUI.*
Thanks. I tried the following: 1) Extract X16-37701.exe (en_office_language_pack_2010_x86_516850) to "C:\OfficeMSI" 2) Extract only the following files from "languagepacksp2010-kb2687449-fullfile-x86-en-us.exe" to "C:\OfficeMSI\Updates": Code: clientshared64mui-en-us.msp clientshared64mui-en-us.xml clientsharedmui-en-us.msp clientsharedmui-en-us.xml officesuitemui-en-us.msp officesuitemui-en-us.xml omui-en-us.msp omui-en-us.xml pmui-en-us.msp pmui-en-us.xml projectmui-en-us.msp projectmui-en-us.xml proof-en-us.msp proof-en-us.xml proofing-en-us.msp proofing-en-us.xml sharepointdesignermui-en-us.msp sharepointdesignermui-en-us.xml visiomui-en-us.msp visiomui-en-us.xml vismui-en-us.msp vismui-en-us.xml xmui-en-us.msp xmui-en-us.xml 3) Since these are already MSPs, I can omit running Extract_MSP_Office.cmd 4) Run "_OfficeUpsourcer2010.cmd" (v6 - I need Windows XP support) with this error resulting: Code: Warning: Important update KB2553347 ocfxca-x-none.msp is not detected Warning: recommended update KB2879953 rmaddlocal-x-none.msp is not detected ============================================================ ERROR: could not detect Office language Press any key to exit. Please advise.
KB2553347 ocfxca and KB2879953 rmaddlocal are needed for all products, regardless SP2 you can try that "Updates" way if you want, but you will be left out with old RTM files and SP2 msp files cached in C:\Windows\Installer also, Language Packs require osetup2010-kb4022208 and ospp2010-kb2883019 updates after SP2
Ok got it, I downloaded the following files: ocfxca-x-none_ea01b56460836086e46ac9135fa5ff094dd4b818.cab (KB2553347) osetup2010-kb4022208-fullfile-x86-glb.exe ospp-x-none_5d0c591708ab6fdb76553c0a2ca137dc3a8b7282.cab (KB2883019) rmaddlocal2010-kb2879953-fullfile-x86-glb.cab Z_rmaddlocal2010_kb2879953_x86_rmaddlocal-x-none.msp and Z_osetup2010_kb4022208_x86_osetup-x-none.msp extract fine with the modded Extract-MSP-Office_23-06-2023, but it does not touch ospp-x-none_5d0c591708ab6fdb76553c0a2ca137dc3a8b7282.cab and ocfxca-x-none_ea01b56460836086e46ac9135fa5ff094dd4b818.cab. The files contained therein are: ospp-x-none.msp ocfxca-x-none.msp What should I rename these to after extraction? Also, since I am manually extracting only those specific files from the SP2 update that apply to my target language, how should I name those before running upsourcer? Thanks
Ok, I put all the files you suggested in the "Update" folder: Code: clientshared64mui-en-us.msp clientshared64mui-en-us.xml clientsharedmui-en-us.msp clientsharedmui-en-us.xml files.txt ocfxca-x-none.msp ocfxca-x-none.xml officesuitemui-en-us.msp officesuitemui-en-us.xml omui-en-us.msp omui-en-us.xml ospp-x-none.msp ospp-x-none.xml pmui-en-us.msp pmui-en-us.xml projectmui-en-us.msp projectmui-en-us.xml proof-en-us.msp proof-en-us.xml proofing-en-us.msp proofing-en-us.xml sharepointdesignermui-en-us.msp sharepointdesignermui-en-us.xml visiomui-en-us.msp visiomui-en-us.xml vismui-en-us.msp vismui-en-us.xml xmui-en-us.msp xmui-en-us.xml Z_osetup2010_kb4022208_x86_osetup-x-none.msp Z_rmaddlocal2010_kb2879953_x86_rmaddlocal-x-none.msp Here are the files in my "OfficeMSI" directory (directory name that is suggested in the readme - extracted from en_office_language_pack_2010_x86_516850): Code: AccessMUI.msi AccessMUI.xml AccessMUISet.msi AccessMUISet.xml AccLR.cab autorun.inf branding.xml branding.xml0 config.xml config.xml0 config.xml1 DW20.EXE dwdcw20.dll dwintl20.dll dwtrig20.exe ExcelLR.cab ExcelMUI.msi ExcelMUI.xml files.txt files14.cat GrooveLR.cab GrooveMUI.msi GrooveMUI.xml InfLR.cab InfoPathMUI.msi InfoPathMUI.xml Microsoft.VC90.CRT.manifest msvcr90.dll Office64MUI.msi Office64MUI.xml Office64MUISet.msi Office64MUISet.xml OfficeLR.cab OfficeMUI.msi OfficeMUI.xml OfficeMUISet.msi OfficeMUISet.xml OMUI.cab OMUI.msi OMUI.xml OneNoteMUI.msi OneNoteMUI.xml OnoteLR.cab ose.exe ose.exe0 ose.exe1 osetup.dll osetup.dll0 osetup.dll1 osetupui.dll OutlkLR.cab OutlookMUI.msi OutlookMUI.xml OWOW64LR.cab PidGenX.dll PidGenX.dll0 PidGenX.dll1 pkeyconfig-office.xrm-ms pkeyconfig-office.xrm-ms0 pkeyconfig-office.xrm-ms1 PMUI.cab PMUI.msi PMUI.xml PowerPointMUI.msi PowerPointMUI.xml PptLR.cab ProjectMUI.msi ProjectMUI.xml ProjLR.cab Proof.cab Proof.cab0 Proof.cab1 Proof.msi Proof.msi0 Proof.msi1 Proof.xml Proof.xml0 Proof.xml1 Proofing.msi Proofing.xml pss10r.chm PublisherMUI.msi PublisherMUI.xml PubLR.cab RbudLR.cab README.HTM README.TXT RosebudMUI.msi RosebudMUI.xml setup.chm setup.exe setup.xml setup.xml0 setup.xml1 setup.xml10 setup.xml11 setup.xml12 setup.xml13 setup.xml14 setup.xml15 setup.xml16 setup.xml17 setup.xml18 setup.xml2 setup.xml3 setup.xml4 setup.xml5 setup.xml6 setup.xml7 setup.xml8 setup.xml9 SharePointDesignerMUI.msi SharePointDesignerMUI.xml ShellUI.MST SPDLR.cab Updates VisioLR.cab VisioMUI.msi VisioMUI.xml VisMUI.cab VisMUI.msi VisMUI.xml WordLR.cab WordMUI.msi WordMUI.xml XMUI.msi XMUI.xml _bin _OfficeUpsourcer2010.cmd _ReadMe.txt _RestoreBackups.cmd But I still get the error "ERROR: could not detect Office language" Thanks again. edit: I used en_office_language_pack_2010_x86_x64_dvd_516538.iso instead of X16-37701.exe (en_office_language_pack_2010_x86_516850) and that seems to work. Except for these errors during one of the steps: Code: - Modify Setup and Package xml files C:\OfficeMSI\_bin\XmlMod.vbs(24, 2) Microsoft VBScript runtime error: Object required C:\OfficeMSI\_bin\XmlMod.vbs(24, 2) Microsoft VBScript runtime error: Object required C:\OfficeMSI\_bin\XmlMod.vbs(24, 2) Microsoft VBScript runtime error: Object required C:\OfficeMSI\_bin\XmlMod.vbs(24, 2) Microsoft VBScript runtime error: Object required C:\OfficeMSI\_bin\XmlMod.vbs(24, 2) Microsoft VBScript runtime error: Object required C:\OfficeMSI\_bin\XmlMod.vbs(24, 2) Microsoft VBScript runtime error: Object required C:\OfficeMSI\_bin\XmlMod.vbs(24, 2) Microsoft VBScript runtime error: Object required C:\OfficeMSI\_bin\XmlMod.vbs(24, 2) Microsoft VBScript runtime error: Object required C:\OfficeMSI\_bin\XmlMod.vbs(24, 2) Microsoft VBScript runtime error: Object required C:\OfficeMSI\_bin\XmlMod.vbs(24, 2) Microsoft VBScript runtime error: Object required
Office exe files can be extracted with command line: Code: X16-37701.exe /quiet /extract:%cd%\X16-37701 i guess not all LP msi files are changed with SP2 test if installation works with updated source
Ok, that explains it, I extracted it with 7-zip which did not re-create the directory structure. With your method it extracts properly just as the official Microsoft ISO does. Installation worked perfectly. Thanks very much for your amazing work.