Windows 10: Using sysprep to create universal image for different computers.

Hello. I am a IT guy that often has to come in and reinstall a lot of different Windows 10 computers. I always just used a regular win10 usb installer created using MCT but i found out about sysprep.

Basically I would like to create a universal image that can be imaged to other PC's, after the imaging is complete I would like the system to once again boot into sysprep, so i can install drivers for that particular model of a laptop/pc.

I set up a Hyper-V machine in audit mode as a reference computer, i installed all the needed programs and set the company wallpaper as well as OEMinfo. What should i do next?

I would like to write that image to a target computer harddisk, and i would like it to once again boot into audit mode. From there I would install all the drivers and run sysprep afterwards with generalization selected. I would then select a shutdown option and leave the computer for the user to set up their credentials.

submitted by /u/verpejas
[link] [comments]

:)

 

SysPrep Advice

Hi Joseph,

The topic that you raised is beyond the scope of support for this site which focuses more on home and personal end users. Here's what I found about SysPrep:

• What Is Sysprep?
• How To Sysprep – Sysprep is a Great And powerful tool And Easy
  Too If You Know How (Step-By-Step).

However these are old articles and the process may have been changed already. You may re-post this question in

TechNet Forums for further assistance.

All the best.

 

Best way to create W10 Pro reference computer and deploy the image

I noticed one of the prerequisites listed on this page for capturing and image using DISM is as follows:

Will I need to generalize my image as stated in the article? I am a little afraid of Sysprep since last time I tried it it failed me miserably. Granted, I have everything backed up now

 

Best way to create W10 Pro reference computer and deploy the image

Its all up to you if you want to try and work with Sysprep- I've gotten by just fine with this without messing with that stupid thing. The only time I see that you would need to do that is if your computers are connected to a Windows domain. All of the computers are going have the same computer name as the reference machine when you get done with imaging- which would create a hassle with managing them on a Windows domain (you'd have to go back to each one pull it off the domain, rename it, add it back to the domain). Sysprep would strip the Windows install of its name and go back through a specific step of the answer file you created (the generalize step step 4 I think it is), which would then apply whatever settings you setup there and then ask for a computer name. (I don't know if that's exactly what would happen, but theoretically that's what is supposed to happen).

>>Given these aren't on a Windows domain (right?) I would say stay a good 20 feet away from Sysprep- I've had zero success with it with this and I see no reason to try and figure it out when things work just fine without it.

>>Lets say each computer does need its own unique name (maybe for inventorying purposes) you would have to go back to each machine and rename it (however, its not going to be as much of a hassle as it would have been if these computers were on a Windows domain).