Creating a .sysprep image

JobCreator

Honorable
Apr 18, 2013
1,077
0
11,660
Hello again, Toms Community!

I have a very simple request that may involve a very complicated answer.

Here are my desired results:

1) Boot to Acronis.
2) "Recover" from a .sysprep image
3) Boot to disk and avoid the need to reinstall everything.

Here's the long of it.

At work, we have external drives with .sysprep images of most versions of Windows so that the reinstall process is streamlined. We do precisely what I just laid out. We boot to Acronis and "recover" the .sysprep image of Windows onto a new hard drive so that we don't have to go through all the Windows Updates or install Office and all the other junk that is standard on our machines.

I want to create one of these .sysprep images for myself. My home computer has all my programs, Steam, Origin, Uplay, my antivirus, etc. etc. etc.

The tutorials I've seen have all ended in the creation of a .WIM file, which seems to be along the same lines as what I'm looking for, but I'm nauseous about changing old habits.

So, my question to you is whether one of you kind-hearted blokes would give me a very rudimentary step by step on how to create a .sysprep image of my home computer so that when I go buy a new DDR4 mobo/cpu/ram combo, all I need to do is pop in the mobo driver disk and transfer my libraries back onto the new SSD.

I will continue searching for the tutorial that I want in the meantime.

I'm somewhat knowledgeable with the workings of computers, so no need to REALLY dumb things down, but give me the basics and I should be able to comprehend it.

Thank you so much for your help!
 
Solution
What you are describing appears to be more of a backup solution than a deployment solution. There are three ways I see to accomplish what you want to do:
1. A basic image-based backup solution such as Windows System Image Backup.
2. An image captured after having run Sysprep to generalize the image.
3. A deployment solution to manage a new image and/or application installations, etc.

The first solution is by far the simplest, which is to just create a backup image of your current system and to restore it to a new system in the case of system failure or replacement. The image will not be generalized, but if you have any issues restoring it to a new system you can restore it to a virtual machine and remove any conflicting drivers through...

WinOutreach2

Distinguished
Mar 3, 2011
413
0
19,160
What you are describing appears to be more of a backup solution than a deployment solution. There are three ways I see to accomplish what you want to do:
1. A basic image-based backup solution such as Windows System Image Backup.
2. An image captured after having run Sysprep to generalize the image.
3. A deployment solution to manage a new image and/or application installations, etc.

The first solution is by far the simplest, which is to just create a backup image of your current system and to restore it to a new system in the case of system failure or replacement. The image will not be generalized, but if you have any issues restoring it to a new system you can restore it to a virtual machine and remove any conflicting drivers through manual uninstallation. This also allows you to avoid Sysprep generalization, which can conflict with security software.

The second solution is essentially what you outlined that you do at work. You would generalize the system with Sysprep and shut it down, then boot to an imaging solution and capture an image. This imaging solution could be DISM on WinPE, MDT boot media, Acronis, or any other imaging solution. One disadvantage to doing this solution is that you will have to generalize your existing environment on your system, so after capturing the image you would boot to an environment stripped of activation information, drivers, etc.

The third solution is to create a new image from a system that is based on a minimalistic environment (usually a virtual machine). In this image you could install your applications, or let them be managed by a deployment solution like the Microsoft Deployment Toolkit (MDT). This would mean that you would not need to run Sysprep on your existing environment, only on a virtual machine. It would also ensure that the minimal driver configuration is present in the image to minimize conflict. With MDT you can even chose to add your apps and drivers to MDT rather than into the reference image and have them be installed automatically. If you’re interested in MDT and what it can do, either for you or for your work, you should check out the Windows 8.1 Deployment Jump Start here. The deployment technologies and concepts discussed also apply to Windows 7.
 
Solution

JobCreator

Honorable
Apr 18, 2013
1,077
0
11,660
Ok, I screwed up. The images are actually .tib files. Not sure what that is. They are not .sysprep like I thought. It is a system prepared image, though.

My problem is that I don't know how to save the generalized image after running sysprep.

I actually did the following...

Ran sysprep to create a generalized image of my current configuration and chose "shut down" upon completion. Then, I stripped the mobo/cpu/ram out and replaced them with completely different parts. Powered on, and voila! It ran through a "first time use" setup through Windows.

Ideally, though, I want to create that image and save it so that I don't have to do everything between the time I choose shut down and the next power on. I want to do as you described, use an imagine software to recover the image onto a drive. Is there a second piece of software I need in order to capture the generalized sysprep image?
 

WinOutreach2

Distinguished
Mar 3, 2011
413
0
19,160
TIB is the format of Acronis True Image Backup. You can restore this on the destination system with Acronis boot media.

The piece of software which you are missing is offline media which supports the creation or restoration of images. The Acronis boot media can provide this, or in the solution I outlined before, you can create boot media with MDT which provides similar functionality.