Event banner
Event details
1. When will the long announced integration of ConfigMgr in Autopilot Deployment be available?
2. will this be fixed with windows 11?
"When you're deploying Win32 apps, consider using the https://docs.microsoft.com/en-us/mem/intune/apps/intune-management-extension approach exclusively, particularly when you have a multiple-file Win32 app installer. If you mix the installation of Win32 apps and line-of-business apps during AutoPilot enrollment, the app installation might fail. The Intune management extension is installed automatically when a PowerShell script or Win32 app is assigned to the user or device."
- Jason_Sandys
Microsoft
Hi trebelow, for #1, I'm assuming that you mean the feature set announced by Rob York at Ignite that enables a device to be directly co-managed during Autopilot. If so, this is an on-going effort but we have nothing to announce about its availability at this time. Do keep in mind though this feature set is only for AADJ scenarios.
For #2, this is a deeper challenge that isn't really specific to Autopilot. Can you expand on why this is a blocker or pain-point for you?
- For the end-user experience, we would like to install all applications (Win32 Apps, LOB and Office) via Whiteglove. This is not possible / reliable today. This is the reason why we have to install Office in the user part, which leads to further problems as additional Win32 apps are also assigned to the user.
- Jason_SandysFor LOB apps, the general suggestion is to repackage these as Win32 apps. While this adds a slight amount of overhead and work, it also adds functionality like requirements, dependencies, and supersedence. As for Office, you can adopt this approach also if you consistently see conflicts. Generally, Office installation issues are related to CDN download times and moving the files into a Win32 app can alleviate this.
