How to create a Windows 10 image

I am looking for guidance on how to create a Windows 10 image—complete with all necessary drivers, software, and configurations—so that I can later deploy it to other machines using Windows Deployment Services. If anyone could offer advice on the most effective way to build this image and which specific tools would be best to utilize... I would appreciate it. Are there particular pitfalls to watch out for during the configuration process? Should I be relying on Windows system image manager, or is there a better alternative...

Creating a Windows 10 image follows the same old playbook as everything else. Since you brought up WDS, I’m guessing you already have a WDS server sitting there ready to go.
If that's the case, just grab a machine (or a VM) and set it up exactly how you want it—install the OS, grab all the latest updates, and get all those necessary programs and drivers installed. Once you're happy with how everything looks on that machine, run Sysprep. After it restarts, boot from the network so you can hit that WDS server and capture the image. From there, you just follow the wizard; it's pretty much foolproof.

As for drivers, you don't actually have to bake them into the image itself. You can just host them on the WDS server, and it'll pull them during the installation process.

If you're looking to automate the whole deployment, you'll want to build an answer file using the Windows Assessment and Deployment kit (Windows ADK) and then just point the WDS to that file for the image.

Maria James94 said:Creating a Windows 10 image follows the same old playbook as everything else. Since you brought up WDS, I’m guessing you already have a WDS server sitting there ready to go.
If that's the case, just grab a machine (or a VM) and set it up exactly how you want it—install the OS, grab all the latest updates, and get all those necessary programs and drivers installed. Once you're happy with how everything looks on that machine, run Sysprep. After it restarts, boot from the network so you can hit that WDS server and capture the image. From there, you just follow the wizard; it's pretty much foolproof.

As for drivers, you don't actually have to bake them into the image itself. You can just host them on the WDS server, and it'll pull them during the installation process.

If you're looking to automate the whole deployment, you'll want to build an answer file using the Windows Assessment and Deployment kit (Windows ADK) and then just point the WDS to that file for the image.

I don't have a WDS server ready yet—so network booting isn't an option for me right now. I have just installed everything needed on the machine and ran Sysprep... Is it possible to put that image onto a USB drive first to test it out, and then eventually move the image over to the WDS later?

You can totally handle the capture manually if you want. You'll just need to grab a WindowsPE bootable media that has ImageX tucked inside.

Here’s a quick example of how you'd capture the "C" drive and dump it onto "D":
imagex /capture c: d:\install.wim "Windows 7 x64 Ultimate" /compress maximum
imagex /capture "Description" /compress maximum

Once you're done, you'll have a .wim file ready to be uploaded to WDS whenever you need it.

Back in the day with older versions of Windows, you could pretty much just grab the C:\Windows folder, toss it onto another drive, and call it a day. 😁

I haven't really figured out how they want us to handle it now with these new, glorified spy-ware gadgets they're pushing on us.

Maria James94 said:You can totally handle the capture manually if you want. You'll just need to grab a WindowsPE bootable media that has ImageX tucked inside.

Here’s a quick example of how you'd capture the "C" drive and dump it onto "D":
imagex /capture c: d:\install.wim "Windows 7 x64 Ultimate" /compress maximum
imagex /capture "Description" /compress maximum

Once you're done, you'll have a .wim file ready to be uploaded to WDS whenever you need it.

I started by running Sysprep on the machine and setting it to shut down... Once I rebooted, I couldn't find my bootable media in the boot menu. So, I went through Recovery to access the command prompt. In the command prompt, I ran:

dism /capture-image /imagefile:c:\install.wim /capturedir:c:\ /name: windows

This gave me the install.wim file on the C drive, which I moved to the bootable media to install Windows on a different PC. Now, my question concerns the computer's SID—how does one influence that? Specifically, how to ensure it's unique for every installation performed via WDS...

When you're putting together a bootable drive, just double-check that you actually have the "make bootable" option checked in whatever software you're using to burn the media.

Also, when you're running Sysprep, make sure to hit that Generalize button. You want to strip everything back on the reference machine so the install goes smoothly on any new PC without hitting random roadblocks.

You can actually handle it all through Rufus
https://rufus.akeo.ie/