New
#1
Dism / Imaging question
Hello Gang, Long time no posts from me.
Personally been a fun year so far, heart surgery, but on the job side I'm FINALLY somewhere where I'm loved and I love the people I'm with, plus I'm learning a crapton of stuff!
Ok, a lot of that has delved into dism / imaging and powershell scripting. It really has been fun.
Ok, my setup and the question:
Have an optiplex mini desktop, booted it up to 10, preformed all updates, etc. up to 21H2 19044.1682 , ran a prep script I wrote which consolidated 3 scripts we used to run to get the machine prepped for use in the organization (removing bloat, setting support options, etc.)
I then rana sysprep on it: /oobe / generalize / shutdown (This time I didnt use an unattend file, hadnt yet made one for this model)
It ran and shutdown. I immediately boot into a win PE drive (Latest) and used dism to capture my c drive image.
My question though, is somehow, something has changed from my previous results: the system I took the image off of, when rebooting it up goes to an winload.efi BSOD. I don't recall having that issue before.
Troubleshooting, it appears the BCD is gone on it.
Now, that said, I took my brand new image of C, booted the "Source" PC and wiped C, then applied the image, and that works, it boots to oobe. In addition and other separate PC I boot to PE, wipe C amd apply the image, and it boots to oobe.
I'm happy on the appearance that the image itself is good (so far), but am scratching my head as to why the source PC behaves as such after I did the sysprep and took the image.
With this limited info on the process, anyone have any ideas? (Hey, and long as I can use the image itself, reapplying it to the source PC and the others in the line is not a problem for me, I definitely believe I've ruled out the image itself being bad ...)
I appreciate al the wonderful people here!
Marc