Forum Discussion
Microsoft 365 Apps (C2R) interfering Windows app (Win32) installs during Autopilot deployments
Hi Hogan_Klink
On which step is your autopilot enrollment failing?
What timeout time did you configure in the Enrollment status page? By default, it is 60 minutes. you can extend this number of minutes if it fails because of a delay in app installations.
What did you configure at the setting: Block device use until required apps are installed if they are assigned to the user/device?
And how many apps are assigned as required to a device group and user group? and what kind of apps are you rolling out? did you setup the Store for Business connector to install the company portal for instance?
If you are during an autopilot enrollment in the ESP and you press Shift + F10 and type Control and go to software. Are there any apps installed?
Kind regards,
Rene
Rene
- It's failing at the application install phase. I know it's because the Office C2R installer is the culprit because I enabled logged in the (Win32) MSI installers and a failure error was listed stating another MSI installer process was running. The Application Event Log showed during this time frame the Office C2R Installers were running.
- Cloud apps can do that during autopilot. Wrap the office installation as win32. I do that and never faced any issues.
- Thanks for the reply. I hoping to avoid creating more Win32 installers than necessary and utilize the built-in cloud app technologies. Have you seen any Microsoft documentation that says they will not work together?
