06-18-2019 08:49 AM - edited 06-18-2019 10:19 AM
06-18-2019 08:49 AM - edited 06-18-2019 10:19 AM
@Michael Niehaus Is it possible for Office 365 to be deployed during the technician portion of White Glove as the App Type "Office 365 ProPlus Suite (Windows 10)" as opposed to a Win32 or LOB app? I have it set to be targeted to the device and required for all Autopilot devices. When I run through autopilot, it quickly skips past the app portion and then lets me reseal without installing anything. After the user logs in, the app does eventually install but our hope is to have install prior to user set up.
(As an aside, white glove did not work at all until I created slip-streamed 1903 media with all of the latest updates from the Microsoft catalog)
06-18-2019 09:50 AM
06-18-2019 10:15 AM
I haven't seen any devices restart during enrollment at this point but I have only tested deploying Office and a single Win32 app. Perhaps one of your apps is requesting a reboot or another is seeing a pending reboot and going through with the reboot depending on the order they are getting installed.
I hadn't thought of changing the Office update ring to see if the behavior would change. We are using Monthly-Targeted but I am going to try it with Semi-Annual now. Are you using Configuration Designer or Enter XML data for the Office install Settings format?
The Windows 10 1903 version that gets installed with our slip-streamed media is 18362.175
06-18-2019 10:22 AM
06-18-2019 10:29 AM - edited 06-18-2019 10:36 AM
@Darren_Bradley I just realized on my new attempt with the Semi-Annual Office update ring that neither my Office app or Win32 app are installing during white glove. I just get the green reseal screen with elapsed time of 0 h 0 min.
So, for us, nothing is installing prior to user setup.
EDIT: If I look at Managed Apps for the device, it shows that my other app did install (must have been so fast, it did't register), but Office failed with Error code: 0x0
It sounds like our Office app was set up the same as yours is. No XML, just chosen apps, latest version of Monthly targeted. (Now Semi-Annual)
06-18-2019 10:45 AM
06-18-2019 11:44 AM - edited 06-18-2019 02:25 PM
@Darren_Bradley For the first time, I let the green reseal screen sit for about 10 minutes after white glove. I refreshed the Managed apps in Intune and saw the status of the Office install go from an error to Installed after a few minutes. I did a Shift+F10 to get a command prompt and verified that the Office installation was in Program Files. So I am not sure if resealing right away and logging in interrupted the installation somehow on my previous attempts or if changing the Office update channels back and forth did something.
I am doing it again now and am not going to wait at the reseal screen to see if I can re-create the previous behavior.
To answer your question, I haven't had any problems installing Office from Company portal or during user setup portion of Autopilot.
06-18-2019 12:09 PM
06-18-2019 02:51 PM
After running through the process again, I can confirm that my apps did not install prior to the reseal screen appearing. So reseal is coming up before the apps are completely installed and if I reseal right away, the laptop shuts down and doesn't complete the installations until it is powered back up and the process is continued. I would expect the behavior to be to not let a machine reseal and shutdown until the white glove apps are installed. This is not happening in our case.
If I leave the device on the green reseal screen for 10-15 minutes, the apps install in the background. Or if I continue the user process immediately, the apps install during, or sometimes long after, the user OOBE screens have been gone through.
The timeline I saw this last time was:
2:08 pm white glove finished with no apps installed.
2:09 pm Resealed, booted up and continued with user OOBE
2:18 pm Intune console shows "App installation completed" while User OOBE was still at the "Connecting to your network" phase.
I did have my machine reboot once this round during the white glove portion which I had not seen before.
06-19-2019 07:52 AM
As you suggested, I set the ESP to install the required apps and block access until it does. Same result, green reseal screen indicating that white glove is complete but the apps are still installing in the background. I can watch the progress of the installs with a Shift+F10 command prompt and in appwiz.cpl.
06-20-2019 09:46 AM
@Darren_Bradley They are assigned as Required and includes our "All Autopilot Devices" group which the target machine is a member of. The group has dynamic membership based on it being an Autopilot device with the membership rule: (device.devicePhysicalIDs -any _ -contains "[ZTDId]")
06-21-2019 04:02 AM
07-08-2019 07:51 AM
@Darren_Bradley are you guys using Hybrid AD join? I think that is causing the reboot (in my scenario) and once that happens it seems to just stop the White Glove and says its done but does continue to check in in the background and apply policies and Apps if you sit on that completion screen. I can also reseal, power on and just let it sit at the OOBE and that seems to work too. Just curious if this is happening to AAD joined or just Hybrid AD.
07-08-2019 07:55 AM
We are just using Azure Joined Machines. We found once we selected Semi Annual channel on the updates the reboots stopped , although the update policy fails in Intune due to 1903 not having semi annual. Still not sure why it reboots or what causing it , but we needed to get around it quick as we are in pilot
07-08-2019 07:57 AM
07-08-2019 08:03 AM
Yes we have had our fair share of issues that for sure and a lot of Gotchas. We are also using patching the machines now with 18362.207 as that fixes the offline apps issue within the store. 18362.30 only seems to work with offline apps.
I did find this on Semi Annual but still not 100% on it , all I know is when we select that it works .. Autopilot will pull down updates as they are needed