Skip to main content

FlexApp packaging Office 2019

Vincent Trieu
  • Created:
  • Updated:

Problem: FlexApp packaging Office 2019 KMS

 

Prerequisite

**NOTE** Office must be captured on a FPC versions 6.8.4.7654-7842 or above

The FPC (FlexApp Packaging Console) and VDI base image should be well-managed and cannot have had Office previously installed (even if uninstalled, the base image would be in a tainted state). This includes the parent VDI image that will be used as the target.

FPC should follow best practices similar to what’s outlined here: https://docs.liquidware.com/profileunity/en-us/686/flexapp-packaging-console-best-practices/686-flexapp-console-best-practices-overview.htm

Please review https://learn.microsoft.com/en-us/deployoffice/install-different-office-visio-and-project-versions-on-the-same-computer for Microsoft supported installation scenarios for version control.

Office 365 Products would need to include “Shared Computer Licensing” as outlined here: https://learn.microsoft.com/en-us/deployoffice/overview-shared-computer-activation 

-------------------------------------------------------------------------------------------------------------------

If using Active Directory Activation:

If using active directory activation for Office (i.e https://learn.microsoft.com/en-us/deployoffice/vlactivation/activate-office-by-using-active-directory), capture the application as normal and add the following option in your script:

If using ospp.vbs for activation:

/skms-domain:value

If using slmgr for activation:

/skms-domain <FQDN>

--------------------------------------------------------------------------------------------------------------------

Process Flow

  1. Take a snapshot of FPC to preserve a clean state for later testing
  2. Download ODT from the Official Microsoft Website: https://www.microsoft.com/en-us/download/details.aspx?id=49117
  3. Run officedeploymenttool_15726-20202 and extract to a directory i.e (C:\ODT)officedepoyment.png
  4. Edit configuration-Office2019Enterprise from the extracted contents using Notepad or any IDE (Notepad++) and remove the following lines unless your packaging to include these options:<Product ID="VisioPro2019Volume">
    <Language ID="en-us" />
    </Product>
    <Product ID="ProjectPro2019Volume">
    <Language ID="en-us" />
    </Product>
    Example below
    edited_lines.png
  5. Open an Administrative PowerShell window and change the directory to the extracted path and execute
    .\setup.exe /download configuration-Office2019Enterprise.xmlpowershell_odt.png
  6. Once the download is completed, begin the capturing process. Use a 20GB for the disk size of the package.
  7. In the same powershell window from earlier execute:
    .\setup /configure configuration-Office2019Enterprise.xml
  8. Once the installer finishes, save the package.
  9. Activate the package after to add a script.
  10. Add script to the package
    Add_script_button.png
  11. Add the office.bat as a Post Activation script. The script is at the bottom of this KB.
    script_window.png
    • Script contents:
      "C:\Program Files\Microsoft Office\root\integration\integrator.exe" /I /License PRIDName=ProPlus2019Volume.16 PackageGUID="9AC08E99-230B-47e8-9721-4577B7F124EA" PackageRoot="C:\Program Files\Microsoft Office\root"
      "C:\Program Files\Microsoft Office\root\integration\integrator.exe" /I /License PRIDName=ProjectPro2019Volume.16 PackageGUID="9AC08E99-230B-47e8-9721-4577B7F124EA" PackageRoot="C:\Program Files\Microsoft Office\root"
      "C:\Program Files\Microsoft Office\root\integration\integrator.exe" /I /License PRIDName=VisioPro2019Volume.16 PackageGUID="9AC08E99-230B-47e8-9721-4577B7F124EA" PackageRoot="C:\Program Files\Microsoft Office\root"
      cscript "c:\Program Files\Microsoft Office\Office16\ospp.vbs" /act
  12. Save the package
  13. Revert snapshot and test the package on FPC and VDI session.

 

Packaging Visio or Project separately from Office

Functionality has been tested on 6.8.5 FPC using High Compatibility mode

 

Prerequisite
The FPC (FlexApp Packaging Console) and Target VDI should never previously had Visio or Project installed (even uninstalled which would leave it in a tainted state).

Steps

  1. Take a snapshot of the FPC
  2. Install Office base in the FPC and same version in the VDI (See steps 1-7 above)
  3. Take another snapshot or be sure to use 6.8.5 rollback mode for next part

  4. Edit configuration-Office2019Enterprise from the extracted contents using Notepad or any IDE (Notepad++) and remove or include the following lines to either have both Visio and Project or only one installed.

    <Product ID="VisioPro2019Volume">
    <Language ID="en-us" />
    </Product>
    <Product ID="ProjectPro2019Volume">
    <Language ID="en-us" />
    </Product>

    then Save the file

  5.  

    Open an Administrative Powershell window and change the directory to the extracted path then type .\setup.exe /download configuration-Office2019Enterprise.xml
    and hit enter. It will take some time but the command will finish once the next line appears and will download files to specified dir (C:\ODT).

    powershell_odt.png

    6. Begin capturing while using 20GB thin provisioned for the disk size of the package.
    7. In the same powershell window from earlier, type

    .\setup /configure configuration-Office2019Enterprise.xml

    and hit enter. A window will pop-up and it will start installing Office. It will take some time to finish.

    8. Once the installer finishes, save the package.
    9. Activate the package after to add a script.

    10. Add script to the package

    Add_script_button.png

    11. Add visioandproject.bat as a Post Activation script attached here to KB.

    script_window.png
    11a. Script contents:
    "C:\Program Files\Microsoft Office\root\integration\integrator.exe" /I /License PRIDName=ProjectPro2019Volume.16 PackageGUID="9AC08E99-230B-47e8-9721-4577B7F124EA" PackageRoot="C:\Program Files\Microsoft Office\root"
    "C:\Program Files\Microsoft Office\root\integration\integrator.exe" /I /License PRIDName=VisioPro2019Volume.16 PackageGUID="9AC08E99-230B-47e8-9721-4577B7F124EA" PackageRoot="C:\Program Files\Microsoft Office\root"
    cscript "c:\Program Files\Microsoft Office\Office16\ospp.vbs" /act

    12. Save the package

    13. Revert snapshot or rollback with 6.8.5 and test the package on FPC and VDI session.

 

Product: FlexApp

Product Version: 6.8.4+

Expires on: 365 days from publishing

Updated: June 27, 2024

Related articles