@hsikkema said in newbie: imaging:
Are you saying that I should NOT run sysprep at all once I have the system setup
No you should run sysprep if you want to deploy one mother image to many target systems. What I’m saying is that sysprep and windows 10 work a bit differently then sysprep and win7. Where in windows 7 you could setup the system exactly like you wanted it and clone it to many systems. With win10 M$ says, <snark> they know better than you </snark>. Where OOBE will reset somethings that you setup during the creation of the golden image. So if you set the system one way in the golden image and then once deployed the values are reset blame it on Microsoft. To get around this system reset you can fix it again using the setupcomplete.cmd file (google it) and setting in the unattend.xml file. You need sysprep to reset the system guid and some other settings used by management programs. Also to prepare the system for deploying to different hardware platforms.
I say this with some hesitation because I understand the meanings, but if you have a golden image on a Dell 9410 and you will clone that image to other 9410s you really don’t “need” to sysprep the image. This is because all of the hardware drivers needed for the target system are already on the computer. But lets say you wanted to deploy that Dell 9410 image to a Lenovo thinkpad? In this case you MUST sysprep the system.
Imaging is a ballancing act between what microsoft things you need, plus settings in the unattend.xml file and then finally corrections you might need to make in the setupcomplete.cmd file or the firstrun commands in the unattend.xml file. Imaging Windows computers is a bit of a black art and this is all before you get FOG imaging in the picture.