Secondly with the developers in order to supply the raw app manifest file. To run the install, use this syntax: Setup.exe /configure configuration.xml You can create a batch file or use something like PDQ or SCCM to deploy it. 5 Steps total Step 1: Download Office Deployment Tool. This should also work for Office/Microsoft 365, but I have not confirmed that. First with IT in order to set the trust relationship with the distribution point, and the server which the app is communicating with. Here is a guide for an offline deployment. Practically it's not going to happen without support and commitment from the IT department and the developers of the app you're interested in. So it is possible, technically, to use app-add-ins without connecting to the Office Store service. The same Overview of apps for Office 2013 page that gives us the graphic above also outlines how to create your own file based Distribution Point repository from which to install apps. My confusion was spawned in part by the fact that Microsoft also uses the "add-in" term for apps in the Store. This is quite different from the "Add-Ins" I've used up until now ( example) which follow the more traditional activation route of download files, unpack, install. The architecture of an Office "app" is predicated on active connection to an external server see diagram. Thank you for asking the question that redirected my searches that eventually revealed understanding, even though it's not what I wanted. The answer is: you can't get there from here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |