![office 365 apps office 365 apps](https://www.danielleshaw.com/wp-content/uploads/2015/07/google-office365-1080x603.png)
For install behaviour, SYSTEM is needed for admin rights. The format for these is setup.exe /configure filename.xml. intunewin file is uploaded to Endpoint Manager, you need to specify the install and uninstall commands that reference your XML files. The specific steps on this are covered in my blog on Win32 packaging, but are summarised in the below screenshot.Īfter your.
![office 365 apps office 365 apps](https://www.mtechsystems.co.uk/wp-content/uploads/2017/11/office365-integration-768x615.jpg)
That will take the three files and put them in one. These should be packaged using the Win32 Content Prep Tool. Now, you’ll have three files: two XMLs specifying install/uninstall options and one executable. You’ll end up with an XML that will be similar to the example below, which I’ve saved as install.xml. The UI for this is very simple, so I won’t guide you through that. You can create your own XML from scratch, or use to build one. The XML files can be disregarded as we’ll be creating our own, which manage the settings for our deployment. You will end up with setup.exe and some XML files. Deploying Office 365 as a Win32 Appįirstly, download the Office Deployment Toolkit and extract the contents to a folder.
![office 365 apps office 365 apps](https://365tips.be/wp-content/uploads/2019/12/image-44.png)
Thank you to DarrenG for pointing out the Intune health advisory.
Office 365 apps how to#
In this blog, I’ll cover how to get that working with Intune.īig thank you to Peter Klapwijk, Alex Durrant, Rudy Ooms, and Chris Roberts for encouraging the Win32 approach. Whatever the root cause of the Office CSP deployment problem, deployments were fine using the standard Office Deployment Toolkit approach, as recommended by many on Twitter. From what I read online, Microsoft support said this is due to a CDN replication problem and, at the time of writing, is listed under service health advisory IT262216. Recently, there have been problems deploying Office 365 apps with this Office CSP method. I wrote a general guide about that for, available here. In the background, this is using the Office CSP to deploy the client, which makes it quite unique compared to the deployment of other apps, which are best done with Win32 packaging. The advantage of this is you don’t need to package anything: you fill out some nice drop-downs and options in a GUI, assign it like any other app, and Microsoft takes care of the rest. Office 365, or Microsoft 365 Apps for Enterprise, or whatever it’s called this month, can be deployed by Intune to Windows 10 devices using a built-in wizard.