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
- rahuljindalAug 05, 2022Bronze ContributorCloud apps can do that during autopilot. Wrap the office installation as win32. I do that and never faced any issues.
- Hogan_KlinkAug 05, 2022Copper ContributorThanks 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?
- pcat54Sep 26, 2022Copper ContributorThis blog has some good info on this very issue too:
https://airdesk.com/2022/03/basic-flaw-in-intune-package-for-microsoft-365-apps/
it states that the MS office app profile available in MEM is susceptible to the same incompatibility between LOB and Win32 apps during autopilot.
Just curious, are you packaging MSI's in your win32 apps? I am converting my office app to a win32 after reading the above blog, and came across your post. I'm wondering if the reason I haven't had any issues is that (so far) all my win32 apps are using EXE's.