When the MSI installation has been generated, click OK. Wait for the Install Toolkit to generate the file, it shouldn’t take long, unless you’ve chosen to download data and embed it within the installation.ġ5. Specify a location where the MSI file should be generated and click OK. Finally, in the Generate pane, select MSI as the Instal type, set Silent install to Yes and optionally specify a name for the file that’s about to be generated. In the Options pane, select None as the Display Level and set Accept EULA to True. In the Updates pane, make sure that Updates are Enabled, make any other desired configurations and click Next.ġ2. In the Download pane, make your desired optional configurations and click Next.ġ1. Select the applications that should be included or excluded and click Next.ġ0. As for this demonstration, I’ll leave their defaults. On the Optional tab, make your desired optional configurations if required. Make your Language selections and click Next.Ĩ. Select your desired Product, Edition and Channel, then click Next.ħ. Office 365 ProPlus Install Toolkit should now have launched. Wait for the installation to download and install the required files.ĥ. Browse to the following website: Install Toolkit.Ĥ. With those configurations, your deployment experience with Office Click-to-Run should be seamless, and not pose any problems.ġ. Leave “Display Level” set to the default “None”.Exclude products you do not want to be installed (e.g.However, you’ll need to make sure that you enable all of the unattended configurations. When you walk through this guide, make a note of that some of settings that I’ve chosen to make for the silent install of Office Click-to-Run may not be suitable in your environment. The first thing we need to do is to generate a MSI installation file for Office Click-to-Run. Generate MSI installation for Office Click-to-Run The reason I mentioned my lab environment setup is simply because I want to give you an overview of what’s possible when enabling the cloud. Microsoft Intune tenant with Mobile Device Management capabilitiesĪs you can see, it’s not really a huge list of requirements.All of this is not a requirement when deploying Office Click-to-Run with Microsoft Intune, however you’ll need the following: As for my Windows 10 lab device, it’s Azure AD joined and it’s getting a General Configuration policy from Microsoft Intune. My lab user account has an Office 365 license. ![]() ![]() My lab environment consists of an Azure AD directory with automatic enrollment in Microsoft Intune enabled. I’d also like to mention how I’ve currently set up my lab environment, to fully support this scenario. OverviewĪs I’ve already mentioned a bit, we’re gonna deploy Office Click-to-Run by using the software distribution feature called Windows Installer through MDM in Microsoft Intune. In this post I’ll walk you through the process of generating an MSI file from the Install Toolkit and deploy it with Microsoft Intune to a Windows 10 device. We can now Azure AD join devices, let them be managed by Microsoft Intune, deploy Office 365 Client and have SSO including many other great features that Microsoft Intune brings to the table in terms of MDM management. This is actually huge news when you think about the mobile concept with Windows 10, Azure AD join and Microsoft Intune. But as of today, MIcrosoft has announced that the InstallToolkit for Office Click-to-Run is now supported to use with Microsoft Intune to successfully deploy Office 365 Client to mobile device managed Windows 10 devices. Unfortunately, it didn’t work that that time, and we thought that we might have done something wrong. Although, myself and some colleagues tested this new tool that generates an MSI file for the Office Click-to-Run installation, and deployed that to some Windows 10 devices in our lab environments. A while ago, the Office team announced the Install Generator (now called Install Toolkit) for Office Click-to-Run, which have some impressions that Microsoft is closing the gap on the problem with deploying Office for Windows 10 devices managed as mobile devices with Microsoft Intune. However, there has been a huge limitation for this to hit the masses, and that has been the fact that there were no way to deploy Office 365 Client (Office Click-to-Run). When we think about the concept of managing mobile devices, ever since the release of Windows 10 and the announcement of managing those devices through an OMA-DM agent (also referred to as MDM in some cases) with Microsoft Intune, this new way of managing Windows 10 devices have look very promising for many companies.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |