Intune App Deployment - why! just why!!

[mdrabble]

Deployed out laptops to staff in Sept and the who process went well once I ironed out issues with apps.

 

Everything been ticking along nicely until recently when I needed to deployment laptops for trainees and now deployment now fails during the ESP on Applications!!

 

Nothing been added, changed or removed - nothing had been altered in anyway - but all of a sudden, I now have issues with Error 0x0070643

 

According to Google 0x0070643 which is a generic error 1603 error!

 

I'm now going through and removing apps to see which fails!

 

Why can there not be a simple deployment methods which isn't flaky as   and breaks when you so much as looking at it!

 

[strawberry]

Bet this is a dependency error. Something will have included dotnet or similar and they are now installing in a different order.

[mdrabble]

43 minutes ago, strawberry said:

Bet this is a dependency error. Something will have included dotnet or similar and they are now installing in a different order.

I would have thought if anything had a dependency, and was missing it would install and then check again to make sure requirements are met.

 

I will have a check to see if any apps have dependancies as cannot remember off the top of my head.

[mdrabble]

While sat on the bus home, just discovered the new powershell install script feature - no more having to wrap the installer!

 

Also discovered that New AppStore uses WinGet 

 

On a side note, if you have the store disabled to published apps only, a cmd Winget install bypasses the store lockdown.

 

i really need to try and keep up on intune changes!

[Langella]

Best way of troubleshooting this is exporting the logs when ESP error happens.   you don't have to read all of them, just upload them to your favorite LLM and let them check what is failing, then you take a decision.    I believe it will be faster this way 

[itskdog]

Are you mixing app types (Win32/LOB), or have Office set as a blocking app in the ESP?

 

Using the M365 Apps app type rather than packaging it as a Win32 app can cause issues during ESP.

 

Also, the Get-AutopilotDiagnosticsCommunity script should be able to tell you step-by-step what happened in the Autopilot/ESP process and what went wrong.

Edited February 3 by itskdog

[mdrabble]

Think I found the cause - Netsupport School MSI for some reason suddenly started playing up.

 

I've just removed the assignment from that app and just testing now.

 

EDIT***

Just tried the AutoPilot diagnostics and turned out to be Dell Command that was causing the issue.

 

Remove that from assignment and testing again........

Edited February 3 by mdrabble

[mdrabble]

Well i thought it was fixed but I was wrong.

 

Dell Command was one of the issues which caused an outright fail.

 

The next issue I have is that an application is hanging on install and waits until the ESP timesouts.

 

Running the Get-AutoPilotDiagnosticsCommunity does not show any errors. (Great tool BTW!)

 

Any ideas where I can look next?

 

Cheers

 

 

[lparry]

Just to circle back to what @itskdog asked - do you have a mix of LOB and Win32 packaged apps?

 

Can you shift+f10 out to a CMD windows and use microsoft's MDM diagnostic tool to generate some logs? (mdmdiagnosticstool.exe -area DeviceProvisioning -cab C:\Intune\Log.cab)

[mdrabble]

2 hours ago, lparry said:

Just to circle back to what @itskdog asked - do you have a mix of LOB and Win32 packaged apps?

 

Can you shift+f10 out to a CMD windows and use Microsoft's MDM diagnostic tool to generate some logs? (mdmdiagnosticstool.exe -area DeviceProvisioning -cab C:\Intune\Log.cab)

 

Yes, very few LOB apps and never had any issues beforehand.

 

Generated the logs and then ran the Get-AutoPilotDiagnosticsCommunity against the cab file and the only error is one about a missing registry key (presumably issue with the script)

 

Looks like I may have to start unassigning apps and then slowly add them after each image to see what is causing the hang.

 

Edited February 5 by mdrabble

[lparry]

17 minutes ago, mdrabble said:

 

Yes, very few LOB apps and never had any issues beforehand.

 

Generated the logs and then ran the Get-AutoPilotDiagnosticsCommunity against the cab file and the only error is one about a missing registry key (presumably issue with the script)

 

Looks like I may have to start unassigning apps and then slowly add them after each image to see what is causing the hang.

 

Sadly probably the only way in that case!

 

I'd start with removing all of one type of app (LOB or Win32 - preferably LOB) and going from there.

 

There's a good explanation of what could be happening in the background by someone smarter than me:

Quote

 

When you deploy a Win32 app, it uses in the Intune Management Extension (IME) to grab the app details, kick off the installer, wait for the exit code, detect it and then trigger the next one.  All nice and straight forward and you know the IME is putting them all in a queue for you.

 

MSI LoB on the other hand is just sent straight to msiexec on the device.  Intune will stagger your MSI LoB installs, but it has no awareness of them so will add your Win32 ones soon afterwards.

 

If you are lucky, the apps will have completed installing before the first Win32 hits, but if not, your Win32 app will start the installer, trigger msiexec which will get extremely unhappy because it’s already in-use.

 

We’ve all seen the familiar “there is already an installation in progress” screen, only this time it’s in the SYSTEM context AND during ESP so no-one sees it at all.

 

The end result is no-one can click the retry button, the app is stuck in limbo and eventually times out, fails to install and your whole ESP comes crashing down around you.

 

 

[itskdog]

1 hour ago, mdrabble said:

very few LOB apps

 It's best to distribute all apps, even single-file MSIs, as Win32 if you're using Autopilot V1 as they could end up trying to install at the same time, and failing during ESP.

 

If you don't want to convert them, then change the blocking apps in the ESP to only the essential apps (antivirus, monitoring, etc.) and let other apps install after enrolment completes (just leave it on the login page for an hour or two) - see how I have it set below.

 

The blocking apps should all be Win32 apps (.intunewin packages) to avoid conflicts - if you want to deploy Office during ESP, package it as a Win32 app with a configuration.xml, rather than the M365 Apps app type.

 

[mdrabble]

23 hours ago, itskdog said:

 It's best to distribute all apps, even single-file MSIs, as Win32 if you're using Autopilot V1 as they could end up trying to install at the same time, and failing during ESP.

 

If you don't want to convert them, then change the blocking apps in the ESP to only the essential apps (antivirus, monitoring, etc.) and let other apps install after enrolment completes (just leave it on the login page for an hour or two) - see how I have it set below.

 

The blocking apps should all be Win32 apps (.intunewin packages) to avoid conflicts - if you want to deploy Office during ESP, package it as a Win32 app with a configuration.xml, rather than the M365 Apps app type.

 

 

I removed all LOB apps and left Win32 and Store (New) apps being deployed and it still hangs until the ESP reaches the timeout limit.

 

No error being show, it just sits on the installing apps.

 

AutoPilot Diagnostics does not show any errors

 

The strange thing is, that if i open a cmd prompt and go into control panel, all the apps are installed..... so unless something not bring reported back as being installed and ESP waiting for notification of some kind.

 

I have now unassigned all apps regardless of type to see if still hangs.

 

Total pain in the rear having to reimage each time