This article explains the process to take a VM with Office installed. Offload the Office folder to a network location and use the VM as a template for all other machines in the host pool. By offloading the Office install footprint folder the following benefits are achieved:
Reduce requirements for C: disk size
When snapshot and/or backup is performed those are smaller and from there cheaper to store
Easier to update images using an automated pipeline
One instance of office per host and potentially WVD deployment
This covers the prerequisites for the manual process. Later we can automate.
VM running Windows
Copy of Office
RDP in the VM.
Install Office. Installation can be either manually or via an automated process. More information here.
Note: the outcome of this operation is the creation of a VHDX with the content of the C:\Program Files\Microsoft Office.
Create rules file
Start the rule editor (C:\Program Files\FSLogix\Apps\RuleEditor.exe).
Create a new Rule Set File by clicking File > New create and saving the ruleset to the local folder (e.g. C:\Users\ssa.GT090617\Documents\FSLogix Rule Sets).
Select Blank Rule Set and press OK.
Click the + button. This will open the Add Rule dialog.
This will change the options in the Add Rule dialog. From the drop-down select App Container (VHD) Rule.
For folder type C:\Program Files\Microsoft Office. For Disk file select <path>\office.vhd from the Create target VHD section. Click OK.
The .frx and .fxa are always saved in a working folder (e.g. C:\Users\<username>\Documents\FSLogix Rule Sets). Both files need to be moved to the Rules folder C:\Program Files\FSLogix\Apps\Rules become effective. This is by design.
ClickApply Rules to Systemfor the rules to take effect.