Forum Discussion
MS Word 2003 (or 2007, 2010)
- Jun 04, 2020
The package for Office applications is not something that can be automatically converted to MSIX or App-V (for that matter), without any inside information about how it was built (information only available to the MS teams).
My recommendation is to way until MS publishes its own version of an MSIX installer for Office. This is what they did for App-V too, they had to make a special build since their own App-V Sequencer couldn't simply repackage it successfully.
Here is an excerpt from the last article linked above:
Office 2016 App-V Packages are created using the Office Deployment Tool, which generates an Office 2016 App-V Package. The package cannot be created or modified through the App-V sequencer.
The package for Office applications is not something that can be automatically converted to MSIX or App-V (for that matter), without any inside information about how it was built (information only available to the MS teams).
My recommendation is to way until MS publishes its own version of an MSIX installer for Office. This is what they did for App-V too, they had to make a special build since their own App-V Sequencer couldn't simply repackage it successfully.
Here is an excerpt from the last article linked above:
Office 2016 App-V Packages are created using the Office Deployment Tool, which generates an Office 2016 App-V Package. The package cannot be created or modified through the App-V sequencer.
- michael müllerJun 05, 2020Copper Contributor
Bogdan Mitrachethank you for your information.
For us, it would be important, that our lagacy Word will be suported als well.
In what timeframe do you think it would be available, maybe there is already some kind of beta in the early adopter program?Michael