You can tell by the monitoring screenshot that this step is currently where we are in the process (step 91/98). The highlighted step below "Execute Sysprep" is where the issue begins. Here is where it is executing sysprep and rebooting. I think I have the problem narrowed down after another attempt at this. I feel like it should be capturing the image and finishing out the task sequence, but it seems that it's just booting to Win10 after the sysprep and abandoning the task sequence, which evetually becomes unresponsive in the mdt deployment share monitor. It shouldn't be sysprepping and then booting back into Win10. I really don't think this error is my problem. I let the last one go for about 12 hours. Eventually the MDT Monitoring status shows "Unresponsive". I click OK, it lets me in Win10 with the new hostname. I can tell before it even lets me into the OS, because WSUS picks up the new name.Īnd then I get this error. It starts booting me back into Win10 and this time it has a different hostname (cherryg-18g1on1). ![]() I think at this point it should start capturing the image, but it doesn't. At this point the deployment share monitoring is showing the "execute sysprep" stage and I'm seeing this happen on the vm. Logs me back into Win10 with Administrator account. *Checked hostname (cherryg-i58sors)Ĥ) Now I resume task sequence, It checks WSUS, Apply WinPE, and reboots the vm. I can see that all of the software has been installed without error (MSVC 2019x86, MSVC 2019圆4, MS Office Business, Google Chrome). At this point it is waiting for me to Resume Task Sequence, because I added the optional suspend action into the task sequence. Everything looks good.ģ) The OS installs without error, it logs me into Win10 with Administrator account. Using the 圆4 iso rather than x86 as mentioned in the guide, because my vm won't boot to the x86 iso.Ģ) I get to the Windows Deployment Wizard Capture Image part. ġ) Boot to optical drive of vm with my mdt build iso attached. I get all the way to the sys prep stage of the task sequence, the sysprep appears to run like normal, the vm reboots, and then logs me back into the OS and displays "can not find script file c:\ltibootstrap.vbs". The only option I have is to click OK or click the X. Instead it is abandoning the task sequence. It should be capturing the image and finishing the task sequence. ![]() ![]() It shouldn't be sysprepping and then booting me back into Win10 with a different hostname. I really don't think that the error is my problem. I re-wrote this to try and make it a bit easier to understand.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |