Upsourcer: Slipstream patches for Office 2007/2010/2013/2016 and rebuild setup source files

Discussion in 'Microsoft Office' started by abbodi1406, Jun 24, 2023.

  1. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,192
    90,682
    340
  2. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,192
    90,682
    340
  3. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,192
    90,682
    340
  4. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,192
    90,682
    340
  5. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,192
    90,682
    340
  6. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,192
    90,682
    340
    Unattended run example (Office 2010 Single Image x64)
    Code:
    - Move Office WOW files to a single folder
    
    - Modify Setup and Package xml files
    
    - Restore administrative installation table
    
    AccessMUISet.msi
    AccessMUI.msi
    ExcelMUI.msi
    OfficeMUI.msi
    OfficeMUISet.msi
    Office32MUI.msi
    Office32WW.msi
    OneNoteMUI.msi
    OutlookMUI.msi
    PowerPointMUI.msi
    Proofing.msi
    Proof.msi
    Proof.msi
    Proof.msi
    PublisherMUI.msi
    SingleImageWW.msi
    WordMUI.msi
    
    - Slipstream Service Pack
    
    Proof.en\Proof.msi
    Proof.es\Proof.msi
    Proof.fr\Proof.msi
    AccessMUISet.msi
    AccessMUI.msi
    ExcelMUI.msi
    OfficeMUI.msi
    OfficeMUISet.msi
    Office32MUI.msi
    OneNoteMUI.msi
    OutlookMUI.msi
    PowerPointMUI.msi
    Proofing.msi
    PublisherMUI.msi
    WordMUI.msi
    Office32WW.msi
    SingleImageWW.msi
    
    - Slipstream Updates
    
    Proof.en\Proof.msi
    Proof.es\Proof.msi
    Proof.fr\Proof.msi
    AccessMUISet.msi
    AccessMUI.msi
    ExcelMUI.msi
    OfficeMUI.msi
    OfficeMUISet.msi
    Office32MUI.msi
    OneNoteMUI.msi
    OutlookMUI.msi
    PowerPointMUI.msi
    Proofing.msi
    PublisherMUI.msi
    WordMUI.msi
    Office32WW.msi
    SingleImageWW.msi
    
    - Replace original osetup.dll and setup.exe
    
    - Insert PatchAdd vbscript into MSIs
    
    - Create MakeCAB DDF directives
    
    AccessMUISet.msi
    AccessMUI.msi
    ExcelMUI.msi
    OfficeMUI.msi
    OfficeMUISet.msi
    Office32MUI.msi
    Office32WW.msi
    OneNoteMUI.msi
    OutlookMUI.msi
    PowerPointMUI.msi
    Proofing.msi
    Proof.msi
    Proof.msi
    Proof.msi
    PublisherMUI.msi
    SingleImageWW.msi
    WordMUI.msi
    
    - Create new CAB files
    
    AccLR.cab
    ExcelLR.cab
    OfficeLR.cab
    OWOW32LR.cab
    OWOW32WW.cab
    OnoteLR.cab
    OutlkLR.cab
    PptLR.cab
    Proof.cab
    Proof.cab
    Proof.cab
    PubLR.cab
    SIWW.cab
    SIWW2.cab
    WordLR.cab
    
    - Remove administrative installation directories
    
    - Restore Office WOW files to the original folder(s)
    
    - Remove original files backups
    
    ============================================================
    Finished.
    
    Press any key to exit.
     
  7. asdddsa101

    asdddsa101 MDL Member

    Feb 11, 2021
    121
    41
    10
    #7 asdddsa101, Jun 25, 2023
    Last edited: Jun 25, 2023
    Office 2007 MSI Upsourcer. Restore the administrative installation table to IME*.msi, execute the "msiexec.exe /a IME*.msi targetdir=xxx" command, the targetdir only has one IME*.msi and one IME*.xml file. As a result, IME32.cab and IME64.cab cannot be packaged in the end.
    Code:
    IME*.xml file e.g.
    2007_Setup_Media\Proofing.zh-cn\Proof.zh-cn\FILES\PFILES\COMMON\MSSHARED\OFFICE12\Office Setup Controller\Proof.zh-cn\IME32.xml
    The original and modified (Restore the administrative installation) files of Chinese Simplified (zh-cn) IME32.msi and IME64.msi are provided in the attachment. The problem should be that the administrative installation was not properly added to both of them.
     

    Attached Files:

  8. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,192
    90,682
    340
  9. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,192
    90,682
    340
  10. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,192
    90,682
    340
    Office 2016 MSI Upsourcer will be delayed, or not possible

    Office 2016 msp files are too sophisticated, and mess-up msi files when applied to (change file properties, name, summary, revision), and can cause some msi files installation to fail
    the msp files also do not add the "Patch._[GUID]" properties, which are needed for patches registration vbscript

    all previous Office products and even .NET Framework 4.8- use Windows Installer Schema 3.0
    while Office 2016 msi and msp files use Schema 4.5
    that might be the main reason for this mess
     
  11. fch1993

    fch1993 MDL Senior Member

    Mar 14, 2020
    381
    273
    10
    #16 fch1993, Jul 1, 2023
    Last edited: Jul 1, 2023
    @abbodi1406

    I still have 2 questions about Office 2010.

    1. About List of all Office 2010 SP2 packages

    Is that OK to use the ISO files from MVS?

    https://forums.mydigitallife.net/threads/office-2010-professional-plus-sp2-iso.76222/#post-1405783


    2. If I use the x86_x64 iso image for installation, the "Location_for_Extracted_OfficeSetupFiles" should be where?

    exp:
    en_office_professional_plus_2010_x86_x64_dvd_515529.iso

    It doesn't work if I set the "Location_for_Extracted_OfficeSetupFiles=D:\OUS2010_u\en_office_professional_plus_2010_x86_x64_dvd_515529"

    with error

    Code:
    Warning: recommended update KB2879953 rmaddlocal-x-none.msp is not detected
    
    ============================================================
    ERROR: could not detect Office language
    
    Press any key to exit.
    
     
  12. asdddsa101

    asdddsa101 MDL Member

    Feb 11, 2021
    121
    41
    10
    Specify sources for x64 and x86 separately, using the script twice.
     
  13. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,192
    90,682
    340
    @fch1993

    1. Whatever SP2 source work, extracted MSP files are what matter
    Code:
    clientshared32ww-x-none.msp
    clientshared64ww-x-none.msp
    officesuiteww-x-none.msp
    projectww-x-none.msp
    visioww-x-none.msp
    clientshared32mui-en-us.msp
    clientshared64mui-en-us.msp
    clientsharedmui-en-us.msp
    officesuitemui-en-us.msp
    proof-xxxxx.msp
    proofing-en-us.msp
    projectmui-en-us.msp
    visiomui-en-us.msp
    
    sharepointdesignermui-en-us.msp
    sharepointdesignerww-x-none.msp
    
    omui-en-us.msp
    pmui-en-us.msp
    vismui-en-us.msp
    xmui-en-us.msp
    
    proofkitww-x-none.msp
    proofmui-en-us.msp
    proofmui-fr-fr.msp
    i personally would prefer windowsupdate cab files links

    2. you didn't read the 1st Important Remark carefully
    specify/update each architecture folder separately
     
  14. asdddsa101

    asdddsa101 MDL Member

    Feb 11, 2021
    121
    41
    10
    I tried Office 2013 Upsourcer. Integrate the Post-SP1 updates from WHD, and after installation, I found that all office applications cannot be opened like this.

    The source is using Office 2013 with SP1.
     

    Attached Files:

  15. fch1993

    fch1993 MDL Senior Member

    Mar 14, 2020
    381
    273
    10