In Application of the Week – Microsoft 365 (Part 1) I’ve described how to create a non-managed package for the deployment of Microsoft 365 Apps.
In this blog I’m happily announcing that the process in that blog has been superseded. As of today you can create a managed package for Microsoft 365 Apps for both x86 and x64. Easy and simple.
Currently we support the Current Channel and the following languages: Dutch, English US, French, German and Spanish. Monthly Enterprise Channel and Semi-Annual Enterprise Channel, English UK and Scandinavian languages will be available soon.
Let’s create a managed package for e.g. the English version for x64, for the Current Channel:
Click Next. Then this KB article is shown here:
provides you detailed information about the ODT configuration which by default is used for each particular combination of Channel, Language and Architecture. Click Next:
Looking at the above example (Business Retail, Current Channel, English, x64), the configuration file ‘O365BusinessRetail-Current-en-us-x64.xml’ being used for this scenario looks like this:
<Configuration> <Add OfficeClientEdition="64" Channel="Current" Version="16.0.15225.20204"> <Product ID="O365BusinessRetail"> <Language ID="en-us" /> <ExcludeApp ID="Teams" /> </Product> </Add> <Property Name="PinIconsToTaskbar" Value="FALSE" /> <Property Name="AUTOACTIVATE" Value="0" /> <Property Name="FORCEAPPSHUTDOWN" Value="TRUE" /> <Updates Enabled="FALSE" Channel="Current" /> <RemoveMSI /> <Display Level="None" AcceptEULA="TRUE" /> </Configuration>
The managed package for Microsoft 365 Apps has two action sets: Install and Launch.
The install action set has three actions. The first ‘Install uploaded directory’ downloads a zipfile which contains setup.exe and all ODT configuration files:
‘Launch setup’ launches setup.exe with the “/configure “O365BusinessRetail-Current-en-us-x64.xml” switch.
Which then downloads the binaries needed to install Microsoft 365 Apps, from the Microsoft CDN network. Similar to how a web downloader setup works. ‘Cleanup temp folder’ then cleans up, after the installation has ended.
The Launch action set is the icing on this cake. This contains all icons to launch either of the Microsoft 365 Apps applications.
And because it’s ‘managed’ the Setup Store connector automatically updates this package when Microsoft releases a new version:
This is how it looks like for an admin creating such a managed package. And then delivering this Microsoft 365 Apps package in his own Liquit Workspace:
Application of the Week
The best way to fully appreciate the power of the Liquit Digital Workspace is to see the above example and other features in action.
Book your demonstration today! Just click the ‘Request a demo’ button in the upper part of this web page. You will be joined by a Liquit expert who will take you on a guided tour of the Digital Workspace, demonstrating features and functionality, specifically focused on the needs and requirements of your organization.