Windows-itpro-docs: 1903 fails to provision with set up schools pcs app

Created on 30 May 2019  Â·  11Comments  Â·  Source: MicrosoftDocs/windows-itpro-docs

With 1903 running in S mode provisioning with the set up school pcs stick fails. I get error code 0x80070005. I have tried several different combinations of settings on the app but it has failed everytime.


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Most helpful comment

After working with intune support we have a workaround for my issue. There is currently a known issue with provisioning over wifi. The solution that worked for me was to create a stick with Windows imaging and configuration designer with just the wifi settings and then create a second stick with set up schools to configure the rest after the wifi settings are applied. Here is a link to some more info https://techcommunity.microsoft.com/t5/Intune-Customer-Success/Known-issue-Provisioning-error-on-Wi-Fi-for-Azure-AD-joined/ba-p/676299

All 11 comments

All of those pages are related to windows updates. I am trying to run the set up school pcs app provisioning package on a new 1903 image running S mode. I get this error during OOBE.
IMG_0549

Fair enough, maybe there is something new happening within 1903 which did not happen on earlier versions (or there could be something else entirely).

We need to wait for follow-up from one of the team members handling the issues.
I also presume you will need to contact Microsoft Support in your region to get your problem solved in a timely manner.
Please note that these pages are intended for improving the Documentation pages.

If you are able to get the issue solved with help from Microsoft Support, you are more than welcome to share, especially if the solution adds useful information to the current documentation page content.

@officedocsbot assign @mypil

@nickesping - Thank you for submitting feedback.

I think the best way forward is if you can open a service ticket so this can get resolved ASAP. Based on outcome let me know if it is something that can be called out in the docs.

Please follow this link to contact support for Windows 10 products:
https://support.microsoft.com/en-us/hub/4338813/windows-help?os=windows-10

If you don't mind please keep us posted here on the resolution and I really want to get this information you are discovering back into the docs.

@mypil - I submitted a ticket with the intune support team a few days ago and provided them with all the information and logs they have asked for so far. I will update this post when we figure out a resolution. Thanks.

@nickesping - This is noted. We will close this issue for now. Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.

@officedocsbot close

After working with intune support we have a workaround for my issue. There is currently a known issue with provisioning over wifi. The solution that worked for me was to create a stick with Windows imaging and configuration designer with just the wifi settings and then create a second stick with set up schools to configure the rest after the wifi settings are applied. Here is a link to some more info https://techcommunity.microsoft.com/t5/Intune-Customer-Success/Known-issue-Provisioning-error-on-Wi-Fi-for-Azure-AD-joined/ba-p/676299

Thank you for posting again, good to see that you got a solution. Even if we consider that the Microsoft Docs team might want to "chime in" with a suggestion, do you have a suggestion for an improvement to the article?

Hi @nickesping, thank you for keeping us up-to-date and sharing your resolution. I filed an internal work item to update the SUSPC articles with some troubleshooting help. Here's some additional information/alternative solutions from the product team about this particular error.

Error 0x80070005: Access Denied.
If you encounter this error immediately after plugging the USB, it’s likely there is another package on the device and it is not in a clean state. There can only be one provisioning package applied to a device. You will need to reimage and try again.

If the error occurs after you’ve seen the UI showing the provisioning progress, then the AAD bulk token likely isn't valid anymore. Check if the package works on other devices. If not, likely one of the prerequisites is not met. If all prerequisites are met, please create a new package and try again. If it still fails, collect information and contact support.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ruffy91 picture ruffy91  Â·  3Comments

sundhaug92 picture sundhaug92  Â·  3Comments

RAJU2529 picture RAJU2529  Â·  3Comments

marcnil815 picture marcnil815  Â·  3Comments

michalzobec picture michalzobec  Â·  3Comments