In technical preview of SCCM – a new feature is a simple way to packaged, deploy and servicing O365 clients.
In this blog post I will show how to packaged a O365 ProPlus.
In the new console there is a lot of new feature and dashboards.
First go into:
- Software Library
- Office 365 Client Management
- Office 365 Installer
Then the Office 365 Client Installation Wizard starts
- Name : enter the name of the application
- Content Location : Enter a location on your packages share
- Click Next
Here you can chose to “Manually specify the Office 365 Client settings”, and SCCM will create a Configuration file for you – as I will show here.
The other option is to “Import Office 365 client settings from a configuration file” you have created before. It can be done in notepad or be using https://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.html
The Suite that can be selected is:
- Office 365 ProPlus
- Office 365 Business
- Uncheck the Office 365 application you don’t want in you deployment
- Click Next
- Select Channel – you can select:
- Current
- Deferred
- First release for Current
- First release for Deferred
- Accept EULA and Autoactivate
- Click Next
More info in the “Office 365 client update channel releases”
- Select Yes or No to deploy the Application now
- Select Next
After the Application is created and downloaded to your packages share you can start to deploy O365 to users or devices.
In the Software Library –> Application your O365 client is now created
A Deployment type is also created
In the Office 365 Default Deployment Type the installation parameters is:
setup.exe /configure configuration.xml
There is also a Detection Rule as part of the deployment type used by the SCCM application model to detect id the product is already installed on the device.
In the packages share there is created a configuration.xml file with all the binary for Office 365
When the first Office 365 client is installed it will also show up in the new dashboard.
I will also to a blogpost about the new Office 365 servicing options in SCCM.
Cloud First 
Can you utilize device based activation method by changing the cmd line in the app deployment for opptransition.exe -tenant -key?
Can you utilize device based activation method by changing the cmd line in the app deployment for opptransition.exe -tenant -key?
I have not tried it – but why will you use device based activation on a user based licensing model??
I’ve got it working. Great question. For schools, we have many shared devices. We need Office on these machines, but it takes away from instruction time if we deploy the user-licensed client and the students have to sign in to the product on each computer they use. Does that make sense? So by using device-based activation, the device is treated as a user and licensed for O365 ProPlus in Admin Console and never asks for any activation to the end user. In the process of rolling out to my district now.
I use shared activation on shared devices – it works great and don’t count in the 5 devices
Interesting. From my testing shared activation still prompted the user to log in each time they open Office. https://technet.microsoft.com/en-us/library/dn782860.aspx?f=255&MSPPError=-2147217396
Does that not happen for you?
With device-based activation, no prompt to login occurs.