It is only supported to run one (1) App-V Package that contains Office Components.Sequencing Office 2016 manually using the App-V Sequencer is not supported! You need to use ODT (Office Deployment Toolkit) to generate the App-V Package.Microsoft actually recommends to go for a Click-To-Run or App-V based Deployment. (To verify that you can search for *AppV* in the Office Installation folder and you will find some EXEs and DLLs that will be very familiar if you know App-V.) With that knowledge that Office Itself is running virtualized when using Click-To-Run, the steps for creating an App-V Package are very straight forward. With the Click-To-Run Installer, there is actually a built-in App-V Client in Office. Since Office 2013, Microsoft has changed the Way, how they deliver Microsoft Office. Creating a Custom MSP with the OCT (Office Customization Tool) is pretty simple and was long a Best-Practice. If you are currently deploying Microsoft Office using for example ConfigMgr, you are probably using the MSI based Installation Method. See here for a list of supported Product IDs: Product IDs that are supported by the Office Deployment Tool for Click-to-Run UPDATE: Based on the following TechNet Forum Thread, creating Volume Licensing App-V Packages of Office 2016 is no longer supported.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |