Event banner
Event details
Jason_Sandys
Microsoft
MicrosoftHi 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.
- That's clear, but it's more of a workaround. We want to use the MEM feature and always install the latest Office version instead of packaging a new Win32 package every month.