Forum Discussion
Install Office after Autopilot
Hi,
I think the issue is based on the following fact. As long as software is installed via Intune Management Extension (IME) Agent the IME can coordinate the behavior. This can also be seen in the log files like checking ESP phase etc.
The Office 365 ProPlus install is not driven by IME it is a separate Configuration Service Provider (CSP)
https://docs.microsoft.com/en-us/windows/client-management/mdm/office-csp
The Office CSP basically gets the XML definition by MDM channel, then uses the ODT to do the install and monitors everything to report on it. So, we are talking about a kind of side channel. The process how Windows and Intune is handling the enrollment is driven by no specific order, meaning there is no defined sequence like first install am then b, then c... This means the MDM driven instruction for the Office CSP does get the command to trigger Office install and the IME does have it's own channel to get the apps to install. IME does respect the ESP phase where the MDM Office CSP driven channel does not. This is why you especially with Office see this install during ESP. As the Office CSP will kick off the process as soon as he gets the MDM SyncML instructions.
I think there is no mechanism currently to coordinate this...
best,
Oliver
Here is evidence about the issue-
https://borncity.com/win/2018/12/09/intune-autopilot-block-app-install-via-enrollment-status-page/
Hope this helps and please keep us updated with your results!
Moe
Hi,
I think the issue is based on the following fact. As long as software is installed via Intune Management Extension (IME) Agent the IME can coordinate the behavior. This can also be seen in the log files like checking ESP phase etc.
The Office 365 ProPlus install is not driven by IME it is a separate Configuration Service Provider (CSP)
https://docs.microsoft.com/en-us/windows/client-management/mdm/office-csp
The Office CSP basically gets the XML definition by MDM channel, then uses the ODT to do the install and monitors everything to report on it. So, we are talking about a kind of side channel. The process how Windows and Intune is handling the enrollment is driven by no specific order, meaning there is no defined sequence like first install am then b, then c... This means the MDM driven instruction for the Office CSP does get the command to trigger Office install and the IME does have it's own channel to get the apps to install. IME does respect the ESP phase where the MDM Office CSP driven channel does not. This is why you especially with Office see this install during ESP. As the Office CSP will kick off the process as soon as he gets the MDM SyncML instructions.
I think there is no mechanism currently to coordinate this...
best,
Oliver
Thank you for the reply. I guess this is supported by having Office "required" (processes immediately when target receives instructions) versus "available" (user driven).
This also explains why I can see Firefox working correctly with the IME while Office does its own thing.I wish this was more clear in the docs for installing Office through Intune.
Paul
- Thanks for the clarification Oliver!
