Intunewin Upload Head Scratcher

Question

I built out an Adobe DC Professional app for an Intune deployment like I have done many times. It's a larger app coming in at 1.5GB. I uploaded to my test dev tenant in about 30 minutes from my house with no errors. Tested the app and it installed just fine.

I then built the app with the same files in client's tenant and it failed with the following error:

An unexpected error occurred during upload of the IntunePackage.intunewin file.

[403 Server failed to authenticate the request.

Make sure the value of Authorization header is formed correctly including the signature.]

Try adding this app again.

I tried multiple times using multiple browsers, cleared out Internet cache and temp files, and no matter what it failed. Granted, my Internet is not the quickest game in town, but I was able to deploy in my test tenant. I noticed that the failure would come like clockwork after 15 minutes.

Some Google-fu brought me to Johan's site https://www.deploymentresearch.com/deploying-large-applications-using-microsoft-intune/#:~:text=My%20Internet%20connection%20when%20doing%20this%20POC,token%20not%20being%20refreshed%20during%20the%20upload.&text=Note%20%232:%20A%20good%2020%20minute%20of,the%20machine%20preparing%20the%20package%20for%20upload.

While not completely on point with what I was doing, it did mention this:

My Internet connection when doing this POC only had 20 Mbit upload, and the IntuneWin32App PowerShell module from Nickolaj Andersen (@NickolajA), that I typically use to create the packages, would timeout after 15 minutes due to the authentication token not being refreshed during the upload.

Not sure how to increase this timeout in the client's tenant or what to look at, but I suspect something along these lines is causing the issues I am having with uploading this file on my Internet connection to this tenant.

I able to successfully upload the intunewin using my employer's connection and got the app built rather quickly with no errors.

Anyone have any idea where I should look or how to fix this timeout I was seeing after 15 minutes?

Answer 1

@Matt Dillon, Thanks for posting in Q&A. From your description, I know you're encountering an issue with the authentication token timing out during the upload process, which is causing the 403 error. This can happen if the upload takes longer than the token's validity period, especially with slower internet connections.

Unfortunately, there isn't a direct way to increase the token timeout for Intune uploads. However, you can try to ensure that your upload speed is as fast as possible to complete the upload within the token's validity period.

For your scenario, here are some suggestions from my side.

1, Use a Faster Internet Connection:

2, Upload via PowerShell.

Here is a link with more details for your reference:

https://www.deploymentresearch.com/speeding-up-win32-apps-upload-via-powershell/

Note: None-Microsoft link, just for the reference.

You can try the above suggestion and if there's any update, feel free to let us know.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.