In order to upgrade the Win10 version and fix issues on certain machines, I created a provisioning template that reboots the laptop and performs the OS upgrade/refresh form the install media. I run setup.exe from the installation with the command line strings "/Auto Upgrade /Unattend /Copylogs %SystemDrive%\ProgramData\LANDESK\Log\" as a software distribution package. These actions are being performed in the system configuration pass. I created a Provisioning Package referencing the provisioning template to create the distribution task.
I pushed this task on about 30 some odd machines and had 25 BSOD's "A required device isn't connected or can't be accessed". A few were repaired by hitting F9 to choose a different operating system, but most had to be swapped out. Not a good few days afterward.
I had previously done this process on about 100 machines prior to this using the install source and manually running the commands. In order to speed the process of the remaining machines in need, I created the provisioning template to run this. I often ran into people that said they would reboot their machines before they left, but had done nothing but walked away at the end of the day with all their apps left running. To combat this, I created the template with the reboot as the first action to overcome this issue.
I could never pinpoint what had caused the BSOD's and chalked it up to a massive freakout that hit the VMWare environment that runs the core server on the night that the task was push out the the 30+ machines. Yesterday, I rolled up another task to upgrade to 1709 in same provisioning template mold. First test run of it gave me the BSOD. To test if it were the source install causing this (which was different from the 30+ machines) I copied the install locally and ran it with the same command line. This went through fine. The only difference really between the two runs in that there was an initial reboot in the template and the setup was run as the System account, not as a local admin as in the second run.
So, since the second run indicated it wasn't an issue with the install source, I tried moving the reboot into the Pre-OS installation pass. This test ran fine.
Why would having a reboot action in the same configuration pass in the template cause a BSOD? This really does not make any sense to me.
I have attached the working templates and packages and the template that caused the BSOD's initially (Windows 10 1703 Refresh.xtp)
Windows 10 1709.xtp.zip 1,013 bytes