![]() I'm new to Intune and Autopilot and found everyone's comments insightful and made me rethink some of my processes. Lesson learned do not use Win32 with LOB apps! This thread brings up the topic but left the conclusion kind of ambiguous:Īutopilot Mixing LOB and Win32 : Intune ()īy the way I really like this Sub-Reddit. I will convert the msi package to a Win32 app to see if that resolves the issue. I have removed it and everything including Office 365 installed without an issue and proceeded to fingerprint/passcode setup. The following text is included in the Setup log: Output. For example, if you use the following command line to run Setup: PowerShell. The real issue was a LOB application Trend Micro Apex One that was causing the issue. If you suspect problems with the command-line properties and switches that you are using, these items are also listed in the Setup log file. I have read elsewhere that if a reboot is required by the app install it may trip up Autopilot but how would I include a reboot when packaging it with the Apps installer?Įdit: Well this is embarrassing. ![]() Are there any tips on getting around this? I am targeting the Windows AutoPilot devices group currently but was targeting a user group previously. I suspected Office 365 was the cause and removed it and now the 4 of 4 apps install and it progresses to the user's desktop successfully without having to hit the "continue anyway" button. When deploying Microsoft 365 Apps for Windows 10 (with other apps) the Autopilot process hangs at Apps 4 of 5.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |