Forum Discussion
Windows 10 2004 Update and Setup School PC Provisioning Package Fails
MDSD421 Hi there! Sorry for not seeing this issue sooner! We have made an update to fix this issue. Make sure you have the latest version of SUSPC downloaded from the store (right now it's 1000.17147.17.0) and you should be good to go! Note that 2004 is not yet visible in the OS dropdown, select "1903 and later".
MicrosoftMDSD421 Hi there! Sorry for not seeing this issue sooner! We have made an update to fix this issue. Make sure you have the latest version of SUSPC downloaded from the store (right now it's 1000.17147.17.0) and you should be good to go! Note that 2004 is not yet visible in the OS dropdown, select "1903 and later".
Liz_Cox I'm having the same issue but no matter what I try provisioning fails on over half of our surface go's. It works flawlessly on some but just fails out on others. Any input or advice would be great!
- Liz_Cox
pghdjspaz are you doing this with 2004 devices? Are all the devices the same OS image? If possible, can you message me a picture of what the screen looks like when provisioning fails.
Liz_Cox I decided to go back to 1909 which fixed the provisioning issue but the only problem I have now is no matter where I try to create the provisioning package the next button is greyed out when trying to customize the name.
I noticed a couple of glitches when using the new Setup School PC app.
- When you get to the Device Names step, the next button is grayed out. No matter what name pattern you enter, the next button remains grayed out. You can click on Continue With Existing Names and create the package. After deploying the package on a computer, the computer ignores the name patter and gets the default "Desktop-" name. I then have to rename the device from Intune and have it append the serial number. We use Intune groups to deploy apps and settings, so having to manually rename several hundred devices will get very time consuming.
- After deployment is finished and you go to sign in, the "Continue anyway" button is gone, so you have to wait for the initial setup to finish each time a new person signs in before the user gets to the desktop.
- Liz_Cox
MDSD421 the greyed out rename button is a bug, and we're working to fix as soon as possible. If it can't wait, you can create a provisioning package with Windows Configuration Designer- the rename functionality still works there.
For issue #2- I'm having trouble understanding what is happening. Does provisioning complete successfully? If so, there shouldn't be a "continue anyway" button.
