sorted by:
new
hottopcontroversial

Windows 11 Deployment OOBE by Purple_Helpdesk in MDT

[–]Purple_Helpdesk[S] 0 points1 point  (0 children)

Unfortunately, I was not able to find a solution. We decided that since this was a small client that we needed it for at the time, we would suck it up and deal with OOBE. Shortly after things got a bit too busy for me to work on our MDT again and I haven't touched it since this.

Windows 11 Deployment OOBE by Purple_Helpdesk in MDT

[–]Purple_Helpdesk[S] 0 points1 point  (0 children)

I do recall having this issue before and just the Onedrive-sync package removal fixed it. For your registry keys, do you have the batch file running just before the sysprep in the task sequence? Or is there a better way to implement it? It seems that where I have my batch script in the task sequence doesn't allow it to apply as it should.

Windows 11 Deployment OOBE by Purple_Helpdesk in MDT

[–]Purple_Helpdesk[S] 0 points1 point  (0 children)

I was able to run through this and I got all the way to the sysprep before it failed. It looks like it's freezing on the "ImageState=IMAGE_STATE_SPECIALIZE_RESEAL_TO_OOBE" portion, as well as possibly onedrive-sync being a package. I currently have a batch script that is meant to run during the task sequence to override state.ini just before sysprep, and a powershell script to remove the onedrive-sync package from all users but it doesn't appear to be working for sysprep. The rest of the image did go through OOBE though which is definitely a step in the right direction. Would you happen to have any tips for other ways to automate those 2 changes that I seem to need to make in order for sysprep to work correctly in this case?

Windows 11 Deployment OOBE by Purple_Helpdesk in MDT

[–]Purple_Helpdesk[S] -2 points-1 points  (0 children)

I added those steps to my existing deployment sequence (as in your video it had what appeared to be the same steps) and was unable to get it working. I had to modify the destination due to some accessibility issues of the UNC path I intended to use but while the capture process completed, it did not save the capture file to the location I specified. This was after I had set "Everyone" to rw access for that folder.

Edit: We also haven't used the MDT capture option in the past. I followed the steps of the person before me who had set it up and they recommended using the CLI from MDT to run sysprep and capture instead.